Win 10 Vsync forced off possibly after using Coop LAN server for first time

[Michael Z Freeman]

Hi,

When I recently went back to playing PR I was starting Coop games from the client. Vsync was always on.

However recently (this could be related to using the included batch file to start a local only Coop server) I cannot ever get Vsync to turn on. It's is turned on in the launcher.

I notice "Launcher.con" in the "settings" directory is included by "init.py" (or whatever its called). Launcher.con contains the Vsync setting which is now always 0 even if I edit it to 1. If I make the file read only then PR throws an error and won't start.

Is this a bug ? Anyway, what can I do to make sure Vsync definitely gets turned on ? I actually know how to do this by adding "renderer.vsync 1" to "GameLogicInit.con" but of course if I do this PR fails on file verification

Tearing really de-immerses me

[[R-DEV]​AlonTavor]

Cannot replicate, vsync gets set for me properly. Are you sure you're editing the right profile in launcher?

Python has nothing to do with any .con files, ever.

[Michael Z Freeman]

Originally Posted by AlonTavor

Cannot replicate, vsync gets set for me properly. Are you sure you're editing the right profile in launcher?

Python has nothing to do with any .con files, ever.

Thanks. It was the wrong profile ... Think I was assuming that "Always use this profile" would auto select that profile in settings.

(BTW It was "init.con" that I meant, that had the reference to Launcher.con).