New Reverb VR user with questions

[Notso]

Unless you are running a magic super computer; i would recommend it be left on.

 

There is no magic switch you have to edit default.vrsettings with notepad ++

 

{
   "driver_Holographic" : {
   },
   "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
       [color="Magenta"]"motionReprojectionMode" : "auto",[/color]

       // 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,
       "thumbstickUseForSystemMenu": true,

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

       // Feature still in development
       "enableSkeletalInput":  true
   },
   "NoInterEyeRotation" : {
       "battlezone_dx11.exe" : true,
       "battlezone_dx12.exe" : true,
       "DOOMVFRx64.exe" : true,
       "Fallout4VR.exe" : true
   }
}

 

simply it helps your computer when you can't quite make 90FPS, by "guessing" every other frame, so you generate 45 fps, but it will be very smooth at 45fps, sometimes you will get some graphical artifacts, like a blurring or flickering of an object as a result.

 

Thanks, I think I have it on now. I simply removed the // in front of the motion reproduction mode : auto. I assume that is correct?

 

If I did it correctly, it seems to be working nicely. I’m running on my laptop at the moment while I await my desktop computer to show up in my 40’ cargo container from overseas. It’s an MSI Titan GT75 with an i9-8950 and an RTX-2080 MOBILE. It runs well, but I can’t run the setting quite as high as my desktop rig in the specs below.

 

The nice thing is the Reverb is running nicely and I really like it. The resolution is great. Well worth the money.

[speed-of-heat]

Sounds good.

[Gunnars Driver]

Thanks, I think I have it on now. I simply removed the // in front of the motion reproduction mode : auto. I assume that is correct?

 

Yes, correct.

 

To confirm that its actually is working in "auto" you can look at the fps counter in dcs or fpsVR.

 

With no reprojection(= off) the frame rate will be either 90fps or exactly what your rig is able to produce if it is lower than 90fps. You can see virtually any number, depending on the load on the CPU/GPU due to the Graphics drawn at the moment.

 

With reprojection in auto, you should see either 90fps when the rig can deliver, or 45 as soon as 90 fps can not be reached. In game, this means mostly Reading 45fps very steady for most gamers. If 45fps in not reach due to too hard load the fps counter again will show the fps actually delivered as reprojection is off below 45fps.

 

In the DCS fps-counter with reprojection on there might be a very brief moment when the counter leaves 90 fps and goes down to 45fps, and vice versa but only for som tents of a second. Buth you shouldnt read it continlously varying at any number.

 

We have seen some people not getting reprojection to work, why I can not tell.