Tweaking the HP Reverb

[Gunnars Driver]

Here is that guide:

https://steamcommunity.com/games/719950/announcements/detail/3229520292654229103

 

Note that commenting out the line doesn't disable reprojection though. There is currently no way to fully disable reprojection with WMR. Btw, if you're not adverse to tweaking this, you should try the latest Windows Insider build, which changes up the WMR quality options for potential performance gains. There's a guide in this forum.

 

Quote from that linked page:

 

When motionReprojectionMode is set to "auto", motion reprojection will turn on automatically when a game is rendering too slowly to maintain 90 FPS. When a game begins to maintain 90 FPS or starts rendering at less than 45 FPS, motion reprojection will turn off.

 

Instructions to enable automatic motion reprojection

 

You can opt-in to this mode by updating the MixedRealityVRDriverresourcessettingsdefault.vrsettings file in the MixedRealityVRDriver install folder.

 

Make sure you have opted into the Windows Mixed Reality for SteamVR Beta using the instructions on the enthusiasts guide.

Close SteamVR if it is running

Edit the file at "C:Program Files (x86)SteamsteamappscommonMixedRealityVRDriverresourcessettingsdefault.vrsettings" (Path will be different if Windows Mixed Reality for SteamVR was installed to a different library)

Add this line just below "driver_Holographic_Experimental" as shown in the example below "motionReprojectionMode" : "auto",

Restart SteamVR with Windows Mixed Reality

 

Example 1: Enabling automatic motion reprojection

 

"motionReprojectionMode" : "auto",

 

Example 3: Disabling motion reprojection

 

// "motionReprojectionMode" : "auto",

 

The guide is old(2018). In all new firmware the line already exists. Just delete or add the //.

 

 

Its crystal clear really. Automatic or off.

There is off course a third setting, enable it always, but it would be rare to use I guess.

 

I do not really see how you can understand this any other way?

 

When it is in auto reprojection is always:

-Off when PC delivers 90fps or more( of course ad the PC has one new frame for each frame to show)

-On when PC delivers between 45 to 90 fps, to lock fps at 45 and reusing each frame once, making it 90 fps to the VR headset( but only 45 true new)

-Off when producing less than 45 fps as there isnt enough frames to make 90 if doubled anyway.

 

[Edit]Reprojection is either on, or off. There is no in between. You can let the computer do all 90 frames for itself or you can use reprojection and then you only use 45 fps from the computer( like vsync), and you double this frames.

Reprojection can not be anything else than on or off.

Edited February 1, 2020 by Gunnars Driver

[Baldrick33]

Here is that guide:

https://steamcommunity.com/games/719950/announcements/detail/3229520292654229103

 

Note that commenting out the line doesn't disable reprojection though. There is currently no way to fully disable reprojection with WMR. Btw, if you're not adverse to tweaking this, you should try the latest Windows Insider build, which changes up the WMR quality options for potential performance gains. There's a guide in this forum.

I am not sure what you mean by not being able to fully disable reprojection? In my own use of having it on (not commented out) or off (default - commented out) the fps show it at 45 or 90 with it on and anything from 90 and below with it off. It certainly seems to work like a switch to me.

 

There maybe a brief indication of another value as it switches between 45 & 90 but that is all.

 

Regardless of fps value the sensation of anything below 90 with it off is very noticeable. With it on it really is smooth unless it drops below 45.

 

For me at least DCS is much smoother at 45 than some other games (e.g. some racing sims) where I try to avoid dropping below 90 wherever possible.

[speed-of-heat]

I am not sure what you mean by not being able to fully disable reprojection? In my own use of having it on (not commented out) or off (default - commented out) the fps show it at 45 or 90 with it on and anything from 90 and below with it off. It certainly seems to work like a switch to me.

 

There maybe a brief indication of another value as it switches between 45 & 90 but that is all.

 

Regardless of fps value the sensation of anything below 90 with it off is very noticeable. With it on it really is smooth unless it drops below 45.

 

For me at least DCS is much smoother at 45 than some other games (e.g. some racing sims) where I try to avoid dropping below 90 wherever possible.

 

I have the same experience, with either:

 

- "motionReprojectionMode" : "auto", it gives me either 90 (though to be fair not on my box and settings) or 45, if you force low settings in DCS you can see this in action..

- "motionReprojectionMode" : "motionvector", it gives me only 45

 

with these lines commented out it will give me any value below 90 depending on the terrain/environment/mission, but it can be choppy

Edited February 1, 2020 by speed-of-heat

[sirrah]

