HP's Reverb VR Pro Headset

I guess you are on the release version of Steam WMR. That's just been brought up to the beta version I think. No changes to projection settings for me on beta.

I guess you are on the release version of Steam WMR. That's just been brought up to the beta version I think. No changes to projection settings for me on beta.

I'm definitely on beta. My point was that for me at least, there is no need to edit the reprojection file in WMR to enable reprojection anymore.

Is Steam VR now doing the job I wonder?

It's a proper faff all this fair play...

I'm definitely on beta. My point was that for me at least, there is no need to edit the reprojection file in WMR to enable reprojection anymore.

My point was/is that the beta hasn't changed. It was the release version that was updated to the last beta a couple of days ago.

No change to the beta projection settings.

My point was/is that the beta hasn't changed. It was the release version that was updated to the last beta a couple of days ago.

 

No change to the beta projection settings.

I use beta for both SteamVR and Windows Mixed Reality for SteamVR. Newest versions installed. I have removed the // from the default.settingsvr file, use "motionvector" there.

Does this mean I don't have to have activated this in this settingsfile anymore, and that I can do it in a Steam VR menu instead?

I can't seem to get it working through Steam VR settings menu.

Any reasons for using the beta files at all now?

Well, I can see no change with the settings in the latest betas (or release now). I still have to take out the '//' to get auto reprojection working.

If I don't make that edit, the situation is the same as it has always been, i.e. the fps jump around from 45-90 and moving (not turning) my head from left to right still produces horrible jumping around.

With reprojection on, I am very happy with the performance.

AFAIK, SteamVR settings for this don't work with WMR headsets.

A good reason for sticking with the SteamVR betas - like DCS - is to make use of any new options, improvements etc. before they move to the release version. SteamVR beetas are in my experience very stable, and if they are not, then fixes are made almost immediately!

Well, I can see no change with the settings in the latest betas (or release now). I still have to take out the '//' to get auto reprojection working.

 

If I don't make that edit, the situation is the same as it has always been, i.e. the fps jump around from 45-90 and moving (not turning) my head from left to right still produces horrible jumping around.

 

With reprojection on, I am very happy with the performance.

 

AFAIK, SteamVR settings for this don't work with WMR headsets.

 

A good reason for sticking with the SteamVR betas - like DCS - is to make use of any new options, improvements etc. before they move to the release version. SteamVR beetas are in my experience very stable, and if they are not, then fixes are made almost immediately!

Mine used to behave exactly as you describe if I left the file untouched.

I just tried again after another system restart and DCS behaves just like it did with the dashes removed and "motionvector" replacing the auto.

The file hasn't been touched and it appears as stock.

Very odd...

Mine used to behave exactly as you describe if I left the file untouched.

 

 

I just tried again after another system restart and DCS behaves just like it did with the dashes removed and "motionvector" replacing the auto.

 

 

The file hasn't been touched and it appears as stock.

 

 

 

Very odd...

Are you saying that the 'stock' settings file has the '//' in place, yet you are seeing a locked 45fps?

Like this: // "motionReprojectionMode" : "auto",

This is my file and I'm getting solid 45. Won't even bounce to 90 when I look up like I would expect.

{

"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

"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

}

Hang on......I'll get my coat...

I was checking out a copy of the file...

This is my file and I'm getting solid 45. Won't even bounce to 90 when I look up like I would expect.

 

 

 

{

"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

"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

}

Yes, that's what I would expect. You have 'motionReprojectionMode' set to 'motionvector', so it will always be locked at 45. If you set it to auto, then you can go up to 90.

But, you still had to edit out the '//', yes? If so, then the stock file pattern hasn't changed.

Realised what I've done now. The update must have not changed the file at all and I've gone in and deleted the indicator // thinking that it had, then replaced to test.

Utter failure on my part.

Cheers

I just got back into SteamVR after a long break while recovering from major surgery, and I have confirmed that the latest SteamVR Beta ends up resetting the default.vrsettings file to defaults. It had never done this before, but I think it did it this time around because they have added a bunch of extra lines to the code that weren't there before.

