Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
Emulation (Games) Games

Easy NTSYNC Arrives For Steam Users With GE-Proton 10.10 28

Long-time Slashdot reader drinkypoo writes: GloriousEggroll has released GE-Proton 10.10, a heavily breathed-upon version of Valve's version of Wine used with Steam, and the big news is that it supports NTSYNC by default on supported platforms. That means amd64 systems whose kernel is built with the CONFIG_NTSYNC option, available in the 6.14 series or later or for 6.12 or 6.13 as a patch.

NTSYNC is support for certain fine-grained Windows NT scheduling primitives for Linux, the use of which improves performance and compatibility for Windows programs. Maximum performance gains range from modest to dramatic, with most programs falling towards the lower end of the spectrum, but it can substantially improve minimum frame rates for some titles. You can observe that ntsync is being used from the console output, e.g. using "tail -f ~/.steam/steam/logs/console-linux.txt". You will see messages like "wineserver: NTSync up and running!"

Easy NTSYNC Arrives For Steam Users With GE-Proton 10.10

Comments Filter:
  • by rsilvergun ( 571051 ) on Sunday July 27, 2025 @10:49PM (#65549394)
    Are turning to Linux and proton because the compatibility with Windows 11 has gotten so bad for older games
    • Re: (Score:3, Funny)

      by Anonymous Coward

      Your mom runs best on wine.

    • by tlhIngan ( 30335 ) <{slashdot} {at} {worf.net}> on Monday July 28, 2025 @12:14AM (#65549462)

      It's actually less Windows 11's fault and more the game's fault. It's just that previous versions of Windows let the game get away with bad practices like use-after-free, or assuming an allocated page will be zeroed (it would be if it's a new allocation - for security reasons, but not if a page is reused by the same process - it's just things like Windows might tend to give you a reused page rather than incur the overhead of having to visit the memory manager for a new page). Some uninitialized data structures got corrupted in this way because they were relying on the fact that somehow one part was zeroed.

      Several bugs were found of that class. Proton could easily result in the same issues since things like that are also not guaranteed by the OS.

      So it is less compatible simply because it doesn't retain the same bugs. Granted, this wasn't like Windows 95 where Microsoft needed to make sure applications ran just as they did on Windows 3.1 or DOS and they had to write compatibility shims to get around them. Though I think Microsoft also said they dumped all those shims as cruft that was really adding bugs to the code.

    • by mjwx ( 966435 )

      Are turning to Linux and proton because the compatibility with Windows 11 has gotten so bad for older games

      Dealing with MS has always been insufferable, it's just that until recently there wasn't really a good alternative.

  • ntsync (Score:5, Interesting)

    by ledow ( 319597 ) on Monday July 28, 2025 @03:30AM (#65549584) Homepage

    This nonsense again.

    It's a very niche feature that benefits only a small handful of particular games, and the other existing and competing "syncs" already do a pretty good job (and the benchmarks almost always compare having none of those enabled to ntsync, rather than actually compete).

    It rears its head every few months over the last couple of years, so I assume the person who wrote the patch has a good PR firm.

    It's always sold as some miraculous huge leap forward for Steam / Steam Deck / Proton / Wine and yet all those places say "no, not really, it helps a little for some games".

    Go read all the mailing lists about this and you'll see it's really not such a huge deal.

    At best it'll end up as a switch somewhere that, for a few games, you'll enable instead of the various other syncs that Proton is using in the wild already, but most stuff will just carry on as normal.

    It's really so much snakeoil that "gamers" with absolutely no understanding of Wine et al leap upon every time it's talked about as if it's the sole saviour of modern gaming somehow.

    • It's just one of the countless small improvements that finally resulted in Windows games running faster on Linux than Windows.

    • It's a very niche feature that benefits only a small handful of particular games, and the other existing and competing "syncs" already do a pretty good job

      It's true that the other sync options are pretty good. My fine summary stated that most titles will not receive major improvements. This sync option is better for some titles, as you say, which I see as positive. You also say it has positive effects for some titles. Thanks for agreeing.

    • It is a big thing for WINE since it is the sole version of any of the other performance solutions that have been accepted upstream in WINE. It is also the sole performant solution that is 100% compatible with how Windows handles synchronization objects (which ofc is less of a problem for games since they tend to use only a small subject of the functionality offered).
    • Woah, did an ntsync developer sleep with your wife or something?

      While it's certainly not going to double framerates in all games it's definitely not snakeoil. Some games show no improvement vs wineserver and fsync, others show fairly massive improvement; it depends on how many syscalls the game makes and the specific hardware it's running on.

      PC gamers have always been excited by free performance boosts and why wouldn't they? Some of them need to rein in their expectations, sure, but that's no reason to piss

    • by Samare ( 2779329 )

      so I assume the person who wrote the patch has a good PR firm

      It was written by https://en.wikipedia.org/wiki/... [wikipedia.org] who both market their own version of Wine and are paid by Valve to work on Proton.

    • This "nonsense" is also the solution moving forward, the other syncs are not being kept. Which means more and more of Wine / Proton is going to depend on it and the other syncs (if maintained) are going to have their work cut out for them.

      BTW: The only reason you're complaining in the first place is because you've been using some downstream build that enables patches from Wine-Staging. Yes, those builds already saw most of the performance enhancements because of the other attempts. That's what you get fro
      • by ledow ( 319597 )

        Rubbish.

        ntsync relies on a very particular kernel module being present on Linux-only systems.

        The other syncs will all have to stick around for the foreseeable, e.g. MacOS is never going to implement ntsync.

        And actual compatibility is not an issue, that's just bug-fixing. But requiring a kernel module to operate AND actually only publishing benchmarks against "no sync at all" (in effect) is disingenuous. It benefits a few apps that are in particular cases of tight CPU loops on sync calls which presume NT-s

  • It's not NSYNC.

The cost of feathers has risen, even down is up!

Working...