How do you get ASW working with the new Steam Beta for WMR?

[oz555]

I never unboxed the WMR controllers and can't get my Xbox controller to do anything with the Steam VR home/mountain hut place so I don't see this dashboard you speak of. Do I continue to comment out the appropriate auto line in the CFG file or the let Steam VR manage line followed by the settings in the basic Steam VR settings window. Confused again..

[speed-of-heat]

Well you could try unboxing them... failing that yes you can still continue to do edit the file at least for the time being.

[imacken]

Well you could try unboxing them... failing that yes you can still continue to do edit the file at least for the time being.

 

Haven’t tried it, but not sure that editing that file works any more. We are told not to edit it in text within the file, and settings changes are no longer stored in it.

 

My feeling is that changes must be made now in the WMR tab of SteamVR overlay. Could be wrong though!

[speed-of-heat]

Oh it still works, it just gets overwritten every time wmr gets updated. And no guarantees it will continue to work

[imacken]

It does? Interesting.

The file shows ‘disabled’, but reprojection is on via the WMR tab for me. Similarly with status indicators. Whatever is in the old settings file, has no effect on what I see.

[speed-of-heat]

It overrides the settings for motion vector, not tried the other stuff, so if on in the file i believe that has precedence, or it could be some Boolean logic applied not sure which, it certainly doesn’t changed the displayed settings, but it does effect the behaviour.., that’s one of the the many reasons they ask people not to mess with the file

[imacken]

Yep, just tried it out. The value in the 'old' settings file does override whatever is set in the WMR tab.

 

Best just to leave it at the default (disabled) and select stuff from the nice new shiny panel!

 

PS Same applies to the status indicators, FWIW.

[speed-of-heat]

Agreed , GUI, until proven otherwise, is always the right way...

[Dunx]

Mmmm, on my rig, default.vrsettings overrides the SteamVR GUI.

 

I need to comment out motionReprojectionMode if I want to use the GUI. I've tried "disabled", and all other combos.

 

• Windows 10 Enterprise 1909
  
• GeForce Game Ready Driver 451.48
  
• SteamVR [beta] (latest)
  
• Windows Mixed Reality for SteamVR [beta] (latest)
  

[imacken]

Mmmm, on my rig, default.vrsettings overrides the SteamVR GUI.

 

I need to comment out motionReprojectionMode if I want to use the GUI. I've tried "disabled", and all other combos.

 

• Windows 10 Enterprise 1909
  
• GeForce Game Ready Driver 451.48
  
• SteamVR [beta] (latest)
  
• Windows Mixed Reality for SteamVR [beta] (latest)
  

 

That shouldn't be happening. The MS default is now disabled and that allows all use of settings in the WMR tab of SteamVR overlay to be applied.

[GunSlingerAUS]

I'm about to try the new WMR tab within Steam - what are the optimal settings to remove ghosting from reprojection? Should I set reprojection to Auto? Per App setting? Advice appreciated.

[imacken]

I'm about to try the new WMR tab within Steam - what are the optimal settings to remove ghosting from reprojection? Should I set reprojection to Auto? Per App setting? Advice appreciated.

 

None of that will make any difference to your ghosting experience.

 

Auto means you will get generally 45fps or 90fps depending on the situation. If you are ever getting 90fps, you probably will not see ghosting, as reprojection is off. (You will go below 45 at times when there is a lot going on.)

 

Per app just means that it will use whichever setting you set for DCS within SteamVR (in the video tab when DCS is running), as opposed to the general, overall SteamVR setting.

 

I personally, always use forced on, so that I get a smooth 45fps 90% of the time.

 

As we have discussed before, I do not experience unpleasant ghosting effects. I don't kow if it's a hardware thing, or the fact that 45fps is acually a big range of frame times, i.e. 12ms to 22ms, or what.

[GunSlingerAUS]

Yeah, tried it again. I solely fly the F-14, and with all details turned extremely low, I was able to play the instant action night landing with relatively little ghosting. It was an excellent experience. Unfortunately, as soon as other aircraft were involved, the horrible artefacting/ghosting returned, in both the instant action missions of Dogfight and Case 1 recovery.

 

I'm guessing it's more noticeable in high speed aircraft, where the ghost frames have to make up for a much larger gap in spacial positioning. Having said that, even the Spitfire instant action BF-109 dogfight degraded from a pleasant experience at the start, to another haunting ghost-fest as soon as I got in a turn fight with the bogeys.

 

Can I ask which aircraft you fly, and what kind of missions? It's possible you're playing slower, ground-attacked focused scenarios?

[imacken]

At the moment, I tend to fly Hornet, Mirage and Spitfire mostly, but tinker with most modules.

 

I tried the F-14 IA Dogfight, and didn't really see much ghosting. Sure, in very tight close up turns with the SU-27, there was a bit, but nothing that would bother me.

 

Are you sure you are achieving a solid 45fps? When you see the bad ghosting, are you sure you are not dipping below 45?

