The NTSYNC driver should be merged for emulating Windows NT synchronization primitives for speeding up Windows games running on Wine / Steam Play (Proton). (Update:) But it looks like so far only the basic NTSYNC driver patches are in char-misc-next and currently not the entire complete series.
Very nice. Gaming on Linux slowly starts to be no problem at least for me.
It shouldn’t speed up anything on Proton, since it already uses f-sync, which gives the same speedup, but breaks some apps, which is why Wine wasn’t using it and ntsync was created as an alternative.
Having a QR code with a link to the error code or at least a way to search it is an excellent UX thing, especially for those who are less accustomed to dealing with Linux kernel panics
See the comments in response to mine on how this might look
I like it when my crashes come with a plain text explanation of what caused the crash. It just seems simpler to me than having to deal with some barcode fuckery.
One doesn’t exclude the other. And if you really hate QR codes that much I’m sure there will be a flag or you can recompile the kernel without this, it’s Linux after all
Man I really hope they kill that. Its extremely user unfriendly, especially in Microsoft’s configuration where they show the bsod for 0.2 seconds for rebooting.
Well the QR code part hasn’t even been submitted to the maintainers yet AFAIK, so there’s still time to change, and I’m sure it’ll be configurable so you either get a stack trace or a QR code.
Yeah, it almost looks like you’d be able to run things faster than natively on windows, which is why I’m suspicious (not that it’s a lie just that the numbers lack context). It doesn’t say what the numbers represent I think?
The numbers represent FPS. Now, Wine is not an emulator and the Linux architecture and it’s system calls are written in C, so it’s not uncommon to find games running better on Linux nowadays. Pretty sure all games can be optimized to be run better than on windows.
Add comment