Crispus

Thanks for taking time to help! My Rift's USB connections are all going back to a dedicated PCIe - USB 3 Card similar to the one that you linked to. The keyboard and HOTAS are on the Motherboard USB, a mixture of USB2 and USB3. Its probably worth noting that ctrl-alt-del still works to open task manager, and shut down DCS, but that ESC will not open the in-game menu in DCS. I think that the controllers are still working, Windows sees them, but DCS stops responding to them.

Hi All, New to DCS, and I have a strange problem when I increase the pixel density to above 1.0 in the VR settings (in DCS world or through Oculus debug). If I start a new mission (F/A-18C) then it will work for a short while before the controls freeze up totally. After this point I cannot interact with the simulation or access the menu through my HOTAS or my keyboard. It seems like this is triggered when I attempt to interact with cockpit controls such as DDI buttons or hard-wired functions like A/A or A/G buttons. Meanwhile the simulation continues to run fine, it does not crash and there is no extra jitter or lag. Frame-rate remains as before also. The Oculus head tracking will also continue to work but I am a passenger in the aircraft. If I change the pixel density back to 1.0 then the problem never happens, ever. The issue seems to be 100% repeatable, I have spent a few hours switching between settings (various different pixel densities from 1.1 through to 2.0) and have faced the same behavior consistently every time. I have repaired the DCS World installation, but no change in behavior. Has anyone else observed this behavior (I did search, honest!)? PC Spec: i5-4670K @4.1GHz, 16GB RAM, EVGA GTX1080 SC