HP's Reverb VR Pro Headset

[Naruto]

Are you running mixed reality for steamvr beta? It was only when I changed from standard to beta I got the new resolutions (74%=2160x something close)

 

Yes Im running the beta 1.6.10

[Harlikwin]

Speaking of SteamVR

 

I updated SteamVR to the beta version. But I need to be running SteamVR for WMR? Or?

 

Anyhow, on the non-beta I saw somewhere that I was running motion reprojection, but not smoothing, now that I have the beta, I can't find that same page showing that. But I see stuff locked at 45 more so I assume thats either reprojection or smoothing?

[Harlikwin]

Just got my second Reverb and I have 1903 with latest July 26 build and I also have to use 188% Steam VR to get a resolution 2204 x 2160. My new Reverb also came with cable clip too and boy oh boy the clarity is awesome. My Experience for number two is night and day from my first Reverb that had issues 10 seconds in.

 

Do you have the chromatic abberation issue? I'm wondering if my set is "special" or not.

[Naruto]

Ok I went to properties for Windows Mix Reality in steam library and check beta and it installed WMR beta to steam and now I have SS 76% as 2196x2148 resolution.

Edited July 30, 2019 by Naruto

[Naruto]

Do you have the chromatic abberation issue? I'm wondering if my set is "special" or not.

 

Not that I notice but only had it for about 30 minute an used it in DCS for about 2 minutes lol.

 

Here is the new clip

 

Edited August 2, 2019 by Naruto

[Baldrick33]

Yes Im running the beta 1.6.10

That is SteamVR beta. You need to change Windows Mixed Reality for SteamVR to beta (current version 1.0.582.). It should be in your Steam Library under software I think

[Naruto]

Do you have the chromatic abberation issue? I'm wondering if my set is "special" or not.

 

Ok after I played for a bit, I do see it ever so slightly and only at the very horizontal edge of the displays and only when I turn my eyes towards it while keeping my head straight ahead looking down the nose of the plane I'm flying. I never would have noticed it if I wasn't looking specifically for it so it not a issue for me and I think its negligible for myself. I also only see it on the canopy frame edges and not the terrain.

 

So far liking the Reverb alot more than my last one and getting about 50-65 FPS with fairly high DCS graphics settings and with 100% Steam SS and DCS PD 1.0.

 

My only complaint is it feels a little jittery when looking out the side of the canopy while banking unlike the smoothness of the Index even with 45 FPS on the Index. I dont get any ghosting but the clarity of the Reverb is 1000 times better than the Index though IMO.

 

So far no flickering and no dimming of the screens.

Edited July 30, 2019 by Naruto

[Naruto]

That is SteamVR beta. You need to change Windows Mixed Reality for SteamVR to beta (current version 1.0.582.). It should be in your Steam Library under software I think

 

Yup found it and WMR is now at beta in steam. Thank you.

[sze5003]

That doesn't solve the issue unfortuantely. It happens when trying to click on something that is at the back of the cockpit to the left or right. Stuff on the desktop gets activated at times without knowing it until you take off the VR headset!

Weird. The only time I had the issue described I took the headset off and realized I wasn't in full screen mode and the mouse had wondered out if the VR window into the desktop.

[USA_Recon]

btw, I get the wierd 'lightning' flashes when I try to turn SteamVR up to 150%. I tend to just keep it at 100%

 

I do get wierd behavior when I change the "motionReprojectionMode" setting. Sometimes the headset doesn't render the steamvr room after that - just dark with the white dot. So I have had to reboot computer/unplug device

[Tinkickef]

Speaking of SteamVR

 

I updated SteamVR to the beta version. But I need to be running SteamVR for WMR? Or?

 

Anyhow, on the non-beta I saw somewhere that I was running motion reprojection, but not smoothing, now that I have the beta, I can't find that same page showing that. But I see stuff locked at 45 more so I assume thats either reprojection or smoothing?

 

 

Motion smoothing does not work with WMR headsets. They use reprojection instead.

I ended up enabling force half rate with reprojection instead of reprojection auto. It gives good results, but still tweaking on my new build.

I still do not have the butter smoothness I had on my old rig, so something is awry. Early days yet.

Goes to show once again, it does not matter how great a rig you have, the main bottleneck in VR is not CPU or GPU, it is DCS VR optimisation.

[Naruto]

Found I can reduce the jittery effect by enabling motion reprojection in the WMR VR setting file. File is in C:\Program Files (x86)\Steam\steamapps\common\MixedRealityVRDriver\resources\settings and called default.vrsettings. Use notepad++ to edit it by uncommenting "motionReprojectionMode" : "auto",

Edited July 31, 2019 by Naruto

[Harlikwin]

Ok after I played for a bit, I do see it ever so slightly and only at the very horizontal edge of the displays and only when I turn my eyes towards it while keeping my head straight ahead looking down the nose of the plane I'm flying. I never would have noticed it if I wasn't looking specifically for it so it not a issue for me and I think its negligible for myself. I also only see it on the canopy frame edges and not the terrain.

 

So far liking the Reverb alot more than my last one and getting about 50-65 FPS with fairly high DCS graphics settings and with 100% Steam SS and DCS PD 1.0.

 

My only complaint is it feels a little jittery when looking out the side of the canopy while banking unlike the smoothness of the Index even with 45 FPS on the Index. I dont get any ghosting but the clarity of the Reverb is 1000 times better than the Index though IMO.

 

So far no flickering and no dimming of the screens.

 

Yeah its hard to see in DCS, its much easier to see in the cliff house, or better yet the WMR house with the white walls.

[Wmacky]

Not that I notice but only had it for about 30 minute an used it in DCS for about 2 minutes lol.

 

