Jump to content

HP Reverb Stutters


Bones308th

Recommended Posts

Hey Guys,

 

Just got the HP Reverb, and I’m having stutter issues. I have a i9-9900K with the NVidia 2080Ti setup, and is stuttering quite a bit. Especially noticeable when moving my head from side to side, in the pit! I’ve checked settings but kind find if this is a limitation with the headset, or if I’m missing some settings. I also noticed my frame rates bouncing all over the place, from 45 all the way up to 90! This is a show stopper for me with this headset, as it gives me a light headache. It sucks! I was running the Oculus Rift S and that thing was glass smooth. Please let me know what I can check, because I’m seriously considering returning it. Thangs guys!

 

Ray

Link to comment
Share on other sites

A couple of things:

 

Are you running the stable or beta versions of SteamVR and Windows Mixed Reality for SteamVR?

 

Have you edited the settings file in WMR to enable reprojection?

AMD 5800X3D · MSI 4080 · Asus ROG Strix B550 Gaming  · HP Reverb Pro · 1Tb M.2 NVMe, 32Gb Corsair Vengence 3600MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · VIRPIL T-50CM3 Base, Alpha Prime R. VIRPIL VPC Rotor TCS Base. JetSeat

Link to comment
Share on other sites

Motion smoothing is for other devices like the Vive & Index.

 

I found SteamVR Beta to worsen performance and have rolled back to the stable version. Worth a try.

AMD 5800X3D · MSI 4080 · Asus ROG Strix B550 Gaming  · HP Reverb Pro · 1Tb M.2 NVMe, 32Gb Corsair Vengence 3600MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · VIRPIL T-50CM3 Base, Alpha Prime R. VIRPIL VPC Rotor TCS Base. JetSeat

Link to comment
Share on other sites