[GunSlingerAUS]

Yep, locked at 45fps. You're right, it's not too bad when the other aircraft are a medium distance away, but I find the stuttering under about 1nm too much for me. Glad you're happy with it - I'm hoping the 3080 Ti will allow me to hit 60fps minimum, in which case I'll happily run the Reverb at 60Hz and play all day.

 

Just wish NVIDIA would hurry the fck up, my C9 monitor desperately needs HDMI 2.1 so I can bust past 60Hz at 4K.

[imacken]

Yep, locked at 45fps. You're right, it's not too bad when the other aircraft are a medium distance away, but I find the stuttering under about 1nm too much for me. Glad you're happy with it - I'm hoping the 3080 Ti will allow me to hit 60fps minimum, in which case I'll happily run the Reverb at 60Hz and play all day.

 

Just wish NVIDIA would hurry the fck up, my C9 monitor desperately needs HDMI 2.1 so I can bust past 60Hz at 4K.

It's not so much that I'm happy with it, I'm just not really seeing the issue! I don't get stuttering at all.

 

Personally, I find the 60Hz experience horrible. The obvious screen flickering at that low Hz is unbearable imo.

[eaglecash867]

It's not so much that I'm happy with it, I'm just not really seeing the issue! I don't get stuttering at all.

 

Personally, I find the 60Hz experience horrible. The obvious screen flickering at that low Hz is unbearable imo.

 

I only rarely get the stuttering on mine with my current settings, but only when I'm down low near a fairly large city with both the TGP and MAV displaying images on my MFCDs.

 

I'm with you on the 60Hz issue too. When I tried switching over to that, it was like being trapped in a room with a bad fluorescent tube. The flickering was terrible!

[VirusAM]

Is any of you experiencing issues with Motion reprojection lately?

In the last few days it seems not working to me (it worked previoulsy).

Basically it is only working if I use "force-on" options in steamvr gui (then is locked on 30 or 45 fps depending if I use 60hz or 90hz refresh rate), but with auto I have frames all over the place from 45 to 90 depending on the load as if it was OFF.

I tried also uncommenting the setting in the text file (as was used before), but the effect is the same.

I am wondering if the Oculus Software which I also have installed (having also the Rift S) could be causing some sort of conflicts with WMR and steamvr.

[speed-of-heat]

if you have HAGS switched on then that may be the culprit...

 

In general I have noticed that the tolerances seem to be a little "tighter"...e.g. Motion Vector cuts in about a 0.5ms earlier than it should

[VirusAM]

if you have HAGS switched on then that may be the culprit...

 

In general I have noticed that the tolerances seem to be a little "tighter"...e.g. Motion Vector cuts in about a 0.5ms earlier than it should

 

Oh yeah...I have it enabled....will try with it off.....

What did you end up using?

[Notso]

You can ignore all previous advice since the update to WMR for SteamVR yesterday. All MP stuff is now handled by the new WMR tab in SteamVR dashboard.

 

imacken, does that mean that we should NOT remove the line "motionReprojectionMode" in the Steam VR settings default file? What should we do if we've already removed the line.

[speed-of-heat]

Oh yeah...I have it enabled....will try with it off.....

What did you end up using?

 

im currently using HAGS, with motinon vector and rendered VR frames=4 in the nvidia control panel ... ymmv but it seems to "work" and by that i mean not cock up... :) i cant honestly see a frame rate difference, but i dont seem to have the lag i used to with pre rendered frames either ...

[imacken]

imacken, does that mean that we should NOT remove the line "motionReprojectionMode" in the Steam VR settings default file? What should we do if we've already removed the line.

 

The line is now defaulted to ‘disabled’ in the recent WMR update. Certainly for me, that allows all options in the SteamVR overlay to work.

[Willie Nelson]

I can’t confirm that reprojection is working since the latest update. Someone from Steam VR (see link) has indicated that for around three months you need to delete the line in motionReprojectionMode line from the default.vrsettings file, which I did. And then, go to the in GUI and select enabled for DCS.

 

 

This hasn’t worked for me, I can’t see the reprojection indicator after I restart and I don’t know how else I am able to confirm that WMR reprojection is operating. Any suggestions?

 

To be clear, I am on the latest updates of SteamVR and my NVIDIA driver is the same. I also have kegerty’s shader mask on, perhaps this is covering indicator but I wouldn’t have thought so. I am not sure if I’m supposed to be seeing 45fps when it’s working or 90?

Edited July 5, 2020 by Willie Nelson

[imacken]

Firstly, you can tell if it's on as you will probably only see 45fps 90% of the time. Occasionally, 90 and below 45, but in general you'll be seeing 45. what you will not see, is variable rates between 45 and 90.

 

A recent update - see various posts above - to SteamVR and WMR has, in theory, made this much simpler. We don't need to edit the old settings file any more, and MS have set motionrepojectionMode to 'disabled' now. All settings for reprojection etc. are now in a WMR tab on the SteamVR overlay.