vividspecter

And asbestos, which Trump has publicly claimed is not dangerous.

I don't have this controller but the Vader 4 pro was updated in the same update, and supports every single extra button + gyro at the same time, provided dinput mode is set.

Full compatibility means native steam input support, which means that gyro + back buttons work together. No need to emulate a specific console controller and lose out on either gyro or back button support.

Yes, although the approach that was fixed only applies to Hyprland and some other wlroots compositors. You can use the virtual edid approach on other systems, but it may not be supported on Nvidia GPUs. You can also use it as a simple supersampling method, such as rendering at 1600p to a Steam Deck, for example.

It looks like mainly a Hyprland fix (and maybe some wlroots based compositors). The old method still works with sway for me, and there's a another approach using a virtual edid that should work everywhere, but perhaps not with Nvidia cards (see here: https://discuss.kde.org/t/how-to-create-a-virtual-monitor-display/2725/5).

I'm not sure if Plasma or Gnome have any support for headless monitors outside of the EDID method.

Russia style petrostate feels the most likely. And in a time where fossil fuels are going through their death spiral (if in a somewhat prolonged manner).

Clean living in his view just means focusing on "natural" things. Which means swimming and drinking shit water is safe, but anything "artificial" is dangerous. So he's certainly not going to care about pathogens in the food supply, because he doesn't believe they are dangerous.

It's so LFC works properly. If there isn't a large range to work with, you can end up with gaps where VRR doesn't work, causing stuttering or tearing. LFC is needed in general because you want VRR to still work when FPS drops below the minimum frame rate. And while it's more of an issue with OLED displays there can be negative side effects such as flickering if the display minimum refresh rate is set too low.

The 120Hz refresh rate doesn’t seem to make a lot of sense if frames can’t even transition at a rate that keeps up with it.

The main use is for VRR, with bigger ranges making it more usable (and input latency should improve, but few games are going to run at 120fps). However, it seems like the feature is mostly broken in retail games, with it only really working in that paid tie-in game.

Usually it's fine. To be honest, most new release AAA games have problems on Windows too (and sometimes it's worse, such as the first part of the FF7 remake).

Have a look at the Linux VR Adventures Wiki for possible VR solutions.

EDIT: And this compatibility site akin to ProtonDB I just found out about.

The original impetus to do these comparisons was that there were reports of significant motion blur on the Switch 2, so comparing it was the whole point.

And indeed, it's even worse than the original LCD Switch display.