Here is the new clip

 

https://ibb.co/0mQwQKq

 

 

My new reverb didn't come with that? Where was it in the box?

 

 

Anyone else with a latest round Reverb not get one?

[aceofspades9963]

Got mine today all I can say is wow! Played from 230 until 945 with a break for food but I left it on and no issues at all.

One question does looking down in the hornet cockpit look foggy ? The ufc and all the black up front is dark but below the canopy bil it looks foggy on all colors ,is it a dcs setting or something? Its not because it isn't oled because its just in the hornet cockpit everywhere else is fine.

[aceofspades9963]

My new reverb didn't come with that? Where was it in the box?

 

 

Anyone else with a latest round Reverb not get one?

 

Mines from the 26th batch from Amazon and i didn't get that

[sze5003]

Got mine today all I can say is wow! Played from 230 until 945 with a break for food but I left it on and no issues at all.

 

One question does looking down in the hornet cockpit look foggy ? The ufc and all the black up front is dark but below the canopy bil it looks foggy on all colors ,is it a dcs setting or something? Its not because it isn't oled because its just in the hornet cockpit everywhere else is fine.

Is the headset on your face seated properly? It could be the ipd software setting that's doing that.

[Secoda]

I ran it like that for about a month and then switched it to where it is on all of the time with the other setting. It is even smoother for my setup. :smilewink:

 

Found I can reduce the jittery effect by enabling motion reprojection in the WMR VR setting file. File is in C:\Program Files (x86)\Steam\steamapps\common\MixedRealityVRDriver\resources\settings and called default.vrsettings. Use notepad++ to edit it by uncommenting "motionReprojectionMode" : "auto",

Edited July 31, 2019 by Secoda

[Secoda]

I think I read changing the gamma setting affected the washed out color appearance. Maybe it's too high. What is it set at?

 

Got mine today all I can say is wow! Played from 230 until 945 with a break for food but I left it on and no issues at all.

One question does looking down in the hornet cockpit look foggy ? The ufc and all the black up front is dark but below the canopy bil it looks foggy on all colors ,is it a dcs setting or something? Its not because it isn't oled because its just in the hornet cockpit everywhere else is fine.

[Hellcat]

I ran it like that for about a month and then switched it to where it is on all of the time with the other setting. It is even smoother for my setup. :smilewink:

 

What other setting are you talking about ?

[Secoda]

What other setting are you talking about ?

 

There are two parameters. "motionReprojectionMode" : "motionvector",

"motionvector" or "Auto". I am using "motionvector" which is on all of the time. "Auto" turns it off when it hits 90 FPS or goes below 45 FPS.

-

-

-

-

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

[Hellcat]

RGR that..thanks

[Gun Jam]

EagleCash had suggested a powered USB port for running the Reverb.

I picked up the recommended item https://www.amazon.com/gp/product/B0...?ie=UTF8&psc=1

 

 

I did this in preparation for when I actually purchase the reverb I am running the SO+ right now.

 

 

The card has the power cable plugged in and a single green led is on

 

The card has the front panel USB like 20pin connector plugged in

The card has the online driver installed for win10

Device manager recognizes the USB ports as "Fresco" or something like that

My Hotas and other items plugged into the card work normally

 

 

WMR says that an incompatible windows driver is installed and will not connect the SO+

 

 

Any Ideas?.... works again when plugged into MB usb port

 

 

Thanks

-Gun

[Naruto]

EagleCash had suggested a powered USB port for running the Reverb.

I picked up the recommended item https://www.amazon.com/gp/product/B0...?ie=UTF8&psc=1

 

 

I did this in preparation for when I actually purchase the reverb I am running the SO+ right now.

 

 

The card has the power cable plugged in and a single green led is on

 

The card has the front panel USB like 20pin connector plugged in

The card has the online driver installed for win10

Device manager recognizes the USB ports as "Fresco" or something like that

My Hotas and other items plugged into the card work normally

 

 

WMR says that an incompatible windows driver is installed and will not connect the SO+

 

 

Any Ideas?.... works again when plugged into MB usb port

 

 

Thanks

-Gun

 

Word of advise, I bought that device and it fried my trackir and a wireless USB stick the very first time I plug them into it. Good thing I was able to return everything to amazon but I would not trust a Inateck to power my $650 HMD. Im using my motherboard 3.0 USB and have had zero issues with my second Reverb so far after about 10 hours of use.

[Tinkickef]

EagleCash had suggested a powered USB port for running the Reverb.

I picked up the recommended item https://www.amazon.com/gp/product/B0...?ie=UTF8&psc=1

 

 

I did this in preparation for when I actually purchase the reverb I am running the SO+ right now.

 

 

The card has the power cable plugged in and a single green led is on

 

The card has the front panel USB like 20pin connector plugged in

The card has the online driver installed for win10

Device manager recognizes the USB ports as "Fresco" or something like that

My Hotas and other items plugged into the card work normally

 

 

WMR says that an incompatible windows driver is installed and will not connect the SO+

 

 

Any Ideas?.... works again when plugged into MB usb port

 

 

Thanks

-Gun

 

 

Gun jam.

 

Reverb is VERY sensitive to USB drivers. Go into device manager and find your new card on the list then /update driver / select driver from list on this PC.

 

Find one ending with (Microsoft) and install that.

 

You will likely find one named something like fresco logic FL1100 usb driver (Microsoft).

 

As opposed to plain vanilla fresco logic FL1100 usb driver. Which is what you likely have now.

 

Avoid ASmedia drivers like the plague unless they have (Microsoft) at the end.

Edited August 1, 2019 by Tinkickef