Version 1.4.1 EARLY ACCESS (debug) (Patreon)

Hi! As I kind of expected, version 1.4.0 was a bumpy ride. Many people seem to have the game running correctly in VR, with DLSS and all the bells and whistles. However, others are reporting a few different problems, some of them blocking issues, and of course I want to solve all of them and have the mod work at its best for everybody.

This 1.4.1 version is just a debug release. It brings nothing new to the table, so if your game is running fine you don't need to upgrade. When all the problems are solved, I will make a new "normal" release for everybody. On the contrary, if you are unable to run the game in VR, please install this debug release so we'll have more meaningful logs and with a little luck I'll be able to understand what's going wrong for some of you.

1. If, after installing 1.4.1, you cannot even open the mod overlay (i.e., the mod doesn't seem to attach to the game) please do the following: quit the game; download the extra .bat file that I'm attaching down below, "RealCleanRunAsAdmin.bat", and put it into the game folder where RDR2.exe is; as the name says, run "RealCleanRunAsAdmin.bat" as administrator (you have to right-click on it to select that option). The problem that this file is meant to solve is an unexpected issue originating from the fact that, during the past few days when the game had to be downgraded to continue playing in VR, many of you decided to move the game installation to another folder or drive. That was not a supported scenario, due to a bug (or "feature") in the system Vulkan loader which gets confused if a layer with the same name is listed as being present in different folders. "RealCleanRunAsAdmin.bat" cleans up all traces of previous mod layer installations found on the system, just like I advised a few of you to do manually with Regedit. I can't expect everybody to be confident to use Regedit though, that's why I'm including this new utility file. After running this file, which will basically remove every past or present installation of the mod from the Vulkan system, please remember to run "RealConfig.bat" as usual, from the actual folder where you now want to run the game.

2.If instead you can open the overlay just fine, but the "Start VR" button is missing from the "R.E.A.L. VR" tab and the game doesn't appear in the headset, simply install 1.4.1, run RealConfig.bat, launch the game and let it get to the initial menus, before loading the Story, then quit. You should now have a RealVR64.log file in the game folder. Open it with Notepad, copy all its contents to the clipboard, go to https://pastebin.com , paste the log contents into the large blank box, then click on "Create New Paste". That will bring you to a new page in the browser, with a URL like https://pastebin.com/abc123de. Copy that URL and put it in your comment or reply so I can take a look at your log and hopefully understand what is going wrong on your system.

3. Some people do have both the overlay and VR working, but the view jitters because they're using a WMR headset like the Reverb G2. Due to a bug in the SteamVR driver for WMR that MS never seems to get around to fixing properly, with WMR headsets you need to use OpenXR. Select the OpenXR renderer from the "R.E.A.L. VR" tab in the mod overlay; the mod will save and remember your choice for the next runs. If you still have jitters after that, get the OpenXR Developer Tools for Windows Mixed Reality from the Microsoft Store, and use them to check that your active OpenXR runtime is set to WMR (if it's set to SteamVR, tracking might still not work correctly). Then, in the developer settings page of the tools, you should make sure that Custom render scale is set to 100% and that Motion reprojection is Disabled.

4. If you get weird errors when starting the game, like "ERR_GFX_STATE", check that you don't have overlays or streaming applications installed and interfering. Several users have already reported that they solved their problems after removing Twitch Studio. I will try to understand what makes it incompatible with the mod, but for now the workaround is to disable/remove it.

5. I also saw several other comments mentioning sporadic or frequent crashes, trouble with image quality on the Valve Index, issues with crosshair alignment, etc. I will address all of these problems, but first I want to make sure that the game at least enters VR mode for everybody!