uri_ba Posted March 17, 2019 Share Posted March 17, 2019 I'm a Vive user myself, so when I was testing a rift I borrowed from work I was surprised to see stupidly long load times. It didn't go into the pit after 30 minutes. DCS was holding a core or two working. However nothing happened. Killed process, disabled VR, loaded the same scenario in normal time. Re-enabled VR, stupid long times, no cockpit after long minutes. Then a friend suggested to try and run the Oculus with steamVR. Worked like a charm. All this using the current stable. Any ideas? Creator of Hound ELINT script My pit building blog Few DIY projects on Github: DIY Cougar throttle Standalone USB controller | DIY FCC3 Standalone USB Controller Link to comment Share on other sites More sharing options...
dburne Posted March 17, 2019 Share Posted March 17, 2019 Should certainly not be that long, something sounds like was amiss in your Rift software setup maybe. Don B EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero| Link to comment Share on other sites More sharing options...
uri_ba Posted March 18, 2019 Author Share Posted March 18, 2019 In other software and flight Sims it works just fine. And the same exact setup with steamVR as API works fine. SteamVR is just a midiary between the game and the Oculus SDK. Compared to running the SDK nativly, which doesn't work properly. Creator of Hound ELINT script My pit building blog Few DIY projects on Github: DIY Cougar throttle Standalone USB controller | DIY FCC3 Standalone USB Controller Link to comment Share on other sites More sharing options...
Recommended Posts