Forum Discussion
Win10 RT 0.7 No Play In HMD
Hi,
I have a clean install of win 10
new install of 0.7 Oculus runtime.
Unity 5.1.2f1
Demo scene in Oculus Utility works great.
Anomaly One:
The BLUE Led on my HMD will stay on AFTER I close the Demo Scene, it will stay on until I close the Oculus Utility tool.
Created a simple Unity project. Plane, Cube, Directional Light and Unity FPS Controller prefab.
Enabled "Virtual Reality Supported" in player settings
In the editor the unity scene plays in the HMD, head tracking perfect etc.
Anomaly Two:
In a build of the same Unity project. The HMD light never turns blue, nothing is displayed in the HMD the scene loads in the PC screen, but no tracking is noted.
EDIT: just found this in the build log.
Initialize engine version: 5.1.2f1 (afd2369b692a)
[VRDevice] Initialization of device oculus failed.
GfxDevice: creating device client; threaded=1
Direct3D:
Version: Direct3D 11.0 [level 11.0]
Renderer: NVIDIA GeForce GTX 980 (ID=0x13c0)
Vendor: NVIDIA
VRAM: 3072 MB
Begin MonoManager ReloadAssembly
Suggestions?
I have a clean install of win 10
new install of 0.7 Oculus runtime.
Unity 5.1.2f1
Demo scene in Oculus Utility works great.
Anomaly One:
The BLUE Led on my HMD will stay on AFTER I close the Demo Scene, it will stay on until I close the Oculus Utility tool.
Created a simple Unity project. Plane, Cube, Directional Light and Unity FPS Controller prefab.
Enabled "Virtual Reality Supported" in player settings
In the editor the unity scene plays in the HMD, head tracking perfect etc.
Anomaly Two:
In a build of the same Unity project. The HMD light never turns blue, nothing is displayed in the HMD the scene loads in the PC screen, but no tracking is noted.
EDIT: just found this in the build log.
Initialize engine version: 5.1.2f1 (afd2369b692a)
[VRDevice] Initialization of device oculus failed.
GfxDevice: creating device client; threaded=1
Direct3D:
Version: Direct3D 11.0 [level 11.0]
Renderer: NVIDIA GeForce GTX 980 (ID=0x13c0)
Vendor: NVIDIA
VRAM: 3072 MB
Begin MonoManager ReloadAssembly
Suggestions?
4 Replies
Replies have been turned off for this discussion
- Can you try restarting your computer, and then immediately running the build exe file (DO NOT open Unity or the Config Util or anything else). Does it work the first time? Then what if you close the app and then run the exe file again?
- Thanks Cyber, I tried as directed.
Restart PC do nothing else bu launch the exe. Nothing in the HMD
Restarting the application directly after Nothing in the HMD.
By nothing I mean no image and the light did NOT turn blue. - UPDATE!
After a reinstall of the sdk\runtime my builds work as expected. My major issues is resolved.
The BLUE LED still remains on after running the demo scene, but this does not prevent my game from working in the HMD, the blue LED remains on until I exit the Oculus Tool, even if Iv started and stooped other experiences . - I'd just like to chime in here and say that this exact problem happened to me and had me stumped until I found this thread. I had verified driver version, runtime version, all build settings, etc., and what finally fixed it in the end was simply uninstalling and reinstalling the 0.7.0.0 runtime. I was using Windows 8.1 x64 with the DK2 and a GTX 980 Ti.
Thanks so much for following up with your found fix, wheatgrinder--lifesaver! :D
