SteamVR terrible frame rate, critical error

[Jay Smizzle]

I'm having lots of problems with SteamVR and my new HP Reverb G2. If I load into Half Life Alyx I get terrible frame rates and after a minute it freezes and SteamVR displays a critical error. With other apps it runs fine for a few minutes and then gets progressively worse until the frame rate is so bad it's unusable. However, I can load iRacing which also loads SteamVR and I have no issues at all. This problem only affects me when I load a VR game or app through Steam.

[AnimulMuthr]

same here only it eventually crashes all my games

[wabajak13]

I don't know if this will help you, but I found that going into the Developer settings in the SteamVR overlay and changing the default runtime from WMR to SteamVR has helped performance and stability and just about everything else.

[Shotoku]

Thanks for the heads up, will try that, my G2 is a delicate and temperamental piece of hardware....feel it need to toughen up and do it's job!

[Eric Clapped 'Em]

Any updates to this problem? I just got my G2 today and am running into the same exact problems. Really bad framerates and such when loading a game, WMR freaking out causing my headset to spin and controllers to fly around, SteamVR menu drops frames massively in some games. Totally unplayable.

[Cruisix]

From the HP + MS site:

WMR render target in SteamVR? This is always changing as SteamVR and WMR update themselves. SteamVR reports the total framebuffer, which in VR is larger than the panel resolution to allow for last millisecond adjustments to the displayed frame to match any movement of the user’s head from when the frame was rendered. So, no need to update it manually.

For me, on a RTX 3090, autmatic resolution resulted in about 3700x3700 PER EYE!!!

Only way to fix this and get better framerates in steamVR games is to set a custom res per eye at about 50%

Stupid i know.. but try it out.

[Michiko_X]

Having the same issues with freezes and crashes on SteamVR with my Reverb G2. When I can even get into SteamVR or run a VR game or app in Steam with my headset, everything looks and plays great. Then it'll crash with an unexpected error and I have to restart Windows to get things working again. I know other WMR headset users have had this issue with SteamVR, but the Reverb G2's issues are more pronounced. This needs to get fixed.

[Del_Pierro]

Same here - G2 and RTX 3080, SteamVR overlay leads to an instant crash of everything VR related. Tried beta versions etc., noting works. Really frustrating experience, Oculus was miles better than this.

[JcTrickY]

Same here 3080 msi trio x and constant crash on half life alyx.
On top of that my joystick block on my left controller...
I am very sad

[JcTrickY]

Can i use the hp without steam vr to play vr game like open vr ?

[EXPERIMENTONGOD]

Same here RTX 2080 with HP Reverb G2, SteamVR crashing very frequently, sometimes even Steam Home glitches like crazy and doesn't work. I tried downgrading Nvidia drivers and several different USB ports on my PC. Terrible experience. Needs fixing ASAP.

[EXPERIMENTONGOD]

Cruisix の投稿を引用：

From the HP + MS site:

WMR render target in SteamVR? This is always changing as SteamVR and WMR update themselves. SteamVR reports the total framebuffer, which in VR is larger than the panel resolution to allow for last millisecond adjustments to the displayed frame to match any movement of the user’s head from when the frame was rendered. So, no need to update it manually.

For me, on a RTX 3090, autmatic resolution resulted in about 3700x3700 PER EYE!!!

Only way to fix this and get better framerates in steamVR games is to set a custom res per eye at about 50%

Stupid i know.. but try it out.

Actually after extensive testing it seems that is the issue. SteamVR FAILS miserably if the render resolution is "too high". If you leave it at AUTO with an HP Reverb G2 and a good GPU you WILL have problems. In my case (RTX 2080) "Auto" sets the resolution to 94% (3064 x 3000). Steam Home plays fine, Alyx plays fine at that resolution.

Until all hell breaks loose and Steam Home Starts glitching. I can exit SteamVR Home and re-enter and it's always glitched. The Fix?, lowered render resolution to 20% and suddenly SteamVR Home stops failing.

TL;DR

UNFORTUNATELY THIS IS "AMATEUR LEVEL TRASH SOFTWARE" (WMR for SteamVR and/or SteamVR itself).

If you have an HP Reverb G2 lower the resolution for massively improved stability

EDIT:

Actually "auto" resolution uses an internal benchmark ran by SteamVR each time it is opened.

Check this file:

..\Steam\config\steamvr.vrsettings

at the beginning I can see:

"GpuSpeed" : {
"gpuSpeed0" : 1602,
"gpuSpeed1" : 1608,
"gpuSpeed2" : 1604,
"gpuSpeed3" : 1557,
"gpuSpeed4" : 1566,
"gpuSpeed5" : 1551,
"gpuSpeed6" : 1335,
"gpuSpeed7" : 1351,
"gpuSpeed8" : 1590,
"gpuSpeed9" : 1501,
"gpuSpeedCount" : 10,
...
"gpuSpeedHorsepower" : 1561,

That "gpuSpeedHorsepower" value is what SteamVR uses to determine "Auto" resolution. Problem is that the value it uses is way too high for stability in games like HL: Alyx or even Steam Home.

[offall]

EXPERIMENTONGOD の投稿を引用：

Cruisix の投稿を引用：

From the HP + MS site:

Check this file:

..\Steam\config\steamvr.vrsettings

at the beginning I can see:

.........
"gpuSpeedHorsepower" : 1561,

That "gpuSpeedHorsepower" value is what SteamVR uses to determine "Auto" resolution. Problem is that the value it uses is way too high for stability in games like HL: Alyx or even Steam Home.

This is the best answer i found, thanks! mine is set as following:
"gpuSpeedHorsepower" : 1326,
"gpuSpeedRenderTargetScale" : 0.89999997615814209

Constantly crashing /blue screening, but change it to 50% does have worse graphics, any suggestion what's good setting?

[Ober]

EXPERIMENTONGOD の投稿を引用：

Cruisix の投稿を引用：

From the HP + MS site:

WMR render target in SteamVR? This is always changing as SteamVR and WMR update themselves. SteamVR reports the total framebuffer, which in VR is larger than the panel resolution to allow for last millisecond adjustments to the displayed frame to match any movement of the user’s head from when the frame was rendered. So, no need to update it manually.

For me, on a RTX 3090, autmatic resolution resulted in about 3700x3700 PER EYE!!!

Only way to fix this and get better framerates in steamVR games is to set a custom res per eye at about 50%

Stupid i know.. but try it out.

Actually after extensive testing it seems that is the issue. SteamVR FAILS miserably if the render resolution is "too high". If you leave it at AUTO with an HP Reverb G2 and a good GPU you WILL have problems. In my case (RTX 2080) "Auto" sets the resolution to 94% (3064 x 3000). Steam Home plays fine, Alyx plays fine at that resolution.

Until all hell breaks loose and Steam Home Starts glitching. I can exit SteamVR Home and re-enter and it's always glitched. The Fix?, lowered render resolution to 20% and suddenly SteamVR Home stops failing.

TL;DR

UNFORTUNATELY THIS IS "AMATEUR LEVEL TRASH SOFTWARE" (WMR for SteamVR and/or SteamVR itself).

If you have an HP Reverb G2 lower the resolution for massively improved stability

EDIT:

Actually "auto" resolution uses an internal benchmark ran by SteamVR each time it is opened.

Check this file:

..\Steam\config\steamvr.vrsettings

at the beginning I can see:

"GpuSpeed" : {
"gpuSpeed0" : 1602,
"gpuSpeed1" : 1608,
"gpuSpeed2" : 1604,
"gpuSpeed3" : 1557,
"gpuSpeed4" : 1566,
"gpuSpeed5" : 1551,
"gpuSpeed6" : 1335,
"gpuSpeed7" : 1351,
"gpuSpeed8" : 1590,
"gpuSpeed9" : 1501,
"gpuSpeedCount" : 10,
...
"gpuSpeedHorsepower" : 1561,

That "gpuSpeedHorsepower" value is what SteamVR uses to determine "Auto" resolution. Problem is that the value it uses is way too high for stability in games like HL: Alyx or even Steam Home.

well. NO!

I upgraded from 1080ti to rtx3070 recently and 1080ti did not have any kind of problems with the same resolution. With the rtx3070 I am having massive stuttering as soon as I open steam overlay during a game and it never goes well after that. SO, this is definitely a driver problem.

[Dedlike]

and it seems like noone can be botherd to fix it since it has been that way for quite some time now

[Torzi]

Have you tried the new hotfix driver from nvidia (461.33)? This problem is listed in the patch notes.