whitav8

As far as reprojection, you may have to reedit the default.vrsettings file

HP Reverb Consumer Version $499 at HP Store https://store.hp.com/us/en/pdp/hp-reverb-virtual-reality-headset?&jumpid=cs_con_nc_ns&utm_medium=cs&utm_source=ba&utm_campaign=&utm_content=sp&adid=73323912492362&addisttype=spla&msclkid=2278a3d8a9b918758338fe04d6313c3c&utm_term=2325123495411914

Use voice commands for complex commands - just like your new car ! Siri: Set up for ground attack, finger formation, ...

Pov1, Could you tell us what some of the key tips that maybe aren’t known to most folks are

Thanks - those screen captures were perfect - I could easily follow. Unfortunately, you might have to update those screen captures about every two days!! Differrences from my ASUS mobo with 9700K at 5Ghz + RTX2070 system: 1) Your SteamVR settings shows you at 100% but the capture shows a funny low resolution like 1608x1576 where when I look at 100% (same version of SteamVR ) I see 2204x2160 which seems correct - anyway, just noticed it 2) Nvidia CPL settings - a few are different: (my settings are shown - please comment ) Anisotropic sample optimization = off Negative LOD bias = clamp Texture filtering= High Quality VR prerendered frames = use application I have the same exact OS build - WOW Does anyone know if the IPD setting works - I don't need it - but others ask about it 3)DCS settings (mine again are shown - please comment ) Water = high Shadows = flat only Vis Range = High Resolution of cockpit = 1024 MSAA = 2X SSAA=1.5X Thanks again for an easy way to compare them - love my Reverb! Most of my flying in DCS is at 45fps reprojection = auto with kegetys patch.

Bénî2a, I would try it with a 1920x1080 monitor and no 4K - I imagine you are using up a LOT of the bandwidth of the 1080ti. Secondly, you should have the latest Nvidia driver (436.48 or newer), Mixed Reality Portal (19081.1301), SteamVR beta (1.8.16). Also make sure you are using the ONLY Display Port to connect to the Reverb without any extra connectors.

I run DCS with Kegetys patch with a 2070 (non Super ) and my Reverb at a pretty steady 45fps with reprojection=auto.

There was a lot of discussion about both physical sweet spot (how do I fit it on my head to see clearly - I have 64.5mm IPD fortunately) and then the gaze sweet spot (how clear is the display as I look to the edge of the field of view). For me, the physical sweet spot for seated VR is fine - I do have to push it around a little but maybe a little less than for the Odyssey+. The gaze sweet spot is the critical issue - how much can I see clearly so I can really read it before I have to move my whole head and re-center. My informal testing of both WWII fighters (IL-2), modern fighters (F18 - DCS and P3D) and Q400 (Aerofly FS2) airliners is the following - I get approximately 50% of total field of view away from center that is remarkably clear - crisp numbers and text in general. If the gauges outside of that are needle pointers or caution lights, I can grasp what they are indicating ( as clear as the Odyssey+ straight on was ) without changing my head position - otherwise I do move my head. As one who has worn their eyeglasses since sixth grade, I naturally move my head to center my foveal vision (about +- 5 degrees) anyway so I can carefully discern the gauge value. The center scan for most aircraft (speed, altitude, vertical velocity, heading, and possible moving map ) is all clear without moving my head! I built flight sims for big companies in my career and I know what the EFIS displays look like - just like this. For the Q400 at the left seat eyepoint, I was impressed that I could even read the right seat PFD speed and altitude numbers. The EICAS in the center, the comm panels, and even the CDU flight management display is easily read WITHOUT leaning in.

Perhaps another couple issues includes the "quality" of a pixel - how many subpixels are there and the amount of black space around them plus their light intensity and color range - and then the imperfect quality of the lenses that we look through to see those pixels at such a short range. On top of that is the amount of graphics predistortion required to make the image seem correct after all the lens distortion. A monitor doesn't have to deal with most of these issues when viewed from a couple feet. Also, due to the high graphics performance required to avoid VR sickness and to provide for smooth scene movement when turning the head, we have to make some compromises in graphics settings that we prefer to use with a monitor and non-stereo operation. It's not just pixel dimensions that make up quality. Most of the time, when we use a monitor, we are looking at about 60 degrees field of view instead of the 100 degrees in VR - this goes to the (sub)pixels per degree issue as well. Whew - I'm glad that it actually works pretty well!

I would like to know good DCS settings as well. I also have an Odyssey+ with a 5 Ghz 9700K and a RTX2070 (which is probably 60 % of a 2080ti I suppose ). I have shadows off, MSAA off, water low, etc (most very low settings ) but it just isn't smooth even with reprojection=auto. I have build 1903 and all the blurriness updates so the image is clear. Aerofly FS2 and Combat Air Patrol 2 are both silky smooth but not DCS. I am running Steam VR SS at 160% and DCS PD = 1.0

I’m also in North County with an Odyssey+ and an RTX2070. I have Aerofly FS2, IL-2, P3D as well as DCS

Go to Windows 10 Updates and check to see in the update history that you have KB4507453. You also need to be using beta for SteamVR.

Don't forget that this new version of SteamVR for WMR updated the default.vrsettings file so as to remove the reference to RenderTargetScale - and therefore turned off reprojection. We need to edit the file again. I am running the SteamVR SS at 160% with reprojection=motionvector and it seems pretty clear and side-window smooth on my Odyssey+ (9700K@5Ghz + RTX2070 ). Most instrument panels don't require leaning in anymore. I have to say that I am very impressed now with the Odyssey+ clarity. It has come a long ways from release back at Thanksgiving. I still want a working Reverb for my flight sims but the O+ blur is almost gone. This shows that the raw video content that we feed to the HMD needs to be inspected somehow - the "monitor" window doesn't cut it. Also, the fact that this video image is much clearer now points out just how important the image processing software that provides SuperSampling, antialiasing, anisotropic filtering, sharpening, FOV distortion, etc is to the final result. We were adjusting this and that and coming to the conclusion that we needed to return the HMD. I'm glad I hung in there eight months - had to do a lot on leaning in to get by.

