Wine 11 rewrites how Linux runs Windows games at kernel with massive speed gains

Re:Wine 11 rewrites how Linux runs Windows games at kernel w... by Rohansi on Tuesday March 24, 2026 @06:43PM (#47510582)

Yes, they are easy to port a lot of the time. Especially now because you can use DXVK to translate DirectX calls into Vulkan, so you don't need to write a Vulkan renderer. Input is sometimes a trickier one to deal with but a lot of the time games are using cross-platform libraries for that already!

Despite all this the Unity engine has spotty Linux support. Some games run better under Wine vs. Unity's native Linux builds. It's Vulkan renderer has had a memory leak for a while now. Input has randomly decided to double keypresses on some distros.

[ Parent | on HN ]

Re:Wine 11 rewrites how Linux runs Windows games at kernel w... by MindSpunk on Tuesday March 24, 2026 @07:27PM (#47511054)

The hard part of Linux ports isn't the first 90% (Using the Linux APIs). It's the second 90%.

Platform bugs, build issues, distro differences, implicitly relying on behavior of Windows. It's not just "use Linux API", there's a lot of effort to ship properly. Lots of effort for a tiny user base. There's more users now, but proton is probably a better target than native Linux for games.

[ Parent | on HN ]

Re:Wine 11 rewrites how Linux runs Windows games at kernel w... by simonask on Tuesday March 24, 2026 @08:52PM (#47511762)

It’s not really about OS differences - as the GP said, games don’t typically use a lot of OS features.

What they do tend to really put a strain on is GPU drivers. Many games and engines have workarounds and optimizations for specific vendors, and even driver versions.

If the GPU driver on Linux differs in behavior from the Windows version (and it is very, very difficult to port a driver in a way that doesn’t), those workarounds can become sources of bugs.

[ Parent | on HN ]