HP's Reverb VR Pro Headset

[imacken]

The WMR for SteamVR from last night reset the config file again, so an edit is required to switch on Motion Reprojection.

[Baldrick33]

The WMR for SteamVR from last night reset the config file again, so an edit is required to switch on Motion Reprojection.

Thanks for the heads up. I didn't get an update and according to the WMR for SteamVR news page the stable version is now a newer build than the beta!

 

https://steamcommunity.com/app/719950/allnews/

[imacken]

Yep, not even sure how to find out what version I'm using!

 

EDIT: Just looked at the exe file, and it says 1.1.177.0, so I guess the beta and release are the same version for the moment.

Edited March 15, 2020 by imacken

[Baldrick33]

Yep, not even sure how to find out what version I'm using!

 

EDIT: Just looked at the exe file, and it says 1.1.177.0, so I guess the beta and release are the same version for the moment.

Sounds right, I just opted out of beta and validated and the only thing that changed was the settings file.

[majapahit]

When using fpsVR this will manage Motion Reprojection whatever the default.vrsettings says

[imacken]

When using fpsVR this will manage Motion Reprojection whatever the default.vrsettings says

Eh no, it won't!

[majapahit]

Eh no, it won't!

Eh, does with me. It's ON while .default has //

[imacken]

Eh, does with me. It's ON while .default has //

 

Where are you setting it as 'ON' in fpsVR?

[majapahit]

Where are you setting it as 'ON' in fpsVR?

'Advanced' I think I remember, ' .. global' 'override Default Global' 'Toggle ..' or something

[imacken]

'Advanced' I think I remember, ' .. global' 'override Default Global' 'Toggle ..' or something

 

That's what I thought. Those settings - as stated on the fpsVR screen - are for Vive/Vive Pro/Index and ASYNC REPROJECTION only. They do not apply to the Reverb which uses Motion Reprojection.

 

The only control over MP on the Reverb and other WMR headsets is via the default.settings file.

[Eaglewings]

That's what I thought. Those settings - as stated on the fpsVR screen - are for Vive/Vive Pro/Index and ASYNC REPROJECTION only. They do not apply to the Reverb which uses Motion Reprojection.

 

 

 

The only control over MP on the Reverb and other WMR headsets is via the default.settings file.

I have the odyssey +.

I found out from my experience that changing settings in vr default setting file is counter productive.

So I have it as it is and vr game play is good without major issues.

[imacken]

I have the odyssey +.

I found out from my experience that changing settings in vr default setting file is counter productive.

So I have it as it is and vr game play is good without major issues.

 

What do you mean ‘counter productive’?

[Eaglewings]

What do you mean ‘counter productive’?

Play becomes jittery and micro stuttering becomes frequent with some artifacts.

Happened the two times I uncommented those lines in 2.5.5 and reverted back to default. Never bothered to change anything again just not to upset present vr play.

I can say I followed the instructions but it did not give me desired results compared to leaving it as is.

[imacken]

Play becomes jittery and micro stuttering becomes frequent with some artifacts.

Happened the two times I uncommented those lines in 2.5.5 and reverted back to default. Never bothered to change anything again just not to upset present vr play.

I can say I followed the instructions but it did not give me desired results compared to leaving it as is.

 

That's really strange, as the whole point of MP is to smooth/fill out the frames to avoid exactly what you say you are seeing, i.e. jittering and microstuttering.

[Eaglewings]

That's really strange, as the whole point of MP is to smooth/fill out the frames to avoid exactly what you say you are seeing, i.e. jittering and microstuttering.

Correct

I do not really know why it did that in my case. Since I play with no issues with default settings, I do not really bother changing anything in there.

I just go by the rule of do not fix it if not broken for now.

[Baldrick33]

Correct

I do not really know why it did that in my case. Since I play with no issues with default settings, I do not really bother changing anything in there.

I just go by the rule of do not fix it if not broken for now.

I guess there is a reason it is only accessible by editing a text file and the term is still labelled "driver_Holographic_Experimental". It seems to work well with the Reverb, maybe the Od+ has different results?

[imacken]

I guess there is a reason it is only accessible by editing a text file and the term is still labelled "driver_Holographic_Experimental". It seems to work well with the Reverb, maybe the Od+ has different results?

 

Good point!

[speed-of-heat]

i had pretty good results with it on the O+ when i had one, though i didn't leave it on Auto and forced it on

[Eaglewings]

I will give it a try again and compare results.

It can only get better for me if all goes well.

There may have been other limiting factors then as I tried it on bit weaker system (laptop). Now will see how it goes with the desktop system.

[speed-of-heat]

i have to say i think your 1060 is under powered to drive a Reverb though, especially in DCS. the recommended minimum graphics card is a 1080 for the reverb (https://support.hp.com/sg-en/document/c06325736)

Edited March 17, 2020 by speed-of-heat

[Eaglewings]

i have to say i think your 1060 is under powered to drive a Reverb though, especially in DCS. the recommended minimum graphics card is a 1080 for the reverb (https://support.hp.com/sg-en/document/c06325736)

I am using odyssey + now and the 1060 is holding up on average settings.

The plan is to see how the new 3000 series Nvidia gpu card for the year will perform and then do an upgrade. Only then will I be looking at the Reverb.

[speed-of-heat]

I am using odyssey + now and the 1060 is holding up on average settings.

The plan is to see how the new 3000 series Nvidia gpu card for the year will perform and then do an upgrade. Only then will I be looking at the Reverb.

 

and you were posting it in the Reverb thread ... because ?

[Eaglewings]

and you were posting it in the Reverb thread ... because ?

Someone mentioned that tweaking vr. Settings works generally for wmr headset.

 

Please no intention to derail the thread guys.

[Hiromachi]

I've got Reverb few days ago and started flying with some tweaking but feel quite confused with settings, especially since older tweaking tutorials (like: https://vr4dcs.com/2019/09/10/reverb-settings-for-dcs/) are not perfectly applicable due to changes in the SteamVR.

So I'm trying to focus on SteamVr and ingame settings, but not sure whether this Reprojection still has to be enabled via file editing or perhaps it's now a default feature.

[imacken]

I've got Reverb few days ago and started flying with some tweaking but feel quite confused with settings, especially since older tweaking tutorials (like: https://vr4dcs.com/2019/09/10/reverb-settings-for-dcs/) are not perfectly applicable due to changes in the SteamVR.

So I'm trying to focus on SteamVr and ingame settings, but not sure whether this Reprojection still has to be enabled via file editing or perhaps it's now a default feature.

 

The main difference - in theory - is that you can now choose SteamVR or WMR to do the Motion Reprojection. I say ‘in theory’ as I can’t get it to work in SteamVR as I can’t get DCS into the application list in Video settings.

The default is now ‘disabled’ in the default.settings file. The other options are the same, i.e. auto or motionprojection.

If you want to try and use MP in SteamVR, then you have to comment out the relevant line in the settings file