I installed my Reverb yesterday and while I'll tinker with all different setting along the way, I've one question that may have past here already. (couldn't find exactly this through a forum search).

 

When in game (DCS or that other flightsim with the name of an old Russian plane ;)) light colors, such as clear skies and clouds, cause a slight flickering. I did set WMR "experience options" to 90Hz.

 

I only see this flickering effect when looking a very bright colors. Inside the cockpit, or looking at the ground I don't see it.

 

Not sure if it's of any importance, but my FPS seem pretty nice between 45 and 90, so I hardly think it's a performance issue.

 

Any ideas which setting could cause/solve this flickering issue?

[eaglecash867]

I am not sure what you mean by not being able to fully disable reprojection? In my own use of having it on (not commented out) or off (default - commented out) the fps show it at 45 or 90 with it on and anything from 90 and below with it off. It certainly seems to work like a switch to me.

 

There maybe a brief indication of another value as it switches between 45 & 90 but that is all.

 

Regardless of fps value the sensation of anything below 90 with it off is very noticeable. With it on it really is smooth unless it drops below 45.

 

For me at least DCS is much smoother at 45 than some other games (e.g. some racing sims) where I try to avoid dropping below 90 wherever possible.

 

I remember finding the Steam article he seems to be referencing over and over again. One important detail that he missed, however, is that they stated the "on by default" asynchronous reprojection feature only applies to non-WMR headsets. I'm not going to go find it for him though, because my Reverb shows the same results seen by all of us here (except him for some reason) when I edit that key line in the vrsettings file for SteamVR For WMR. I rarely stare at FPS counters, but with the line commented out, I get FPS in the 60s to 70s, but when I rapidly move my head from side to side, the image in the cockpit is smeared and not smooth. Take the // out of the equation, FPS goes to a solid 45, and that same head movement yields smooth motion of the cockpit image.

 

Its very strange how the one person out of all of us here who insists that the rest of us are suffering from some sort of delusion seems to also be the only one here who can't seem to get this feature to work. I'm pretty sure I know the key step that he's missing in his setup, but I'm not going to bother with that. There's a clear lack of attention to detail in certain individuals that just can't be overcome, and quite frankly, its exhausting.

 

I'll just go back to enjoying the hell out of the A-10C and F-16C in VR. :D

[eaglecash867]

I installed my Reverb yesterday and while I'll tinker with all different setting along the way, I've one question that may have past here already. (couldn't find exactly this through a forum search).

 

When in game (DCS or that other flightsim with the name of an old Russian plane ;)) light colors, such as clear skies and clouds, cause a slight flickering. I did set WMR "experience options" to 90Hz.

 

I only see this flickering effect when looking a very bright colors. Inside the cockpit, or looking at the ground I don't see it.

 

Not sure if it's of any importance, but my FPS seem pretty nice between 45 and 90, so I hardly think it's a performance issue.

 

Any ideas which setting could cause/solve this flickering issue?

 

Hi Sirrah,

 

Are you seeing that flickering in the sky and clouds as you're moving your head? Do the clouds appear to suddenly disappear and reappear, or is it something different? One other possibility might be your in-game gamma setting. I had trouble with that for a while, until I finally made the "discovery" (heh...something I should have already known, but didn't) that I could hit the escape button and bring up the graphics settings menu while paused in flight. You can't adjust everything on that menu while in flight, but the gamma slider works. It made a huge difference in the color quality to set it that way. Try playing around with the in-game gamma slider while in flight and see if you can get a result that looks good to you.

[sirrah]

Hi Sirrah,

 

Are you seeing that flickering in the sky and clouds as you're moving your head? Do the clouds appear to suddenly disappear and reappear, or is it something different? One other possibility might be your in-game gamma setting. I had trouble with that for a while, until I finally made the "discovery" (heh...something I should have already known, but didn't) that I could hit the escape button and bring up the graphics settings menu while paused in flight. You can't adjust everything on that menu while in flight, but the gamma slider works. It made a huge difference in the color quality to set it that way. Try playing around with the in-game gamma slider while in flight and see if you can get a result that looks good to you.

 

Thanks for the response Eaglecash, I'll try turning down gamma and see if it helps a bit

 

I think though, I might have found the true issue here. My GTX 1080ti has three 1.4 display ports, which only support 60Hz apparently...

 

Surprises me that I didn't read about this earlier on this forum, as many more people here are using a 1080ti in combination with a Reverb. Or am I missing something here?

 

 

 

 

Edit:

hmz... Just tried changing the Gamma slider in DCS, but it doesn't seem to respond at all. Normally you see gamma go up and down while sliding, but nothing's happening.. haha... next issue... I'll get there at some point

