3.2.2 (the "You guys are amazing" update) (Patreon)

I have incredible news, and it's all thanks to you guys! We made the world's Top 50 for the "Games" category O_O

https://graphtreon.com/top-patreon-creators/games

It's even more amazing because we're not talking about a "VR games" category, but games in general! That gives me great hopes that we're going to save VR yet, save it both from the publishers and studios that are too afraid to invest in it anymore and from the bitter people who spend their days posting everywhere that VR is dead (╯°□°)╯︵ ┻━┻

It's so not dead! What a beautiful community you're making with your support and enthusiasm!!

Update Mar 20: If you're a Pimax user and want to get rid of the black hairline on the left and right sides of the HUD, AND you feel comfortable with hex editors like HxD, you can patch the pi_server.exe file yourself: while PiTool is not running, just modify the byte at offset C97CB from 04 to 03 and save the file. Please only attempt this if you know what you're doing, otherwise you run the risk of breaking your Pimax software installation. You've been warned!

Update Mar 19: I found the exact point where pi_server.exe (a component of PiTool) messes up the alpha calculation for the overlay layer, i.e., the root cause for the Pimax black square of infamy :-P
Release 3.2.2 attached below pre-corrects for that bug, allowing you to enjoy RDR2 and the other games with your Pimax headset. The thin black line at the outer borders of the HUD remains, as it can't be pre-corrected (see above for a new method to get rid of it that unfortunately involves hex-editing the server).
I hope that when the lockdown in China relents, the Pimax engineering team will roll up their sleeves and actually get around to fixing their bugs, because it's unfair toward the majority of my Patrons that I should waste so much development time tracking down and working around a plethora of vendor-specific issues that Valve and Oculus have never had, or solved years ago. Maybe it's just me, but I believe that when your market is a niche inside a niche, and your headsets command a high price and are mostly intended for power users in search of the best possible experience, your software should be more robust and performant than the competition's, and not the other way around!

Update Mar 17: There was a problem with release 3.2.0 where the new code for detecting and activating Oculus emulation mode on Pimax headsets would erroneously trigger with the original Oculus Rift S, making it impossible to enter VR with it. The issue is fixed with release 3.2.1 attached at the bottom. If you're already on 3.2.0 and don't have a Rift S you don't need to download again, as nothing else has changed.

Here it is finally, 3.2.2. So many changes, we're gonna need a post timeline:

• new Patrons please see the main CP2077 post for full instructions and lots of details;
• refer to the troubleshooting post if you have problems;
• the previous update post explains all you need to know about aiming down the sights;
• here's how to make ReShade effects work in VR;
• the full list of fixes and improvements in update 3.2.2 was already posted here;
• how to use the new custom resolution and target PPD functions (with video);
• how to use the new HUD interaction paradigm (a.k.a. tilt 'n slide, full gameplay demo).

Remember to run RealConfig after unzipping the new archive into the game executable folder, otherwise the update won't work!

Pimax users: as anticipated, this release brings a major performance update. Pimax headsets are not very common, so I'm in fact not sure whether the awful performance that I was seeing compared to other, more mainstream headsets like the Quest 2 or the Index was specific to my system or widespread. Anyway, on my PC I'm now seeing major improvements. [Thank you for the performance reports, guys!!! It seems that the improvements are indeed visible across all systems!]
Unfortunately the Pimax driver for SteamVR has some severe bugs that I cannot work around. I reported those issues to their team in December, but since then they have gone completely silent on me. So, in order to reap the benefits, I had to force the headset to work in Oculus emulation mode.
If you never used Oculus emulation mode in the past on your system, you will need to install the Oculus runtime. You don't have to create an account with Oculus/Facebook/Meta; just finish the installation and reboot.
If the Oculus runtime is already installed on your PC, you won't need to do anything else as the mod will automatically inject the necessary libraries; just make sure that PiTool is running as usual. However, you will notice that when the game starts you will get a UAC prompt to run something called "RealFluid"; you'll have to wait for the prompt and click on it on the desktop before putting on the headset. It's a nuisance, but without official support it's the best I can do. The prompt won't appear again until you quit PiTool, even if you restart the game.