I have also confirmed that the menu-based settings for Motion Smoothing still do not work with WMR headsets (same as it was when Steam had disclosed that on their web-site back when they added the Motion Smoothing setting, that it was not compatible with WMR), even though they specifically now show an individual application setting for Windows Mixed Reality that offers Motion Smoothing as an option. So, maybe they're planning on making that work somehow in the near future? Until then, we can just turn Motion Reprojection on and off the way we're used to doing so.

The display resolution indicated in the SteamVR SS settings has changed to be pretty close to the native resolution of the headset (at least the Reverb anyway) when set to 100%. Mine now shows 2196X2153 when set to 100%

Realised what I've done now. The update must have not changed the file at all and I've gone in and deleted the indicator // thinking that it had, then replaced to test.

 

 

Utter failure on my part.

 

 

 

Cheers

Its also really easy to forget to shut everything down and restart it after making changes to that file, which will make it seem as if your changes had no effect. I've done that before. :doh::D

I just got back into SteamVR after a long break while recovering from major surgery, and I have confirmed that the latest SteamVR Beta ends up resetting the default.vrsettings file to defaults. It had never done this before, but I think it did it this time around because they have added a bunch of extra lines to the code that weren't there before.

 

I have also confirmed that the menu-based settings for Motion Smoothing still do not work with WMR headsets (same as it was when Steam had disclosed that on their web-site back when they added the Motion Smoothing setting, that it was not compatible with WMR), even though they specifically now show an individual application setting for Windows Mixed Reality that offers Motion Smoothing as an option. So, maybe they're planning on making that work somehow in the near future? Until then, we can just turn it on and off the way we're used to doing so.

 

The display resolution indicated in the SteamVR SS settings has changed to be pretty close to the native resolution of the headset (at least the Reverb anyway) when set to 100%. Mine now shows 2196X2153 when set to 100%

All good except it isn’t SteamVR beta that resets the default.vrsettings, it’s WMR for SteamVR that changes the file. This happened a few beta updates ago.

All good except it isn’t SteamVR beta that resets the default.vrsettings, it’s WMR for SteamVR that changes the file.

You know what I meant though. :smilewink:

I've had the Reverb Pro for 5 days, now. I'm getting close to giving up on it, because there is so much that needs to be done to get it working. There are lots of places to go for help, like this thread, but the general assumption is that I know things I don't really know. I see advice on what to do, but almost nothing on HOW to do it. One thing that bothers me is that HP, and others, haven't included an owners manual that takes you through the setup procedure, and no software to do most of the heavy lifting for the buyer.

I would imagine that most people using VR, and computers in general, grew up with computers. The rest of us didn't. The rest of us know only enough to get in trouble and become easily frustrated.

It seems to me that VR, right now, is mostly for early adopters. Maybe, hopefully, it will become as easy as buying a new smart phone. I just did that, and it didn't come with a owners manual, either.

I'm wondering if there are any other flight sim users out there in my situation that are suffering in silence. And would buy a VR headset if only the setup process was much easier.

I've had the Reverb Pro for 5 days, now. I'm getting close to giving up on it, because there is so much that needs to be done to get it working. There are lots of places to go for help, like this thread, but the general assumption is that I know things I don't really know. I see advice on what to do, but almost nothing on HOW to do it. One thing that bothers me is that HP, and others, haven't included an owners manual that takes you through the setup procedure, and no software to do most of the heavy lifting for the buyer.

 

 

I would imagine that most people using VR, and computers in general, grew up with computers. The rest of us didn't. The rest of us know only enough to get in trouble and become easily frustrated.

 

 

It seems to me that VR, right now, is mostly for early adopters. Maybe, hopefully, it will become as easy as buying a new smart phone. I just did that, and it didn't come with a owners manual, either.

 

 