Edit2:

Gamma issue solved.. Apparently it doesn't work in the DCS menu screen :)

Edited February 1, 2020 by sirrah

[speed-of-heat]

In the wmr portal, check settings for the hmd, make sure it's set to 90mhz under experience

[sirrah]

In the wmr portal, check settings for the hmd, make sure it's set to 90mhz under experience

 

I did, it is on 90Hz

[speed-of-heat]

Well not sure what to tell you, I’m on a1080ti and operating at 90hz, have you tried different ports

[Gunnars Driver]

I did, it is on 90Hz

 

And some time the WMR bug set the headset to 60hz despite the settings is 90.

Solution is to pull out the headset connector and put it back, enabling 90hz as it should.

 

Only time I saw flickering is when headset unintentionally get to 60hz.

[sirrah]

Well not sure what to tell you, I’m on a1080ti and operating at 90hz, have you tried different ports

 

:doh:

 

 

I would hug you you if you were here!! :thumbup: (in a non gay kind of way)

 

 

Why I didn't try this myself, is beyond me... Perhaps because it doesn't make sense..

 

Anyways... The flickering is gone now!! :pilotfly:

[speed-of-heat]

:doh:

 

 

I would hug you you if you were here!! :thumbup: (in a non gay kind of way)

 

 

Why I didn't try this myself, is beyond me... Perhaps because it doesn't make sense..

 

Anyways... The flickering is gone now!! :pilotfly:

 

That's alright m8, hugs are fine! Glad you are up and working

[eaglecash867]

 

 

 

Edit:

hmz... Just tried changing the Gamma slider in DCS, but it doesn't seem to respond at all. Normally you see gamma go up and down while sliding, but nothing's happening.. haha... next issue... I'll get there at some point

Edit2:

Gamma issue solved.. Apparently it doesn't work in the DCS menu screen :)

 

That's odd. The DCS menu gamma slider is what I've always used. Looks like you're getting things figured out though. I was so frustrated with my Reverb at first, I almost sent it back. Just turned out to be a few things I had to do differently than what I was doing with my Rift.

[sirrah]

Two more tweaking questions from a Reverb rookie:

 

1. Although I love my new Reverb and I wouldn't want to go back to my Rift cv1, I did notice the Reverb has a pretty small sweet spot. Can this be improved somehow by altering settings?
   
