Hi everyone, I've been away for a bit pursuing other projects but decided to pick up my DIY DK1 project again. These two games worked natively with the 0.4.4 runtime, though sometimes had to unplug/plug the tracker: įantastic work on the forum and experimenting!ĭemos/games with which I've had success, for anyone else with similar build.
This is amazing even without SteamVR/Vireio, and finally have experienced the. Key note for anyone else struggling with visual studio mscvp100.dll errors, installing all three of these resolved it: However, it was working for me in side by side crosseyed.
Unfortunately, I could not get 3.0.1 working direct to rift, or detecting tracking. Maybe I missed a step in getting newer Oculus runtimes working in Win10 and seeing the EDID?
COLORCROSS VR REDDIT DRIVERS
My drivers are up to date, and I noticed from the forum here that it had been not working, but now was working again for them. This happened with Oculus runtime versions 0.7, 0.8, and 1.3, but 0.4.4 works perfectly. After uninstalling Oculus and restarting, the EDID is immediately detected. The graphics card won't even recognize a monitor is plugged in, even with a fresh restart with only the EDID plugged in. Mysteriously in Win 10, after installing the newer SDKs, the EDID is not getting detected at all. Vireio Perception and SteamVR are not working for mine with runtime 0.4.4 (Windows 10, NVIDIA GeForceGTX 760). Only Oculus 0.4.4 runtime is working, which is limiting. Tracker, with excellent instructions on the MPU6000 & STM32F103C8T6 (no HMC, haven't noticed drift)~$25 EDID spoofer failed, so ordered a headless dongle online (blew at least 10 hours trying all methods here, but realized after getting the dongle that I had the latest SDK installed.ops. Rubber baby buggy bumper foam padding, superglued to mask for comfort (generic headset hurt), ~$4 Generic Colorcross VR headset (Google cardboard-style lenses seem fine), ~$12
0 kommentar(er)