"driver_Holographic_Experimental" : {

// Motion reprojection doubles framerate through motion vector extrapolation

// motionvector = force application to always run at half framerate with motion vector reprojection

// auto = automatically use motion reprojection when the application can not maintain native framerate

"motionReprojectionMode" : "auto",

 

// Automatic motion reprojection indicator to display the mode currently selected

// green = off because application can render at full framerate

// light blue = on because application is cpu bound

// dark blue = on because application is gpu bound

// red = off because application running at less than half framerate

"motionReprojectionIndicatorEnabled" : true,

Ryzen 3700X, 2080ti, 32GB, HP Reverb, Rift S, Thrustmaster Warthog, Crosswind, SFX-100 motion rig :thumbup:

Link to comment
Share on other sites

"driver_Holographic_Experimental" : {

// Motion reprojection doubles framerate through motion vector extrapolation

// motionvector = force application to always run at half framerate with motion vector reprojection

// auto = automatically use motion reprojection when the application can not maintain native framerate

"motionReprojectionMode" : "auto",

 

// Automatic motion reprojection indicator to display the mode currently selected

// green = off because application can render at full framerate

// light blue = on because application is cpu bound

// dark blue = on because application is gpu bound

// red = off because application running at less than half framerate

"motionReprojectionIndicatorEnabled" : true,

 

Where would one make this change...location? Thanks

Link to comment
Share on other sites

Thanks guys. I’ll check it out tomorrow. I put back my Rift S, and is silky smooth. I mean, I occasionally get some stutters every now and then, but nothing compared to the Reverb. One thing I did noticed is the Rift S maintains a constant 40 FPS. On the Reverb my frames are all over the place between 90 and 45. I had the same issue with the first generation Rift, but I managed to lock it at 45 FPS with the Oculus Tray Tool. I think the jumping around in frame rates, may be what’s causing the stutters. Again guys, thanks. I’ll test it in the morning. I’ll post back here.

 

Ray

Link to comment
Share on other sites

Bones, do you see the little color indicator in the top left of the HMD for the status of Reprojection? It's green when reprojection is off light/dark blue when it's on and red when the FPS is below the reprojection minimum. If not, reprojection is probably not in use.

Link to comment
Share on other sites

Thanks guys. I’ll check it out tomorrow. I put back my Rift S, and is silky smooth. I mean, I occasionally get some stutters every now and then, but nothing compared to the Reverb. One thing I did noticed is the Rift S maintains a constant 40 FPS. On the Reverb my frames are all over the place between 90 and 45. I had the same issue with the first generation Rift, but I managed to lock it at 45 FPS with the Oculus Tray Tool. I think the jumping around in frame rates, may be what’s causing the stutters. Again guys, thanks. I’ll test it in the morning. I’ll post back here.
As I mentioned I have gone back to the stable versions of both WMR & SteamVR, because I found the FPS was jumping around. Bear in mind every time you change between WMR stable & beta the settings file needs to be edited to enable reprojection. Hard to believe this isn't a GUI option but so be it!

AMD 5800X3D · MSI 4080 · Asus ROG Strix B550 Gaming  · HP Reverb Pro · 1Tb M.2 NVMe, 32Gb Corsair Vengence 3600MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · VIRPIL T-50CM3 Base, Alpha Prime R. VIRPIL VPC Rotor TCS Base. JetSeat

Link to comment
Share on other sites

Bones, do you see the little color indicator in the top left of the HMD for the status of Reprojection? It's green when reprojection is off light/dark blue when it's on and red when the FPS is below the reprojection minimum. If not, reprojection is probably not in use.

 

I don’t see a color indicator on the Reverb Pro.

 

Bones

Link to comment
Share on other sites

Okay. Something I noticed. On the SteamVR Settings menu. On the lower left hand side, I’m showing:

 

Dashboard Off

Chaperone Bounds Of

Reprojection On

Motion Smoothing Off

 

When I launch DCS, I’m left with:

 

Dashboard Off

Chaperone Bounds Off

 

Does this mean anything?

 

Bones

Link to comment
Share on other sites

Use this instead

 

"motionReprojectionMode" : "motionvector",

 

Do not use a second monitor, turn it off if you do.

System specs: Intel i9-9900k OC 5.1Ghz, 32 GB PC3200 G.SKILL TridentZ RGB RAM, Asus Strix 2080 TI OC SLI, Asus Z390 Workstation Pro, 970 EVO 1TB M.2 PCIe NVMe and many other SSDs, Alienware 3418DW Widescreen 120 Hz G-Sync Monitor, Corsair H150i PRO RGB CPU Cooler

 

Flightgear: HP Reverb Pro, Samsung Odyssey +, Virpil MongoosT-50CM2 Grip & T-50CM2 Base, TM Warthog, TM TPR Rudder, TM Cougar MFDs, Jetseat, Trackir 5, Sennheiser Game One Headset

Link to comment
Share on other sites

I don’t see a color indicator on the Reverb Pro.

 

Bones

Just to clarify the indicator is in the top left of the display as an overlay, so you should see it while flying.

 

If it not there then it sounds as if the right file hasn't been edited correctly.

AMD 5800X3D · MSI 4080 · Asus ROG Strix B550 Gaming  · HP Reverb Pro · 1Tb M.2 NVMe, 32Gb Corsair Vengence 3600MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · VIRPIL T-50CM3 Base, Alpha Prime R. VIRPIL VPC Rotor TCS Base. JetSeat

Link to comment
Share on other sites

Just to clarify the indicator is in the top left of the display as an overlay, so you should see it while flying.

 

If it not there then it sounds as if the right file hasn't been edited correctly.

 

Copy man. Thank you. I’ll look for that later today and let you know. At least for now, I haven’t noticed it in game. I contacted HP tech support today about the issue. They seemed to confirm the issue, and are working on a solution. I gave them the link to this forum as well.

 

Bones

Link to comment
Share on other sites

Use this instead

 

"motionReprojectionMode" : "motionvector",

 

Do not use a second monitor, turn it off if you do.

 

huh? Why?

Have two monitors + VR, never any issues.

Ryzen 3700X, 2080ti, 32GB, HP Reverb, Rift S, Thrustmaster Warthog, Crosswind, SFX-100 motion rig :thumbup:

Link to comment
Share on other sites

Okay guys. Here’s the latest: I removed the “//“, and it did make a noticeable difference. However, I’m still getting them. The frame rate changes are narrower after the edit for sure. In other words, instead of swinging wildly between 45 and 90, they’re +/- 5 FPS or so, when the frame rates are somewhere in between 90 and 45. When I get low to the ground and frames are locked at 45, is a smooth experience. Is there any way of locking the frames at 45 FPS? If I can do that, I think it’ll cure the problem.

 

Bones

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...