This is not how motion blur works at all. Is there a specific game you’re taking about? Are you sure this is not monitor ghosting?

Motion blur in games cost next to no performance. It does use motion data but not to generate in between frames, to smear the pixels of the existing frame.

No

Motion blur off looks like those high shutter speed fight scenes from the Kingsman movies. Good for a striking action scene but not pleasant to look at in general. Motion blur blends the motion that happen between frames like how anti aliasing blurs stairstepping.

They asked me to put my hands behind my back and all that stuff, and I realized what was going on.

Because she was too dangerous to be cuffed normally, or not cuffed at all?

Als I hate this doubly for the kid. Your mom getting arrested for your slightest sign of independence will fuck you up.

They literally said the issue was an unintentional bug and then fixed it. How is that damage control?

No

Will it not use it even after the ram fills up? I wouldn’t want the compressed part be prioritised anyways

Do you need a swappiness over 1 if you don’t have another swap device?

Isn’t this already a thing on Wayland?

Xiaomi probably has some kind of maintenance app that can run automated checks, do that. If you’re paranoid, check if the bootloader is unlocked and if so reflash the stock rom.

Guessing from how this change required 3+ implementations before it became official according to the gitlab page, maybe it’s a chicken and egg situation. Hdr is a lot of work so maybe people don’t want to implement an unfinalized version that might change

Wow the icon saga is finished!?

If anyone wants to throw away a couple hours, there was SO much discussion (and initially drama) over it: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/269

Gpu brand shouldn’t be a factor, just buy whatever’s better value.

I’ve used nvidia on Wayland for a year and the issues are greatly exaggerated, and if you have a cpu with an igpu you can plug your monitor(s) into the motherboard to get around wayland-related ones (there’s probably some latency impact for games but I can’t tell).

Currently the problems (that I know of) with nvidia drivers are that colors get muted if you enable hdr, steam’s web interfaces appear corrupted or flicker unless you resize them, there is no memory spillover to ram, and the nvidia ‘x server’ settings app doesn’t support wayland.

And keep in mind that issues tend to get resolved over time. When I first built my PC the nvidia gpu would cause xwayland apps to flicker and didn’t support nigth light or transparent panels in kde. The amd igpu would turn the screen pure white if I changed windowing related kde settings. These don’t happen anymore.

If you can just add a 7ms delay without noticing it as the solution suggests, latency doesn’t sound that stringent. What the problem sounds to me like is that the headset doesn’t support vrr so frames have to wait a whole frame time if they miss their window, and steamvr doesn’t realise that’s happening. Which wouldn’t be a problem if this was managed by the driver instead

Why is this something valve needs to fix? For ordinary gaming gpu manufacturers already have latency lowering solutions that don’t overshoot or require hard-coded values. What makes vr different?

Does it work with nonstandard steam directories and proton?

This worked. Apparently I had all the usb devices connected to the same controller and it seems linux initialises them controller by controller. Thanks

I did try messing with the hook order but it’s already as early as it can be.

How would bios change how linux loads usb devices?

It works fine in bios and bootloader. This only happens during boot