2. This might be somehow related to my first question, but I noticed that outside the sweet spot area, I see a small sort of rainbow-effect (sorry I don't know the technical term). The more I look to the edge of the screen, the "worse" it gets. I didn't have this with my Rift cv1. Is this typical for the Reverb, or can the effect be reduced by some software setting?
   

[epolta]

Two more tweaking questions from a Reverb rookie:

 

1. Although I love my new Reverb and I wouldn't want to go back to my Rift cv1, I did notice the Reverb has a pretty small sweet spot. Can this be improved somehow by altering settings?
   
2. This might be somehow related to my first question, but I noticed that outside the sweet spot area, I see a small sort of rainbow-effect (sorry I don't know the technical term). The more I look to the edge of the screen, the "worse" it gets. I didn't have this with my Rift cv1. Is this typical for the Reverb, or can the effect be reduced by some software setting?
   

I removed the factory facial interface and added my own foam piece attached to the factory velcro along the edge of the headset. Comfort isn't quite as nice and I had to loosen the straps a bit, but now my eyes are much closer to the display. This gives me better perceived FOV (I can check six and see more without requiring the Linda Blair, and it gives me a noticeably better (bigger) sweetspot.

[eaglecash867]

Two more tweaking questions from a Reverb rookie:

 

1. Although I love my new Reverb and I wouldn't want to go back to my Rift cv1, I did notice the Reverb has a pretty small sweet spot. Can this be improved somehow by altering settings?
   
2. This might be somehow related to my first question, but I noticed that outside the sweet spot area, I see a small sort of rainbow-effect (sorry I don't know the technical term). The more I look to the edge of the screen, the "worse" it gets. I didn't have this with my Rift cv1. Is this typical for the Reverb, or can the effect be reduced by some software setting?
   

 

1. The Reverb does have a smaller sweet spot. I've found that getting it positioned on my face properly is a little difficult, but once I get it positioned, the small sweet spot isn't as much of a problem.

2. Make sure you have removed the protective film from the lenses. That was one of the things that got me when I first got mine. :doh: :D

[sirrah]

I removed the factory facial interface and added my own foam piece attached to the factory velcro along the edge of the headset. Comfort isn't quite as nice and I had to loosen the straps a bit, but now my eyes are much closer to the display. This gives me better perceived FOV (I can check six and see more without requiring the Linda Blair, and it gives me a noticeably better (bigger) sweetspot.

 

That's clever. Was it difficult/risky to remove the original facial interface?

 

 

2. Make sure you have removed the protective film from the lenses. That was one of the things that got me when I first got mine. :doh: :D

 

Hehe, I saw you mention that in an earlier post somewhere and double checked mine :P

[epolta]

That's clever. Was it difficult/risky to remove the original facial interface?

 

 

 

 

Hehe, I saw you mention that in an earlier post somewhere and double checked mine :P

Not risky or difficult. The facial interface is made to remove so it can be cleaned/replaced. The only tricky part is the velcro tends to want to peel off the HMD when you try to remove it, so just go slow, and press the velcro back down again. I may end up removing HP's velcro and replacing it with my own strips eventually.

[sirrah]

Not risky or difficult. The facial interface is made to remove so it can be cleaned/replaced. The only tricky part is the velcro tends to want to peel off the HMD when you try to remove it, so just go slow, and press the velcro back down again. I may end up removing HP's velcro and replacing it with my own strips eventually.

 

I see. I think I'll might do the same eventually :thumbup:

 

Now that I got your attention :P... Here's another question :)

 

On vr4dcs.com I've read that it's best not to use the DCS ingame supersampling and better to use SteamVR supersampling

 

Adjust the SS in Video SS (Global) or in the Application SS section specific to your game in the SteamVR Application Settings. Not both. Both is a multiplier and will zap your horsepower ASAP.

 

Applying these settings in SteamVR seems to have less of a drag on your CPU and GPU than using the PD Slider in the DCS VR Tab. PD does essentially the same thing in DCS but not as efficiently.

 

So, is the red circle in my screenshot showing the SS bar?

 

And if so, isn't this only working for the Steam version of DCS? Because I'm using standalone

 

 

 

 

Oh, and do I want to enable MotionReprojection? I have no idea what it does. Well... I googled it, but I still don't understand its purpose.

Edited February 3, 2020 by sirrah

[Gunnars Driver]

I

 

So, is the red circle in my screenshot showing the SS bar?

 

And if so, isn't this only working for the Steam version of DCS? Because I'm using standalone

 

 

Oh, and do I want to enable MotionReprojection? I have no idea what it does. Well... I googled it, but I still don't understand its purpose.

 

 

Yepp, its that dot @100%. Thats fine. You dont need Steam version, it works without. I dont have the Steam DCS.

 

 

Motionreprojection: Yes, you would like (need) to use it.

 

As the Reverb have 90hz frequency as default(if setup correctly, 60hz also availabe), your computer need to feed the reverbs with 90fps. The computer will not be able to do this all the time, actually quite seldom. So, instead of getting a stuttering experience when the computer cannot feed the reverb with 90fps it will switch to using 45 fps from the computer and double each of these, so there will be sent 90 frames but each is sent twice.

The recomendation is setting reprojection to auto.

[sirrah]

Motionreprojection: Yes, you would like (need) to use it.

 

As the Reverb have 90hz frequency as default(if setup correctly, 60hz also availabe), your computer need to feed the reverbs with 90fps. The computer will not be able to do this all the time, actually quite seldom. So, instead of getting a stuttering experience when the computer cannot feed the reverb with 90fps it will switch to using 45 fps from the computer and double each of these, so there will be sent 90 frames but each is sent twice.

The recomendation is setting reprojection to auto.

 

Could it be, that Motionreprojection will also fix this issue?

 

When flying around I notice that when I make a rapid movements, like a fast roll for instance, I see some sort of stutter when looking at ground scenery. Even though my fps counter shows 45-90 without drops. Stutter might not be the correct term actually, but it's just not smooth when looking at the ground.

 

(I would just try it out, but I'm not at my pc for a few days and I was just curious)

[speed-of-heat]

Just to be clear.

 

This should be set in the default.vrsettings file, \steamapps\common\mixedrealityvrdriveer\resourses\settings file

[sirrah]

Just to be clear.

 

This should be set in the default.vrsettings file, \steamapps\common\mixedrealityvrdriveer\resourses\settings file

I assume if I follow the instructions from vr4dcs.com, I'd be ok, right?

 

 

So can I expect this to help smoothing out the issue I described above?

[speed-of-heat]

yes and yes, though “renderTargetScale” : 2.0 doesn't do anything anymore, that's legacy