The most recent Windows 10 update 1903 plus the KB4507453 blurriness patch had a remarkable clarity improvement for the Odyssey+ so make sure you have it. I do hate to do major Windows updates though (what do I backup??? ) The improvement supposedly was to make the RenderTargetScale that is mentioned in the SteamVR file "default.vrsettings" actually work greater than 1.25. I would love to have a working Reverb though but these clarity improvements really help.

Make sure you have the win 10 1903 update with the KB fix for blurriness. Really helps the Odyssey+ with Steam SS at 200%

try it - great clarity improvement for WMR - especially Odyssey+

I was on Windows 10 Version 1809 waiting for the clarity fix that came out yesterday. My update to 1903 surprised me initially by apparently wiping out all my Desktop icons and Documents folders. I couldn't get the WMR portal to start either so I decided to uninstall it. After rebooting my PC, everything (Desktop and Documents ) came back as before and the WMR Portal started installing itself and it remembered my boundaries. I then checked for updates and finally KB4507453 wanted to install. I checked out IL-2, DCS, P3D, and Aerofly FS2 which all seemed remarkably clearer ( the "0" zeroes seem really easy to read ) but the reprojection:motionvector seems somewhat an FPS killer but with reduced artifacting (maybe) - better with it off though. I will need to spend some time trying various combinations of SS (I use 180% and 1.25 in-game )and repro options as well as in-game graphics options. For an Odyssey+ user, the clarity seems remarkable ( Aerofly FS2 at Innsbruck especially seems much better ) - and it must be stunning with a Reverb. I do notice especially now the sweet spot effect of the Odyssey+ (I have the widmovr lenses instead of glasses ) so that I can aim the center of my VR vision at the FMS CDU and read it well without leaning but not unless it is in the center of my view. The scenery in the distance is also clearer which helps immersion.

Has anyone tried this with their Reverb? StarTech.com DisplayPort Signal Booster - DP Video Signal Amplifier - 4K 60Hz (DPBOOST) https://www.amazon.com/DisplayPort-Signal-Booster-Video-Amplifier/dp/B01IE3IAIS/ref=sr_1_3?keywords=displayport+booster&qid=1561676939&s=gateway&sr=8-3

I'm still confused about Imacken and his continued use of Win 10 (build 1903). We know there is a decidedly fuzzier image with that build and I don't think there is a hotfix available yet. I think those with build 1809 are getting a clearer image with Reverb. Yes?

Hunchy, Are you going to try to extend your Reverb cable? I've seen a Display Port booster box on Amazon but you need another booster for USB as well. I use the ValveLink (both HDMI and USB) box with my Odyssey+ - wish there was something like it for Reverb. Instead of just saying the Reverb is amazing (we know it is), please figure out an instrument on the default SU-25 or whatever that is easy to read that you know for sure we can't read without leaning in so we can tell the difference and get excited so we will spend the $650 as well !!! What is your CPU and GPU clockrate? Also, if you run it at 60Hz, tell us if you notice the flicker on bright areas. Thanks! Also, try to see how low a SuperSample you can set and still get a clear display - it would seem that the Reverb should be OK with just 2300x2300 or so - maybe depends on how much AA you use. Some of us with just a 2070 want to make it work OK. Dave

@twobells, I don't understand the HP Reverb calculation of pixels per degree. 2160 / 114 degrees = 18.9 so either the pixels per degree is less (at least horizontally ) or the field of view is. (25 ppd no way )

For the Odyssey+, someone recommended that in the starting WMR cliffhouse, just go "outside" and look up at the stars and adjust the HMD IPD wheel to where you see one particular star in focus and it feels comfortable.

One of the simplest things for me to set IPD was suggested by someone is to go outside the WMR cliffhouse, look at the stars - pick one, and then adjust your IPD wheel until the star is as clear as it can be.

The only things I would add to the above Brewnix settings (I use Shadows=flat only and MSAA 2x + SSAA@1.5) is to use motionvector: "motionReprojectionMode" : "motionvector", which gives a steady 45FPS for the Odyssey+ ( I have 9700K at 5.0Ghz and RTX2070). I do have to fiddle with eye position to get it max clear but I am satisfied - I really like the brightness and intense colors. Maybe PiMAx in the future??

@Gryzor, Thanks again for the RenderTargetScale improvement. I currently set the SteamVR global setting to 200%, the Application setting to 100%, and then use an ingame setting (if there is one, to 1.6 ==??160%) to have the clearest image on my Odyssey+ . I am running with motionvector smoothing enabled so my FPS=45 constantly and I make sure by watching the SteamVR frametime readout to be less than 16 msec or so (has to be less than 22.2 msec for all situations) as I adjust SS (and other game settings) settings. The image is quite beautiful and pretty clear (I would say a B+) One thing I wish we could try globally (SteamVR at least ) is a sharpening setting. Some of the guys that run Unreal Engine games have tried a setting called r.Tonemapper.Sharpen=1.3 ( up to 2.0) to be set in the Engine.ini file in the Users\yyy\AppData\local\xxx\Saved\Config\WindowsNoEditor directory. I think it is a post process image option and it apparently adds a little more clarity to text and textures. Let me know if you take a look. The setting must be prefaced by the following: [ConsoleVariables] THanks much Dave W.