The issue is one of licensing, not technology. There’s all kinds of patents in the space, and using free codecs could still infringe them. DirectX doesn’t have the same patent protection. I believe in theory you could make a fully open source Linux native version of DirectX.
For more info from someone who knows more than me, see here.
Well, sometimes Windows games depend on propietary codecs, and until Valve can get the devs to make adjustments so the codecs aren’t needed, the games aren’t going to work properly in regular Proton.
If GE received a Cease and Desist, that would be frustrating, but linux gaming would go on. If Proton got a Cease and Desist, that could be catastrophic to linux gaming. Valve could even theoretically get banned from working on linux gaming (like the Yuzu devs got banned from working on emulation). It’s just not worth the risk for compatibility/performance for a smaller proportion of games.
This isn’t binding tho, Adobe could change their minds in a year and then legally train an AI on all the data they’ve collected. Their own blog post doesn’t even preclude that, their AI language is present tense. In addition they could just license the data to other AI companies.
This is a great list of USB wifi adapter chipset compatibility.
Nvidia already opened their driver, at least to the same extent as AMD, which is why NVK is able to exist.
I’m not sure about the latter
I believe it was Xwayland 24.1 that recently released that brought explicit sync support, so you’ll need that.
Seems like a good redesign.
I believe that the custom for a lot of wine patch notes is just to mention the first application reported with the bug even if it affects many applications. So that could be what’s happening here.
will not solve issues with compositors not having it
Many compositors already have patches for explicit sync which should get merged fairly quickly.
graphical libraries not having it
Both Vulkan and OpenGL have support for explicit sync
apps not supporting it
Apps don’t need to support it, they just need to use Vulkan and OpenGL, and they will handle it.
Wayland doesn’t implement sync of any kind, they probably meant to say “the Wayland stack”
Wayland has a protocol specifically for explicit sync, it’s as much a part of Wayland as pretty much anything else that’s part of Wayland.
Nvidia is not the only driver that needs to implement explicit sync.
Mesa has already merged explicit sync support.
The reason is 24.04 is LTS, and they want to keep things more stable, even if that means more bugs. 24.10 should come with 6.1 in the fall.
Currently yes, tho Wine has gotten pretty far with Wayland support, so it wouldn’t be too surprising to see Wine Wayland be useable for gaming in the next year or two.
I’m in a similar boat. I’ve got a bunch of small Wayland niggles, but I’m waiting to investigate them until after I switch to Tumbleweed when it gets Plasma 6 (I’m currently on Kubuntu).
The games on Steam Deck are already running in Wayland using gamescope IIRC
I believe they’re saying that when come back from suspension, the wifi doesn’t work until they reboot.
Sounds like a “temporary” error message.
Could anyone give a brief rundown of the changes since 4?
The headliners are: 1. Porting everything from qt5 to qt6, 2. Getting Wayland working well enough to be recommended as default
And is there a preview version of 6 available yet?
There’s a beta out already
AMD/Nivdia GPUs will still run with RISC-V. RISC-V is a CPU architecture, not GPU.
It’s a very strange place to go on fire! A fire? At a Sea Parks? It’s been racking my head!
Linux may very well not be for you, but using Arch first is like jumping into the deep end to learn how to swim. It’s no surprise you’re drowning. I’d recommend you try a gaming-focused distro like Nobara before you go back to Windows for good.