I'm wondering if there are any other flight sim users out there in my situation that are suffering in silence. And would buy a VR headset if only the setup process was much easier.

https://vr4dcs.com/2019/09/10/reverb-settings-for-dcs/

Have you ran through this?

 

https://vr4dcs.com/2019/09/10/reverb-settings-for-dcs/

Yes. I’m the guy that suggested it should be stickied.

But, it’s more of the “what” to do than “how” to do it.

Yes. I’m the guy that suggested it should be stickied.

 

 

 

But, it’s more of the “what” to do than “how” to do it.

If you just launch steam vr on its own you will see the same little black box pop up once steam vr launches and you can get to the settings from there too. I just did what that guide said and everything has been working fine.

You can only get to steam vr settings once you launch steam vr. If you go to dcs options and enable VR headset and then you close dcs and launch dcs again, it should load wmr app as well as steam vr. You will see a little black box on the bottom of your monitor saying steamvr. There is small menu icon on the steam vr box where you can click and select settings which opens steam vr settings.

 

If you just launch steam vr on its own you will see the same little black box pop up once steam vr launches and you can get to the settings from there too. I just did what that guide said and everything has been working fine.

Are you one of those that grew up with computers?

Sure, you can right click on the black box. But, how did you know what settings to pick?

So, we are back to the “what” without the “how”.

I've had the Reverb Pro for 5 days, now. I'm getting close to giving up on it, because there is so much that needs to be done to get it working. There are lots of places to go for help, like this thread, but the general assumption is that I know things I don't really know. I see advice on what to do, but almost nothing on HOW to do it. One thing that bothers me is that HP, and others, haven't included an owners manual that takes you through the setup procedure, and no software to do most of the heavy lifting for the buyer.

 

 

I would imagine that most people using VR, and computers in general, grew up with computers. The rest of us didn't. The rest of us know only enough to get in trouble and become easily frustrated.

 

 

It seems to me that VR, right now, is mostly for early adopters. Maybe, hopefully, it will become as easy as buying a new smart phone. I just did that, and it didn't come with a owners manual, either.

 

 

I'm wondering if there are any other flight sim users out there in my situation that are suffering in silence. And would buy a VR headset if only the setup process was much easier.

No offense my man, but it took me like 5 min to set it up. Quite painless. You tried thuds guide for the reverb?

Is it running DCS for you or what?

We are happy to entertain questions.

Are you one of those that grew up with computers?

 

 

 

Sure, you can right click on the black box. But, how did you know what settings to pick?

 

 

 

So, we are back to the “what” without the “how”.

Lots of people mentioned that here in this thread. I grew up with computers but didn't need to use them until I started writing code in college so I don't think that has anything to do with it.

The wmr headsets are more of a pita to use compared to the Oculus because of the software. Hopefully one day we will have native dcs support for wmr.

Are you one of those that grew up with computers?

 

Sure, you can right click on the black box. But, how did you know what settings to pick?

 

So, we are back to the “what” without the “how”.

I think we can help you out. But you need to tell us where you are in the installation.

1) Are you on windows 10?

2) Have you downloaded SteamVR?

3) You may or may not have to download Windows Mixed Reality depending on the version of Windows.

Let's start there and we can help you along. I'm assuming you already downloaded and installed DCS?

I think we can help you out. But you need to tell us where you are in the installation.

 

1) Are you on windows 10?

2) Have you downloaded SteamVR?

3) You may or may not have to download Windows Mixed Reality depending on the version of Windows.

 

Let's start there and we can help you along. I'm assuming you already downloaded and installed DCS?

Yes to all 3. I have the latest version of Windows.

I have flown VR in DCS, but the cockpits are very blurry. In the P-51, for instance, the only thing in focus is the head pad saying "NO HAND HOLD".

Thanks for whatever you can do.

Your VR headset isn’t in your signature, can we confirm it’s a Reverb?

What is your SteamVR super sampling set to? Look in SteamVR settings under video?

What is your IPD, and have you set that correctly in WMR settings?