Forum Discussion
0.4.1 integration: #Fail
I've been removing all references to the 0.3 sdk, imported the new 0.4.1 sdk and gave it a spin (DX11: off). In direct to rift mode, all I see is a blue screen, Rift does not activate from orange LED to blue.
When I start the standard exe, I see a black screen, nothing more.
The Rift is set up as Direct HMD access.
Anyone had the same and found a workaround?
- Martin
P.S. I patched the RIft to Firmware 2.11 as it was written in the docs.
P.P.S: I tested the "Cubes" scene. The pos tracker camera is on, Rift rotation works, but LED is still orange and Rift display is off. The config util demos works fine bzw. Using latest Unity 4.5.3 P3 patch release.
When I start the standard exe, I see a black screen, nothing more.
The Rift is set up as Direct HMD access.
Anyone had the same and found a workaround?
- Martin
P.S. I patched the RIft to Firmware 2.11 as it was written in the docs.
P.P.S: I tested the "Cubes" scene. The pos tracker camera is on, Rift rotation works, but LED is still orange and Rift display is off. The config util demos works fine bzw. Using latest Unity 4.5.3 P3 patch release.
11 Replies
Replies have been turned off for this discussion
- @vrdaveb I've set up like you suggested. In extended mode then with 2 desktops I often get a crash when starting the <XXX>directToRift.exe. When it starts, it sends the output not to the rift, but to the main screen. But no blue or black screen anymore then.
That happens to me with a plain new project in Unity 4.5.2 p2 and only importing the 0.4.1 unity package from the Oculus SDK (Cubes scene).
The ONLY way to get it working is to modify OVRShimLoader.cs and change the line 50 from ResolutionDialogSetting.HiddenByDefault to ResolutionDialogSetting.Enabled.
That lets me choose the second display as output in the config dialog (that is a new change in p2 - the patched startup dialog with screen selection).
