Skip to main content
Up and Coming
February 24, 2015

7 seconds of blackness before my scene appears

When I run my "DirectToRift" exes, it takes about 5 seconds to get the Health & Safety Warning to appear, another 5-7 seconds with the gray background Unity logo, and then 7-8 seconds of blackness before my scene fades in from black. Is there any way to reduce these times?

None of the unity demos that I run have these kind of load times and my scene is much simpler.

Thank you kindly for your assistance.

My important specs:
Core i5 2500K, GTX 970. 16GB RAM
    This topic has been closed for replies.

    10 replies

    Inspiring
    February 24, 2015
    What version of Unity are you using and on what OS?
    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
    Inspiring
    February 24, 2015
    Also, you can try removing OVRScreenFade.cs from your cameras and disabling the health and safety warning (see the documentation).
    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
    Up and Coming
    February 25, 2015
    "cybereality" wrote:
    What version of Unity are you using and on what OS?


    Unity 4.6.2f1. Windows 8.1.
    Up and Coming
    February 25, 2015
    "cybereality" wrote:
    Also, you can try removing OVRScreenFade.cs from your cameras and disabling the health and safety warning (see the documentation).


    Thank you for the reply Cybereality.

    OVRScreenFade is set to 0 for Fade Time.
    OVRMainMenu is set to 0 for fade in time (although I don't have a menu).

    Same result.

    I am unable to remove the Health and Safety Warning. My registry does not have the required key (64-bit OS):

    HKEY LOCAL MACHINE\Software\Wow6432Node\Oculus VR, LLC\LibOVR\HSWToggleEnabled

    For reference, the 32-bit location is not there either.
    Inspiring
    February 25, 2015
    I was saying actually deleting the component script from the inspector. I'm not sure setting it to zero is enough.

    I'm also concerned if you don't have those registry keys. Can you try reinstalling the latest runtime as administrator?
    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
    Up and Coming
    February 25, 2015
    "cybereality" wrote:
    I was saying actually deleting the component script from the inspector. I'm not sure setting it to zero is enough.

    I'm also concerned if you don't have those registry keys. Can you try reinstalling the latest runtime as administrator?


    I'll give that a try and report back. Thanks!
    Up and Coming
    February 25, 2015
    "cybereality" wrote:
    I was saying actually deleting the component script from the inspector. I'm not sure setting it to zero is enough.

    I'm also concerned if you don't have those registry keys. Can you try reinstalling the latest runtime as administrator?


    I reinstalled the latest runtime as administrator and my registry looks the same:



    The folder is there, but no key for HSWToggleEnabled.

    I removed the component script from the inspector, rebuilt, and still have a 7-8 second black screen from the time the gray background Unity logo disappears and my scene appearing.
    Inspiring
    February 25, 2015
    You may have to create the key if it's not there.
    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
    Up and Coming
    February 25, 2015
    "cybereality" wrote:
    You may have to create the key if it's not there.


    Key created. I was able to go into Advanced Oculus config and remove the HSW. My application loads much more quickly. Still 3-4 seconds of black, but much more manageable.
    Inspiring
    March 14, 2015
    This was happening to me, turning the fade time down on OVRscreenfade fixed the issue.