

Proton has been defaulting to NTSYNC automatically for me since it was fully implemented?
Both when I was using EndeavourOS and when I switched to Artix and manually installed Plasma.
He/Him 🏳️🌈 🏴☠️
Linux Nerd [Artix BTW] and Gay Furry. Anti-Ai.


Proton has been defaulting to NTSYNC automatically for me since it was fully implemented?
Both when I was using EndeavourOS and when I switched to Artix and manually installed Plasma.


Same happened to be back when I tried the flatpak version.
Edit: Also to add to this, I had issues recently when trying to load a game with Proton from a drive I had manually mounted but not added to fstab yet. I tried a Linux native game on the same drive and it worked however.


I’m probably overstating, I admit to spending too much time talking to “capital G gamers” and a while back something went around about “We’ve reached the limit of x86 and Nvidia’s new ARM processors will be the future of PC gaming”
I’ve had at least two separate people go on long winded rants about it to me, so now my eye twitches anytime I hear someone mention it.


More people need to take this into account.
Even until semi-recently a lot games were 32bit only. Luckily we got projects like WOW64 for Wine/Proton that’s helping assure compatibility of older games in the future when 32bit libraries are completely dropped by most distros. But that still takes time to work out all the edge cases.
Same thing for the people heavily pushing for everyone to SWITCH TO ARM RIGHT NOW!
I like Arm (I’d prefer RISC-V) but I like video games being preserved, playable and as easily accessible as possible for people more than any shiny new hardware.
There’s an option in Mangohud called ‘winesync’ that tells you what it’s using.