*FIXED* Resolution Scaling and Bluescreen Crashes with HP Reverb G2

[Itama]

Hey guys!
I'm new to VR and I recently got the HP Reverb G2.
My PC Specs are as follows:
i7-9700k, RTX 2080, 32GB RAM

Now my question: What resolution scaling is recommend for my setup?

I've read many articles and user experience feedback saying they play at 70%-100% resolution with often times an inferior setup, but if I use anything above 50% resolution scaling, I often times get a bluescreens.
So is there something I am doing wrong or I am not aware of yet?
Or is my setup simply not strong enough to display the HP Reverb G2 at a higher resolution, which would be fine, since I wasn't expecting to use 100% resolution anyway, but it seems strange how apparently so many people can use a higher resolution than I do without experiencing any problems.

If you need some other information to help me with my problem, I am happy to share.

Games I tried: The Lab & Phasmophobia (Both crash constantly on anything above 60%)

I just wanna be sure if 50% is completely fine for me, so I am not loosing out on any potential.

[Itama]

I fixed it.
For everyone who wants to know what I did, here you go:

First:
https://www.reddit.com/r/HPReverb/comments/kdursz/hp_reverb_g2_bluescreen_in_headset_issue/
I did everything Greyraven91 said in his post.
This stopped the crashes in most cases.
The whole post is down below if you don't want to use the link.

Second:
In Windows Mixed Reality for SteamVR Graphic Settings I enabled Motion reprojection for my inividual App-Settings and enabled Motion smoothing (Forced) aswell in the Apps in SteamVR that I use (In the Video Settings in SteamVR)

This limit my FPS to 45, which is totally enough for me. I don't really need 90 FPS unless I wanna play some fast games.
The 45 FPS allowed me to significantly increase my Resolution Scaling.
With My Setup, I am now able to play Phasmophobia with a stable 70% Scaling (Was 40% before) and "The Lab" with 80% Scaling (Was 50% before)

I hope this helped some people!


Reference for what Motion reprojection actually does:
https://store.steampowered.com/news/app/719950/view/4034618638818063452


Reddit Post from Greyraven91:

"(...) So im 99% sure its fixed for me since i played 2 sessions with a break in between and 3 chapters in total. i just finished the game and here is my current setup:

WMR portal updated from windows store.
Windows 10 20H2 latest update.
Nvidia driver 446.14
everything closed in the background except afterburner (without riva tuner)
HP G2 steam res set to 100%
Steam SS filtering set to off
Steam VR overly set to on but render quality set to low
VR runtime in steam set to Steam VR instead of WMR ..... i know its odd but it is what it is.
no overclock on GPU, only on the CPU.
no gpu shecduling in windows.
Half life alyx set to high settings.
Steam vr home disabled.
wmr portal app res set to 720 and low details..... be careful this effect the cilffhouse setting not the VR headset setting.
wmr headset res set to native, and highest quality.
physics inside nvidia cp set to gpu.
PC power settings set to ultimate performance, set it to high if your PC dont have ultimate plane.
G2 connected using the included adapter from usb c to usb a. this could be the culprit.
installed openxr dev tool for wmr from win store and enabled use latest preview xr runtimes."

[geoff]

45fps? How don't you vomit from that? And did you ever find a way to improve your situation?

[Itama]

Originally posted by geoff:

45fps? How don't you vomit from that? And did you ever find a way to improve your situation?

I do vomit on 45 FPS nowadays xD
And yes, I managed to optimize my VR Setup, so I can usually play everything at 90 FPS.

I believe what mostly fixed it for me, was further reducing the Resolution Scaling and then using VRSS in the Nvidia Settings. This was huge for me.
Take a look at this video here to see, what I mean:
https://www.youtube.com/watch?v=4Et4GRimbIQ

After a while I also came to the conclusion, that everything that happened to me was due to HP Reverb G2 being pretty new back then and Software not being optimized for that. Just speculation on my part, but after a while I just never had any issues again.