Reverb G2 - 6DoF to 4 DoF and tracking issues

[EAFFlashheart602]

HI all,

 

Been having some tracking issues with the Reverb G2 and  Il2/FC which seems to have got particularly worse recently and is now making it borderline unplayable.

 

I'm getting regular flickering, and the headset losing tracking when I turn round (say 'sticking'; 45deg off) necessitating hitting the recentre button every 5mins, or it will shift my viewpoint to one side laterally. Also I seen to lose one DoF from time to time so when I lean forward, the cockpit will move away from me.

 

I'm using VR in MSFS and  DCS too and there VR works fine. I've also tried getting it to 'forget' the environment settings in Control Panel as well as use Room Scale instead of sitting - but not much seems to be working. 

 

I'm on SteamVR beta and WMR for Steam beta and running a 2070 with 32G RAM. As noted above - DCS and MSFS the G2 tracking is mostly perfect and its just IL2 where this has now got unplayable.

 

Anyone got any ideas, please? 

 

(NB: I'm no numpty when it comes to PC stuff, but if anyone does have a solution could they please screenshot their settings or the menu involved or just explain how to get there as there seem to be so many places to adjust VR settings (Steam VR 'home' 3D space, Windows MR 'Home' 3D space, the WMR menu that pops up when you hold a controller button down, the SteamVR 2D settings panel etc etc). Thanks!)       

[O_DesoLunatic]

Make sure the room is well lit, and if G2 is using regular WMR software, go to options and "clear environment data" - I noticed that WMR headsets after some time require it to work properly. 

[firdimigdi]

A couple of things:

1. The most obvious: clean the cameras on the headset, hair (especially from pets, or even your own if you wear yours long) can confuse it, also if something gets in the way of the lateral cameras for long enough it can lost tracking altogether.

2. Turn on the WMR flashlight and scan around to see what the cameras are seeing. If there's any LED, especially on a joystick or other object that can move around or just change position it can confuse inside out tracking easily. I had interference from a VKB grip that had an LED, luckily it could be turned off with their software; while it would not lose a degree of movement it would suddenly shift the view.

[patrickod]

Is your G2 connected to an externally powered USB hub? When I first got my G2 none of my motherboard USB ports were compatible so I purchased a PCI-E USB expansion card which "worked" in the sense that the headset was recognized and I could play games, but it experienced significant tracking and flickering/blue screen issues similar to the ones that you describe. I figured this was down to brightspots in my environment and tweaked but to no avail.

For separate reasons I picked up an externally powered USB-3 hub, and once I connected my G2 through this all my tracking issues were instantly resolved. I've not had a recurrence since. If you have access to one for debugging this might be worthwhile.

Edited June 19, 2021 by patrickod

[EAFFlashheart602]

Thanks all for the replies and advice. This is something new as earlier this year it seemed to be working perfectly. (and works fine with MSFS and DCS). I use the 'seated' position rather than room-scale. 

 

I've tried 'clearing the environment' in the Win10 settings - but that didn't seem to do anything. Have the lights on. 

 

G2 connects directly to my motherboard - and USB. I may try another port though to see if that solves it. I could also try cleaning it,

 

LEDs/lights - there are lights on Warthog which may be obscured when I move my hand I suppose. Also a TrackIR - although that's obviously not turned on.

Thought - would the tracking be affected by the sim mirroring the Headset display in my monitor and movement there? If so is there a way to minimize it during flight so it would just be the desktop? or maybe even perhaps a 'test screen'/ grid pattern to assist in tracking? 

 

(Also a user above in this forum said that start-up procedure should be WMR, SteamVR and then Il2. Maybe that's it? (I usually startup WMR first then hit play in Il-2 which starts SteamVR)

 

 

[O_DesoLunatic]

On 6/22/2021 at 12:58 PM, EAFFlashheart602 said:

Thought - would the tracking be affected by the sim mirroring the Headset display in my monitor and movement there? If so is there a way to minimize it during flight so it would just be the desktop? or maybe even perhaps a 'test screen'/ grid pattern to assist in tracking? 

 

 

 

 

Unlikely but you can confirm by trying to replicate the issue with both game and mirror minimized. Also since it is not happening in DCS and MSFS, it might be that loosing DOF is connected to being too close to the edge of the cockpit and the game will not let you move further due to limited VR view option (many server enforce this setting so you won't push your head outside the cockpit). 
What is your CPU and what in-game settings are you running? Maybe you are getting some stutter due to too much load on CPU and tracking doesn't get enough resources to work properly?

 

[EAFFlashheart602]

i7 - 9700k @ 3.60Ghz here. 32Gb RAM and a 2070 Gfz card

 

In game settings on 'Balanced' except for enable 4K textures and use VR HMD.

 

I fly with cockpit VR boundary restrictions on - maybe I'll take that off.

 

As I said above - used to work perfectly earlier this year (and was smoother than DCS) so not sure what has changed. Il-2? SteamVR? WMR?

 

 

 

[coconut]

Check if you have game mode enabled in the windows settings. If it is, try disabling it.

My guess is that one of the processes involved in getting the images from the headset cameras and processing them has too low priority.

An improperly configured Process Lasso could do that too. 

[EAFFlashheart602]

Hi folks - thanks for suggestions.

 

The tracking problem is still there. 

 

A similar thread on this form suggested it was BIOS problem related to sound and USBs - so I used the inbuilt ASUS EZ BIOS updater to patch it to latest version - but again no joy.

 

I've also turned on/off the WMR OpenXR reprojection tool that was released earlier this year and boosted framerates for some folks in DCS. Again no difference.

 

Game mode has been tried on/off. No change

 

SPECS

WMR and Reverb G2

PROCESSOR: Intel Core i7-9700K CPU, 8 Cores / 8 Threads, 3.6 - 4.9GHz
GRAPHICS CARD: NVIDIA GeForce RTX 2080 8GB GDDR6 Graphics Card
MOTHERBOARD: Asus TUF Z390-PRO GAMING Motherboard
Memory: 32GB DDR4 2400MHz Memory (2 x 16GB Sticks)

 

Any other ideas? Full reinstall of Il-2 and see if that somehow cures it? DCS and MSFS are working fine with Il2 and it used to work perfectly too - up until about March/April.  

 

[EAFFlashheart602]

Bumping this again as I updated BIOS and all drivers and completely uninstalled and re-installed the game. 

 

Same result.

 

From my playtime I reckon something changed after  May when the Spit XIV came out. I flew some SP career mission with that - but then the tracking issues came in.

 

Steam VR? WMR? OpenXR? 

[Drum]

Are you using NobiWan's Necksafer mod?  If so, you might want to check if you're using the newest version.  Also, if you're using the latest Necksafer version, put your settings to sitting; I read up thread you had changed that and the Necksafer mod requires sitting to be set.

Edited August 31, 2021 by Drum

[EAFFlashheart602]

No - not using Necksafer. (I think the immersion of having to twist and turn in your seat is part of the fun!)