sohei Posted June 9, 2019 Posted June 9, 2019 Hi everyone I've noticed with both the Rift CV1 and the Reverb that occasionally when I fire up DCS the head tracking isn't working fully for VR. What I mean is that I can look around and tilt my head but I can't move laterally, up/down or forwards and backwards. If I make any of these movements the cockpit just moves with me. Fixing it seems to be a bit trial and error. A restart of the PC can work, and on one occasion in the F14 it just randomly fixed itself. I've also experienced this in the A10 Does anyone have any idea what causes this and what can fix it? It's a bit frustrating to fire up a mission only to find I can't move fully in my cockpit. This doesn't happen huge amount but it spoils the experience when it does occur, especially when I'm all primed for a larger mission! Any help appreciated. Thanks in advance! A small pie is soon eaten
kzial Posted June 9, 2019 Posted June 9, 2019 It happens to me too with my Lenovo explorer. It happens when wmr looses track of your motion (the xyz axis are lost). Usually, moving my head around helps the camera to track my position back. If not enough I fix it by launching the headset setup or turn the lights on.
Tinkickef Posted June 9, 2019 Posted June 9, 2019 (edited) Probably a usb problem. I got that sometimes with Rift. Maybe try a different driver, or plug it into a different usb port, maybe try a MB socket if you are currently using a PCie card. When it happened, I usually found that Oculus was flagging up a problem with the USB drivers for the cameras. I am having a few issues with Reverb at the moment. It has started to constantly connect and disconnect. It will fire up into cliff house, but when I move my head it will lose tracking, go black screen and the on monitor WMR portal will tell me to connect the headset. I originally suspected the large cable connector at the back of the headset, but having thought about it, it could be a USB or power issue. I am still going to cable tie the connector together though, and clip the cable directly to the side of the headset. That thick, stiff cable will be putting a lot of pressure on that connector. Edited June 9, 2019 by Tinkickef System spec: i9 9900K, Gigabyte Aorus Z390 Ultra motherboard, 32Gb Corsair Vengeance DDR4 3200 RAM, Corsair M.2 NVMe 1Tb Boot SSD. Seagate 1Tb Hybrid mass storage SSD. ASUS RTX2080TI Dual OC, Thermaltake Flo Riing 360mm water pumper, EVGA 850G3 PSU. HP Reverb, TM Warthog, Crosswind pedals, Buttkicker Gamer 2.
Werewolf_fs Posted June 9, 2019 Posted June 9, 2019 I had a similar problem with my Rift and they were my usb from my motherboard. Connect the rift to the usb-c of the RTX2080ti with an adapter and solved the problem!!.
sohei Posted June 9, 2019 Author Posted June 9, 2019 Thanks for the input everyone. I'll play around with USB connections to see if it helps. A small pie is soon eaten
sohei Posted June 9, 2019 Author Posted June 9, 2019 Probably a usb problem. I got that sometimes with Rift. Maybe try a different driver, or plug it into a different usb port, maybe try a MB socket if you are currently using a PCie card. When it happened, I usually found that Oculus was flagging up a problem with the USB drivers for the cameras. I am having a few issues with Reverb at the moment. It has started to constantly connect and disconnect. It will fire up into cliff house, but when I move my head it will lose tracking, go black screen and the on monitor WMR portal will tell me to connect the headset. I originally suspected the large cable connector at the back of the headset, but having thought about it, it could be a USB or power issue. I am still going to cable tie the connector together though, and clip the cable directly to the side of the headset. That thick, stiff cable will be putting a lot of pressure on that connector. I think you may have a point about the cable connector. I noticed that just a slight pressure on that connector causes flickering, so it could well also cause a reconnect. I'll do the same. Also I moved my various devices around so that the USB 3.0 ports were freed up as much as possible other than for the headset. It's a bit early to be certain but it does seem to be more stable now. A small pie is soon eaten
Recommended Posts