SCG_motoadve Posted October 2, 2019 Posted October 2, 2019 Any ideas how to fix this? try to lean to the side or front the whole cockpit moves forward or to the side. Does not matter if VR limit view is checked or not.
SCG_motoadve Posted October 2, 2019 Author Posted October 2, 2019 1 minute ago, dburne said: Sounds like maybe a tracking issue? Its the HP Reverb, it has no stations, dont know actually how is the tracking being done with this headset. Happened to me before with the O+ and it fixed it itself.
dburne Posted October 2, 2019 Posted October 2, 2019 21 minutes ago, II./JG77_motoadve said: Its the HP Reverb, it has no stations, dont know actually how is the tracking being done with this headset. Happened to me before with the O+ and it fixed it itself. Dark or bland room?
SCG_motoadve Posted October 2, 2019 Author Posted October 2, 2019 (edited) Lighted room. Its not IL2 , DCS has the same issue. Edited October 2, 2019 by II./JG77_motoadve
71st_AH_statuskuo Posted October 2, 2019 Posted October 2, 2019 I think it's a WMR issue. Exit out of WMR and then startup again, put on your headset and follow the instructions to look sideways and down. Then start Il2.
Muff_Huggar Posted October 3, 2019 Posted October 3, 2019 When this happens to me occasionally (and it happens in RFactor 2 also), I get out of the game, go into the VR settings and set the seated position again. This fixes it every time. I haven't figured out what causes it...sometimes I think it's after I've loaded the game on a flat screen to do some adjustments/configuration/etc.
SCG_Redcloud111 Posted October 3, 2019 Posted October 3, 2019 I used to use WMR wtih O+. A simple reenter in WMR settings will fix it. Make sure you have enough light in the room. I never had to shutoff and restart the game.
Aap Posted October 3, 2019 Posted October 3, 2019 I wonder if there has been some nVidia driver update or Windows update lately that affects WMR. Recently (a week or two ago) I had an issue that computer did not recognize my device and gave me an error code that the device was not plugged or something like that. Unplugging and re-plugging made my device work again, but when I tried to fly after that I had the same issue that entire cockpit moved, when I was moving my head. Restart of my computer and again un- and re-plugging fixed the cockpit issue, but now I have a situation all the time that I need to unplug and re-plug USB's to get Windows to recognize my device. After I do that everything works normally, but is not very fun to crawl behind my computer to unplug and re-plug cables every time I want to use VR.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now