Skip to main content
MartinSchultz
Up and Coming
August 12, 2014

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.
    This topic has been closed for replies.

    11 replies

    drash
    Inspiring
    August 12, 2014
    I just now knocked out the last problem with this with my own project:

    QualitySettings Vsync On
    DX11 On
    DirectToRift.exe
    and update graphics driver.

    If Vsync is off, crash at startup.
    If DX11 is off, DirectToRift.exe doesn't work.
    And I was getting vertical tearing until I updated my (Nvidia) graphics driver to the latest version.

    I haven't even tried getting something working in the Editor, though.
    Titans of Space PLUS for Quest is now available on DrashVR.com
    MartinSchultzAuthor
    Up and Coming
    August 12, 2014
    I tried your settings, didn't work for me.

    Do you run your DK2 in Direct HMD Mode or as extended desktop?
    Play Rift Racer @ http://www.decane.net/game/oculus-rift/riftracer/
    drash
    Inspiring
    August 12, 2014
    "MartinSchultz" wrote:
    Do you run your DK2 in Direct HMD Mode or as extended desktop?

    Sorry forgot to mention that -- Direct HMD Mode.

    And my updated graphics driver is now giving me a ton of random triangles/sparklies, and freezes the PC occasionally. Not too happy about that.
    Titans of Space PLUS for Quest is now available on DrashVR.com
    Boff
    Up and Coming
    August 12, 2014
    I had similar problems with 0.4.0 (haven't had a chance to try 0.4.1 yet).

    I ended up creating 4 builds of my project to test (similar to the judder test posted on Reddit)
    DX11VSync
    DX11NoVSync
    DX9VSync
    DX9NoVSync

    The only one that would work correctly (i.e. Direct HMD mode is set in config util, all direct-to-hmd exe's used) was DX11NoVsync.

    Hopefully using this method you can at least get something to run.

    Initially when I couldn't get my existing project running at all, as a test I created a brand new project, imported the OVR stuff and just created an empty scene with OVRCameraController, a plane, a directional light and a few primitives. Worked fine!!
    budwheizzah
    Up and Coming
    August 12, 2014
    "drash" wrote:
    "MartinSchultz" wrote:
    Do you run your DK2 in Direct HMD Mode or as extended desktop?

    Sorry forgot to mention that -- Direct HMD Mode.

    And my updated graphics driver is now giving me a ton of random triangles/sparklies, and freezes the PC occasionally. Not too happy about that.

    Direct HMD even with the editor? Direct + editor never worked for me, but Extended works great.
    I just undock the game preview window and drag it to the extended screen. Voila, poof, beauty. This since 0.4.0.
    ronjart
    Up and Coming
    August 12, 2014
    I have very similar problems. Crashes, not rendering to rift etc. (4.0 was working fine for me - with the known issues) - my development has come to a halt.
    vrdaveb
    Inspiring
    August 15, 2014
    "knup" wrote:
    Crashes, not rendering to rift etc. (4.0 was working fine for me - with the known issues) - my development has come to a halt.

    Did you uninstall the 0.4.0 runtime before installing 0.4.1? What kind of crash is it?

    "budwheizzah" wrote:
    Direct + editor never worked for me, but Extended works great.

    The editor doesn't support direct mode yet. It should be in a future release, but for now you'll have to use extended mode.

    MartinSchultz, any luck with extended mode?
    MartinSchultzAuthor
    Up and Coming
    August 15, 2014
    @vrdaveb: No, actually not. I'm using Win 8.1 and try to duplicate the main screen. Regardless which combination I try, the screen always orients to vertical and the selector to change it is greyed out. I've updated Nvidia drivers, but didn't help.
    Play Rift Racer @ http://www.decane.net/game/oculus-rift/riftracer/
    ronjart
    Up and Coming
    August 15, 2014
    "vrdaveb" wrote:
    "knup" wrote:
    Crashes, not rendering to rift etc. (4.0 was working fine for me - with the known issues) - my development has come to a halt.

    Did you uninstall the 0.4.0 runtime before installing 0.4.1? What kind of crash is it?


    At first I did not uninstall and simply installed the new runtime/sdk. Since things weren't working for me, I uninstalled all Oculus software (Runtime and SDK) and when it prompted a restart, Windows would not start up again :cry: . I re-install windows. Just got my Laptop running again, installed the Oculus runtime and now my PC won't start up again.

    I'm assuming that there is something else wrong with my system unless other people experienced something similar. I'm probably going to attempt a clean install of windows and see where this takes me.
    vrdaveb
    Inspiring
    August 15, 2014
    "MartinSchultz" wrote:
    No, actually not. I'm using Win 8.1 and try to duplicate the main screen. Regardless which combination I try, the screen always orients to vertical and the selector to change it is greyed out. I've updated Nvidia drivers, but didn't help.

    Have you tried extending the desktop instead of cloning it? That should enable you to set the resolution and rotation of the Rift.

    "MartinSchultz" wrote:
    In direct to rift mode, all I see is a blue screen, Rift does not activate from orange LED to blue.

    Is this issue still occurring in extended mode?
    Show more replies
    Terms & ConditionsAccessibility statement