VR has much more stringent latency requirements than normal gaming, because moving your head needs to be in perfect sync with the world “staying still”. The manual calibration needed for this is around 8ms, which is compensating for the render/presentation time of a single frame at 120fps.
It sounds like a nitpick, but I can tell you from experience that it makes a very significant difference.
if it takes you 20 shots to neutralize a threat at point-blank, I don’t think you should be allowed to own a gun
deleted by creator
So you’re telling me to stop paying my bills in protest of Google Chrome, because I’m not technically being forced to pay my bills
What a privileged life to lead, where you aren’t forced to use certain websites by (e.g.) your student loan servicer, or your utility company
Still waiting for them to fix latency reporting for AMD 7000 series GPUs
https://steamcommunity.com/app/250820/discussions/3/3802777845426075295/
Loving the hand on the counter
Just because the other kids are doing it, that doesn’t make it ok
The text of the LGPL actually imposes some very inconvenient restrictions around static linking:
Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.
https://www.gnu.org/licenses/lgpl-3.0.html#section4
In order to be compliant, you would have to also ship linkable object files of the proprietary application code alongside the executable.
can’t wait for 12 years from now when we can finally begin to stop making climate change worse
US dollar bills are 6 inches long
oh no, you can definitely pet bears
Sounds to me like maybe the sample rate is changing away from what your application expects (44.1 vs. 48 kHz). I used to have this problem with Pulse quite often, but I don’t remember if I fixed it before switching to PipeWire.
Pulse has a “preferred sample rate” setting in its config files, but it seems to only really be a suggestion, and Pulse tends to ignore it.
What a coincidence, so was I
Unfortunately for that, the middle part is gonna have to go negative 😔
Source?
Kagi search subscription, absolutely
Yeah, well, I’m surprised it was that high.