HP's Reverb VR Pro Headset

Sounds Good

 

The Loadscreen flickering is a SteamVR Bug and I hope they find a Solution. I close my eyes while loading.

 

But anyway, I'm 100% Happy with the Reverb and DCS today. Its unbelievable in combination with the Motionsimulator and Simshaker, how good a Home-Simulator can be today

 

This was a very good Year for us

 

Merry Christmas

 

Gesendet von meinem SM-G973F mit Tapatalk

Yeah, thanks for the suggestions regarding motionvector and Nvidia settings.

As for the screen instability, I don't think it's Steam VR that's causing the multiplayer issues. After selecting my airframe in the menu the screen jumps all over the place through the briefing screen and for quite a while in the pit.

Not the end of the world of course, but it is quite unpleasant.

Edit- Have just ordered another 16GB of RAM to take me up to 32GB- Will report back if it improves things.

ordered the reverb pro from Amazon UK last night, (Sold my Amazon, not another retailer). I suppose i will get a V2 Reverb, correct?

ordered the reverb pro from Amazon UK last night, (Sold my Amazon, not another retailer). I suppose i will get a V2 Reverb, correct?

You should do, if not just rma it. The questionable serial numbers were updated:

Yeah, thanks for the suggestions regarding motionvector and Nvidia settings.

 

 

As for the screen instability, I don't think it's Steam VR that's causing the multiplayer issues. After selecting my airframe in the menu the screen jumps all over the place through the briefing screen and for quite a while in the pit.

 

 

 

Not the end of the world of course, but it is quite unpleasant.

 

 

Edit- Have just ordered another 16GB of RAM to take me up to 32GB- Will report back if it improves things.

Gesendet von meinem SM-G973F mit Tapatalk

The Loadscreen flickering is a SteamVR Bug and I hope they find a Solution. I close my eyes while loading.

It drives me crazy also. ; >

On a plus note, I noticed a marked improvement in FPS stability by replacing the "auto" with "motionvector" in the projection settings and also changing the low latency mode to ultra in the Nvidia Control Panel.

Thanks for this! While I couldn't find the 'motionvector' in any settings, I did change the 'low latency mode' to 'Ultra' from 'Off' and what a huge difference! Super smooth now and much higher fps. Amazing how much difference just one setting can make when you don't really know the in's and out's of what your doing.

Thanks for this! While I couldn't find the 'motionvector' in any settings, I did change the 'low latency mode' to 'Ultra' from 'Off' and what a huge difference! Super smooth now and much higher fps. Amazing how much difference just one setting can make when you don't really know the in's and out's of what your doing.

XX:\SteamLibrary\steamapps\common\MixedRealityVRDriver\resources\settings.

I assume you have already enabled reproduction here. If so just replace the “auto” with “motionvector” in the line that you originally removed the quotes on.

Close down and restart Steam VR and your FPS should now be locked at 45 instead of fluctuating on the rare occasions that it can hit 90.

XX:\SteamLibrary\steamapps\common\MixedRealityVRDriver\resources\settings.

 

I assume you have already enabled reproduction here. If so just replace the “auto” with “motion vector” in the line that you originally removed the quotes on.

 

Close down and restart Steam VR and your FPS should now be locked at 45 instead of fluctuating on the rare occasions that it can hit 90.

Thanks for pointing me to the file in question oz555, I had a look and I think I see what you mean, as for assuming I have enabled reproduction I didn't even know all that existed or even what it means to be honest. but a good test tonight hosting with just the low latency mode turned to ultra has made an incredible difference and one I was able to pass on to a squad mate. I will try the motion vector but have to admit I am getting uncomfortably out of my comfort zone here in understanding what I am doing. Might have to be a case of if it aint broke don't fix it going forward. The low latency mode to ultra made such a huge difference for me and overall I was happy with it before this except for the ghosting and dropping out/double screen shot flickering/'waiting for DCS' crap that was happening, now, none of that at all!

Thanks dude! :thumbup:

Thanks for pointing me to the file in question oz555, I had a look and I think I see what you mean, as for assuming I have enabled reproduction I didn't even know all that existed or even what it means to be honest. but a good test tonight hosting with just the low latency mode turned to ultra has made an incredible difference and one I was able to pass on to a squad mate. I will try the motion vector but have to admit I am getting uncomfortably out of my comfort zone here in understanding what I am doing. Might have to be a case of if it aint broke don't fix it going forward. The low latency mode to ultra made such a huge difference for me and overall I was happy with it before this except for the ghosting and dropping out/double screen shot flickering/'waiting for DCS' crap that was happening, now, none of that at all!

Thanks dude! :thumbup:

I understand where you are coming from, but you really do want to enable motion projection, otherwise you’ll get variable frame rates all over the place! Personally, I use auto as that locks you into 45fps, but does allow 90 when conditions allow.

Early morning typo for me there. Should read Reprojection not reproduction

If you follow the setup steps in the link below, you should be well on your way...

https://www.google.co.uk/amp/s/vr4dcs.com/2019/09/10/reverb-settings-for-dcs/amp/

Cheers guys I really do appreciate your help and information. I'll look into it over the next few days but I am so happy with what I have now. I did go through the whole Thuds setup before I got the reverb just so I was on the right foot to start with and it has been a pretty seamless process since then, its getting the final little things checked off that will make all the world of difference is where I'm at now. My biggest hurdle is the terminology and understanding what it means and where it is applicable, but slowly getting there and if I try one thing at a time I am getting incremental improvements at each stage. Super happy with where I am at with my Reverb now that's for sure.

