Forum Discussion
Blank Screen using DK2
I have tried running the basic scenes from the OculusUtilities package and all I get is a blank screen in the goggles with the following console output:
[CAPI] LibOVR module is located at C:\Program Files\Oculus\Support\oculus-runtime\LibOVRRT64_1.dll
[HMDState] Requested to SetForegroundWindow(80408ll)
IAD changed to 64.0mm
[HMDState] Requested to SetForegroundWindow(80408ll)
Here is what I have:
Unity 5.3.4 p5.
NVIDIA 365.10 on Win7 using GTX 980 TI
Latest Oculus Rift runtime, 1.3.2 utilities and OVRPlugin 1.3.2
I have tried other Unity projects and it is the same issue.
Any ideas? Thanks.
[CAPI] LibOVR module is located at C:\Program Files\Oculus\Support\oculus-runtime\LibOVRRT64_1.dll
[HMDState] Requested to SetForegroundWindow(80408ll)
IAD changed to 64.0mm
[HMDState] Requested to SetForegroundWindow(80408ll)
Here is what I have:
Unity 5.3.4 p5.
NVIDIA 365.10 on Win7 using GTX 980 TI
Latest Oculus Rift runtime, 1.3.2 utilities and OVRPlugin 1.3.2
I have tried other Unity projects and it is the same issue.
Any ideas? Thanks.
5 Replies
Replies have been turned off for this discussion
- There are a few things that can cause this:
1) A firmware or driver update is pending
2) Rift unplugged or disabled
3) Your app was built with a newer version of the SDK than your installed Oculus system integration. This is uncommon due to our push updates.
Can you use the Oculus log gatherer and PM me the ZIP file it creates for you? - I figured it out:
Anti Aliasing was set to disabled under Quality Settings. I don't even know how that happened. I wonder if I installed a package that disabled it.
Thanks vrdaveb - Thanks, there seems to have been a regression in Unity when MSAA is disabled. We're working with them to fix this.
- The issue appears to be fixed in 5.3.4p6 and higher.
- OK. I'll try it. Now I remember... I disabled AA due to the white speckles "fire flies" around the edges of meshes when AA is enabled.
