Skip to main content
Up and Coming
July 26, 2014

Getting rid of health and safety warning

What is the proper way to get rid of the health and safety warning in Unity?
In OVRDevice.cs, I tired commenting out this:

if (HMD != null && Input.anyKeyDown && HMD.GetHSWDisplayState().Displayed)
HMD.DismissHSWDisplay();

and adding this to the end of Awake():

HMD.DismissHSWDisplay();


But that only works in the Editor but in the standalone version the head tracking stops working and the warning is not removed.

    261 replies

    Participant
    August 7, 2014
    As an enthusiast, avid user of the DK1, waiting list jockey for the DK2, and a future user of the Rift CVx, please, for the love of The spaghetti monster, get rid of this kindergarten nanny-state crap. Put it as a notice in the box, or at least let it be possible to turn it off(for ever and ever and ever) in the config utility. This would annoy me to no end if I have to see this every time I enter an application, and would be a serious nudge toward any competition of the Rift as soon as it would arrive.

    And before you ask, yes, I would actually consider an inferior product(within reason) if the better product annoyed me to the extent described in this thread.
    Up and Coming
    August 7, 2014
    As a developer I now have to build my app every time I need to test it, and seeing that warning every time has become extremely frustrating. Especially when I only need to run my app for 30 seconds.
    VR Jam 2015: Inside The Human Body Forum Post: viewtopic.php?f=77&t=23266
    Up and Coming
    August 7, 2014
    I'l getting my DK2 within the next few days and this is concerning. They really didn't add an option to turn it off or disable it after it's seen once? That's going to get really old during development. Ah well, I'm sure someone here will post when they discover the best way to erase this nuisance.
    -- -- --
    Up and Coming
    August 7, 2014
    While I do understand the need for the warning from a consumer product perspective. It should be disabled in debug builds completely, not just there for less time. And it should follow best practices, because right now it is uncomfortable to look at.
    Participant
    August 7, 2014
    "DillonRobinson" wrote:
    I'l getting my DK2 within the next few days and this is concerning. They really didn't add an option to turn it off or disable it after it's seen once? That's going to get really old during development. Ah well, I'm sure someone here will post when they discover the best way to erase this nuisance.


    If you look through this thread, I already outlined that you can use ovrhmd_EnableHSWDisplaySDKRender to disable it.
    Up and Coming
    August 7, 2014
    Ah, I must have glossed over it. Awesome! I understand their need to cover their asses, especially with relatively new technologies like these, but seeing it every time was not going to be fun. I'll try that line as soon as I get my DK2!
    -- -- --
    Up and Coming
    August 8, 2014
    "usb420" wrote:
    I think it caused a blood vessel to burst in my retina and I was seeing a spot (in real life) that wouldn't go away.


    Rather than guess about what may or may not have happened and whether or not it was anything to do with the Rift, that sounds like something you really should get checked out by an ophthalmologist. It could be nothing, or it could be a symptom of a serious condition. Either way, the Rift was most likely coincidental to whatever caused it.
    August 11, 2014
    So I've just installed the .4 drivers and I'm now permanently stuck with the Health and Safety Warning. Pressing keys does nothing, waiting does nothing. I'm in Unity, and am unable to get rid of the warning both in-editor and in a compiled app.

    I've tried following a couple threads' advice, but I get exactly the same problem. My app is utterly useless until I get this sorted out. Anyone out there with a concise guide on fixing this in Unity?

    Don't know that it's relevant, but I'm on an HDPrototype, not a DK2...

    Thanks very much
    August 11, 2014
    "mgc90403" wrote:
    So I've just installed the .4 drivers and I'm now permanently stuck with the Health and Safety Warning. Pressing keys does nothing, waiting does nothing. I'm in Unity, and am unable to get rid of the warning both in-editor and in a compiled app.



    Reinstalling the runtime fixed the issue. Huzzah.
    Participant
    August 11, 2014
    "mbzdmvp" wrote:
    As a developer I now have to build my app every time I need to test it, and seeing that warning every time has become extremely frustrating. Especially when I only need to run my app for 30 seconds.


    This.

    There's no way a developer should have to sit through it 1000 times per day....