886
Wine 11 rewrites how Linux runs Windows games at the kernel level, and the speed gains are massive
(www.xda-developers.com)
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
No memes/shitposts/low-effort posts, please.
Help:
Launchers/Game Library Managers:
General:
Discord:
IRC:
Matrix:
Telegram:
What is often overlooked
Ntsync is great and there will be performance improvement. But not exactly
massiveWhat’s massive is the need for clicks
Well said
That's not the only thing that's massive.
How about their gigantic ego?
I don't think that's overlooked at all. 99.9% of people using WINE/Proton aren't going to have any idea what fsync is, and almost nobody not using
proton-cachyosis going to use it. fsync, itself a workaround, is niche within what's already a niche.From what I found online, Steam enables esync by default, and fsync if your kernel supports it.
Lutris has both options nowadays in the runner settings. Idk if they’re both enabled by default, but in my case they’re enabled. ymmv there.
source
any idea how this would compare to starting steam directly from a display manager using gamescope as the compositor?
I’m imagine gamescope is the best-case, since there’s no other apps or visual effects.
What are the kernel requirements? Is it something any random Debian user is likely to have, or do you need to be compiling it yourself?
From the article:
So since Jan 2022, it’s been in the stable Linux kernel. For Debian and its derivatives, it would be included beginning with Bookworm.
So basically, both esync and fsync are enabled by default for almost everybody.
Assuming that most non-technical users (who wouldn’t research and enable it) are probably using Wine/Proton through Steam: yeah.
Speaking, although I've heard the term thrown around a lot. Can I get a layman's overview?
I think it's pretty well described in the article of the post
You're right, it is.
You can try all you want, but you will never get me to read the articles before commenting.
i use ntsync whenever i can, but i've only had linux (cachyos) on my gaming rig since like august. that said, i believe one of their recent updates made ntsync the default for proton-cachyos
Fsync maybe not but AFAIK esync is widely used. On some protondb pages there's a hint to disable esync, not the other way round. And while esync is not as performant as fsync, it is still much better than vanilla
It's worth noting that the new sync implementation shouldn't cause any of the compatibility problems esync and fsync ran into, so it's a worthwhile upgrade from a stability viewpoint even if a user won't see huge performance gains.
These don't sound massive to you?
You won't see those because most probably you are already using one of other *sync
It should still fix minor stuttering that some gets get on Linux, which will be pretty huge.
I remember hearing that Ntsync isn't even faster than fsync in general use, just in some rare corner cases
This is true and expected, the point of NTSYNC was to be a more faithful emulation of Windows synchronization primitives, so increased compatibility and correctness. If it's ever faster than esync or fsync it's just a bonus. It's on par generally, though.
Wine Is Not an Emulator.
Okay. Parts of WINE emulate parts of Windows in order to function. The NTSYNC driver emulates NT synchronization primitives.
People on Lemmy are fucking dumb, wow. The word WINE literally stands for “Wine Is Not an Emulator”. It’s a translation layer.
I'm aware. You seem to be equivocating on the word "emulate." Nobody called WINE an emulator. The design and behavior of NTSYNC is meant to mimic that of NT synchronization primitives.
It fixed the lag spikes I experienced playing some of the older Call of Duty titles so it's overall been a huge upgrade for me.