Skip to main content
Participant
October 9, 2014

Unity Tuscany Demo - only black screen with sound

Hi everyone,

Just got my DK2 and installed the runtime and Unity Tuscany demo for windows downloaded from here
https://developer.oculusvr.com/?action=dl&p=sdk&v=21. However when I double click Win_OculusUnityDemoScene.exe all I get is a black screen although I can hear sound. Also the headset LED remains orange.

I tired changing Direct/Extended/Legacy and still the same problem.

I believe theres something wrong with the Unity demo because I tried the DK2 demo and the ConfigUtil demo and they both work. Is the Unity demo ready for DK2 yet and are there any changes I should make? Are there any logs I should look at?
    This topic has been closed for replies.

    19 replies

    November 24, 2014
    Unity integration just crashes Unity :-(

    CORRECTION: If I enable Direct X 11 in project settings, then I can see the rift display in the play window, and it responds to head tracking, but device remains black

    Anybody having success with the Unity integration?
    Inspiring
    November 24, 2014
    Can you guys post more detail specs of you system?

    Most important is the OS, video card, video driver version, and Unity version.

    Thanks.
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
    November 24, 2014
    Problem occurs in Unity, and also just running the pre-built Oculus Unity demos.

    Mirror display shows fine onscreen, but device is black.
    (Win_OculusUnityDemoScene_DirectToRift.exe is black mirror too, but can hear sound).
    Demo Scene works fine on device
    OculusWorldDemo works fine on device.

    Windows 8.1
    Oculus Runtime 0.4.3
    Oculus Firmware 2.12
    Oculus Unity Integration 4.3.1

    Graphics Card GTX 980, Driver 344.75
    pg278q GSync Monitor - problem occurs with gsync enabled and disabled

    Unity 4.5.5f1
    (Integration doesnt work in 5.0 beta 14 )

    Should the Unity integration or Oculus Service generate any logs I can check?
    OutputLog.txt from Log from prebuilt Unity 4.3.1 demo included below

    Thanks again for your help

    -----------------------------------------------------------------------------

    Initialize engine version: 4.5.5p3 (b8dc95101aa8)
    GfxDevice: creating device client; threaded=1
    Direct3D:
    Version: Direct3D 9.0c [nvd3dum.dll 9.18.13.4475]
    Renderer: NVIDIA GeForce GTX 980
    Vendor: NVIDIA
    VRAM: 3072 MB (via DXGI)
    Caps: Shader=30 DepthRT=1 NativeDepth=1 NativeShadow=1 DF16=0 INTZ=1 RAWZ=0 NULL=1 RESZ=0 SlowINTZ=0
    Begin MonoManager ReloadAssembly
    Platform assembly: D:\OculusUnityDemo431\OculusUnityDemo\Win_OculusUnityDemoScene_Data\Managed\UnityEngine.dll (this message is harmless)
    Loading D:\OculusUnityDemo431\OculusUnityDemo\Win_OculusUnityDemoScene_Data\Managed\UnityEngine.dll into Unity Child Domain
    Platform assembly: D:\OculusUnityDemo431\OculusUnityDemo\Win_OculusUnityDemoScene_Data\Managed\Assembly-CSharp.dll (this message is harmless)
    Loading D:\OculusUnityDemo431\OculusUnityDemo\Win_OculusUnityDemoScene_Data\Managed\Assembly-CSharp.dll into Unity Child Domain
    - Completed reload, in 0.032 seconds
    <RI> Initializing input.

    <RI> Input initialized.

    desktop: 2560x1440 144Hz; virtual: 2560x1440 at 0,0
    Platform assembly: D:\OculusUnityDemo431\OculusUnityDemo\Win_OculusUnityDemoScene_Data\Managed\System.Core.dll (this message is harmless)
    Platform assembly: D:\OculusUnityDemo431\OculusUnityDemo\Win_OculusUnityDemoScene_Data\Managed\System.dll (this message is harmless)
    New Participant
    November 26, 2014
    Having the same issue, although my screen becomes white instead of black. Here is mine log, so you guys ahve some more info:

    Initialize engine version: 4.5.5p3 (b8dc95101aa8)
    GfxDevice: creating device client; threaded=1
    Direct3D:
    Version: Direct3D 9.0c [aticfx32.dll 8.17.10.1172]
    Renderer: ATI Radeon HD 5800 Series
    Vendor: ATI
    VRAM: 1016 MB (via DXGI)
    Caps: Shader=30 DepthRT=1 NativeDepth=1 NativeShadow=1 DF16=1 INTZ=1 RAWZ=0 NULL=1 RESZ=1 SlowINTZ=1
    Begin MonoManager ReloadAssembly
    Platform assembly: D:\Oculus Rift\OculusUnityDemo\Win_OculusUnityDemoScene_Data\Managed\UnityEngine.dll (this message is harmless)
    Loading D:\Oculus Rift\OculusUnityDemo\Win_OculusUnityDemoScene_Data\Managed\UnityEngine.dll into Unity Child Domain
    Platform assembly: D:\Oculus Rift\OculusUnityDemo\Win_OculusUnityDemoScene_Data\Managed\Assembly-CSharp.dll (this message is harmless)
    Loading D:\Oculus Rift\OculusUnityDemo\Win_OculusUnityDemoScene_Data\Managed\Assembly-CSharp.dll into Unity Child Domain
    - Completed reload, in 0.050 seconds
    <RI> Initializing input.

    <RI> Input initialized.

    desktop: 1920x1080 60Hz; virtual: 1920x1080 at 0,0
    Platform assembly: D:\Oculus Rift\OculusUnityDemo\Win_OculusUnityDemoScene_Data\Managed\System.Core.dll (this message is harmless)
    Platform assembly: D:\Oculus Rift\OculusUnityDemo\Win_OculusUnityDemoScene_Data\Managed\System.dll (this message is harmless)
    Crash!!!


    I am working on a windows 7 machine, OS-Version: 6.1.7601 (Service Pack 1)
    New Participant
    November 26, 2014
    Hey guys,

    Try updating your graphic card driver. I had the same problem and fixed it by updating it.
    New Participant
    November 26, 2014
    I had the same problem but got mine to work! Here's my extreme newbie method:

    From this post: viewtopic.php?f=26&t=17458&p=222902&hilit=desktop#p222902

    I set the rift to Extended mode, rotated it around to portrait and tried moving the Unity demo window to the extended screen as described. No dice, crashes everywhere. What worked for me was setting the rift as the primary monitor. Then when I ran the unity demo it popped up on the rift, no problems.
    November 27, 2014
    Still not working....

    344.75 are the latest drivers, released on 11/18/2014....

    Can't set rift as primary unless in extended mode... and the demo is designed to run direct to rift.

    Thanks again for any help
    December 5, 2014
    [UPDATE]

    4.4 Release fixes issue...Thank you :-)

    BTW - (For those too excited to read the docs) I didn't realize DirectToRift mode doesn't work within editor - you have to drag game window to extedned display and resize appropriately.

    After building, 2 exes are created, and DirectToRift exe works!
    New Participant
    April 1, 2015
    Hola el problema lo solucione, forzando el dx a dx 9...y no ma ha dado problemas