I'm trying to activate motionvector mode with no success. I change the default.vrsettings file but when I fly the fpsVR shows that the FPSs are varying, so I assume that it is in auto mode. Here is the content of my file:

{

"driver_Holographic" : {

// Increase back buffer size so that larger superscale values do not get a resolution reduction

“renderTargetScale” : 2.0

},

"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" : "motionvector",

// 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,

// Motion indicator size and position in 0-1 space

"motionReprojectionIndicatorSize" : 0.015,

"motionReprojectionIndicatorXPosition" : 0.3125,

"motionReprojectionIndicatorYPosition" : 0.3125,

// Some people may experience increased discomfort such as nausea, motion sickness, dizziness,

// disorientation, headache, fatigue, or eye strain when using thumbstick controls in Windows Mixed Reality.

//

// Setting thumbstickControlsMoveEnabled to true may cause application compatibility issues

"thumbstickControlsTurnEnabled" : false, // true = use thumbsticks for artificial turn, false = default application thumbstick behavior

"thumbstickControlsMoveEnabled" : false, // true = use thumbsticks for artificial move, false = default application thumbstick behavior

"thumbstickControlsReversed" : false,

"thumbstickTurnSmooth" : false,

"thumbstickDeadzone" : 0.25,

// During some transitions (typically entering Home), controller events start accumulate and the system has difficulties to catch up

// Settings a mximum age for a contoller input allows ensuring that the events queue does not grow indefinitely

"obsoleteStateMaxTimeInSeconds": 1.0,

// Disable DX12 support

"forceDisableDX12": false

},

"NoInterEyeRotation" : {

"battlezone_dx11.exe" : true,

"battlezone_dx12.exe" : true,

"DOOMVFRx64.exe" : true,

"Fallout4VR.exe" : true

}

}

Did you shut down then restart Steam VR?

Would suggest a pc restart if possible.

Cheers guys I really do appreciate your help and information. I'll look into it over the next few days but I am so happy with what I have now. I did go through the whole Thuds setup before I got the reverb just so I was on the right foot to start with and it has been a pretty seamless process since then, its getting the final little things checked off that will make all the world of difference is where I'm at now. My biggest hurdle is the terminology and understanding what it means and where it is applicable, but slowly getting there and if I try one thing at a time I am getting incremental improvements at each stage. Super happy with where I am at with my Reverb now that's for sure.

As mentioned above, editing the reprojection file in the WMR for Steam VR file is necessary for a smooth (ish) experience.

Did you shut down then restart Steam VR?

 

Would suggest a pc restart if possible.

Yes, I did. Actually I reinstalled steamvr, because I was using beta version, and I wanted to be sure that I am using stable version.

I’m not at my pc for a few days, so I can’t compare my file with yours I’m afraid. Looks about right though. Hopefully somebody can compare for you.

I also reinstalled WMR for steamvr and now it seems to work. At least in my rig I cannot see so much difference between auto and motionvector modes.

The Difference is,that DCS Runs Static and Smooth @45FPS. With my System,it would be switching at high Altitude to 90FPS than back to 45 and again and again. It performing better with Motionvector.

Gesendet von meinem SM-G973F mit Tapatalk

I also reinstalled WMR for steamvr and now it seems to work. At least in my rig I cannot see so much difference between auto and motionvector modes.

Unless your system can do 90fps at times - which mine does quite a lot especially in NTTR - you won’t see much of a difference as you will be locked at 45fps (or occasionally less) in both modes.

Unless your system can do 90fps at times - which mine does quite a lot especially in NTTR - you won’t see much of a difference as you will be locked at 45fps (or occasionally less) in both modes.

Exactly, it is what I experiment.

Funny,

If I activate reprojection, I got all the jaggies and micro stuttering possible.

Leaving it off gives me a smooth ride.

Price to pay is some ghosting of course when abeam some other planes. It shows of course during dogfight and I still need to find a way to get rid of this.

It might get better with updates (WMR, steam...) in time and with new future vid cards. Who knows...

So I just enjoy the smooth ride and the amazing cockpit quality offered by the Reverb and learn to live with a bit of ghosting...

Got it.

 

And yeah, ED will run fine on the reverb, I can push ED to stupid high settings now. Worked fine on my old system too.

Just installed reverb too coming from cv1 and i too noticed i can push in higher graphics having less issues... But this is not normal, in every other game i had to lower graphics to maintain 90fps.. why DCS is different?

Just installed reverb too coming from cv1 and i too noticed i can push in higher graphics having less issues... But this is not normal, in every other game i had to lower graphics to maintain 90fps.. why DCS is different?

I dunno, DCS is just special I guess. :music_whistling:

Just installed reverb too coming from cv1 and i too noticed i can push in higher graphics having less issues... But this is not normal, in every other game i had to lower graphics to maintain 90fps.. why DCS is different?

I am surprised using a steam supersampling of 250%, dcs PD of 1.0, high graphics setting and still able to play stable in dcs.

Downside is I have to put off MSAA with shimmering from far object.

I am only using an i5 7600k, gtx 1060g and SSD.

The experience has be good with dcs but not without stuttering when playing America Truck simulator on a 250% supersampling.

250% supersampling.

250% supersampling is insane