Hotfix for 60 fps cap (NVIDIA cards)

This is an emergency release to work around an issue that is ruining the mod experience in VR for many of you.

There seems to be a bug in recent NVIDIA drivers that severely limits the performance of windowed applications. The driver is erroneously forcing V-Sync on, even if the application explicitly asked for an uncapped frame rate. That results in serious ghosting/jitter/judder in the best case, and can also lead to the eye images randomly being drawn out of place or even swapped. As you know, that very quickly leads to motion sickness in VR.

The specific scenarios that trigger the bug are still a bit unclear. From the reports I have received, and from my own personal experiments, several different factors appear to be involved:

• the game exceeding some unknown framerate threshold while in windowed mode;
• the presence of multiple monitors in the system;
• the game window straddling different monitors vs being visible only on one;
• one or more monitors in the system being G-Sync capable;
• the fact that an HDMI TV is/was connected to the system;

and possibly other, yet undiscovered ones.

I don't expect this bug to be fixed anytime soon by NVIDIA, as it only affects windowed applications, and it's pretty hard to reproduce. Luckily there is a workaround, which is to force V-Sync off in the driver itself, either globally or for each specific game.

This release adds a component to RealConfig which will automatically take care of implementing the workaround in case you have an NVIDIA card. If you are affected by the bug, download the archive below to update your R.E.A.L. VR installation, and remember to run RealConfig again: it will tweak the driver profile for the game to make sure that the game runs with V-Sync off (as it should).

Should you later want to play the game in pancake mode and with V-Sync activated, just open the NVIDIA Control Panel, navigate to "Manage 3D settings" and then to the "Program Settings" tab, and find the game you'd like to play flat. Restore its default profile to allow V-Sync again.

The only other change in this release is a minor fix for CP2077 that allows you to play Roach Race in VR.

Hope this helps all of you who have been affected by this nasty issue!!!

Update 1: it seems that forcing V-Sync off in the driver is preventing Cyberpunk 2077 from starting altogether for some of you. I just hate these driver quirks. Anyway, if you have this problem, you should be able to undo the changes very easily: open the NVIDIA Control Panel, navigate to "Manage 3D settings" and then to the "Program Settings" tab, and find Cyberpunk 2077 in the list. Press "Restore" and then after confirming the warning press "Apply" otherwise the restore won't, erm, apply. Of course that will leave you once more with the 60 fps cap issue if you suffered from it before. In the next few days we'll try together to find a solution that works for everybody.

Update 2: I suspect the freeze at startup might be due to the launcher. If you're affected, please try adding "--launcher-skip -skipStartScreen" without the quotes to your launch options and let me know if that changes anything!

Update 3: It seems that my hotfix is causing problems for several people, who can no longer launch the game(s) at all, even in 2D. To avoid further problems, I reverted the link below to the previous version of the mod. I absolutely cannot reproduce the freeze-at-start issue here however, so I need a few volunteers to help me get to the root cause. If you have an NVIDIA system that was affected by both problems (60 fps cap with 8.0.1, games not launching with 8.1.0), you're good with computers, and you have plenty of time to spare, please get in touch with me in the comments below or with a DM. The "plenty of time" part is crucial, because these kind of problems that involve the drivers can only be diagnosed with lots of reboots, reinstallations, tweaks and blind tries :-(

Update 4: Okay, I should have nailed the issue that was causing the games to freeze at launch for some of you. Apparently one of the latest Windows updates must have tightened security around driver profiles, with the result that a simple operation that used to succeed now silently fails, and what's worse is that it leaves the profile in an inconsistent state. That inconsistent state is what was preventing the games from creating the Direct3D device at startup. Anyway, please download the new 8.2.0 release attached below and update. When you run RealConfig after the update, it will fix the broken profile and also force V-Sync to off as expected. Remember that each game needs a separate installation, as RealConfig only modifies the specific game profile and doesn't touch the global driver settings.