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

    Up and Coming
    October 22, 2014
    Doesn't the consumer accept it while buying it? Why would you need this in something that is a prototype? It is not consumer ready.
    Inspiring
    October 22, 2014
    Seriously, can we not just lock this thread?

    It's basically just troll-bait at this point, and the 'new' questions being asked are just rehashing old points.

    We all hate the HSW during development, and Oculus knows we hate it.
    Brad Davis - Developer for High Fidelity Co-author of Oculus Rift in Action
    Inspiring
    October 22, 2014
    I don't see a reason to lock the thread. It appears people are following the rules.

    And, yes, Oculus is aware of the community's feedback and I thank you guys for contributing.
    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
    October 24, 2014
    A bit more esoteric post, but I understand why Oculus are including this warning. They are the first to introduce a new technology to the masses, and rather than being sued for people being stupid, they prefer to be proactive with their warnings.

    But I think we will look back on this in a couple of years and laugh at the extreme caution at which we introduced this new technology. It can be compared to the laws (Locomotive Acts) that were passed in Britain in the 1861-1878, which limited vehicles to maximum of 4 mph (6.4 km/h) in the country and 2 mph (3.2 km/h) in the city - as well as requiring a man carrying a red flag to walk in front of road vehicles.

    So every time you see the "health and safety warning", think of the man with the red flag. :lol:

    Up and Coming
    October 24, 2014
    Our prayers have been answered in the new 0.4.3 SDK:

    "Added option in the Oculus Configuration Utility to Suppress the Health and Safety Warning during active development."
    Up and Coming
    October 24, 2014
    "pixelminer" wrote:
    A bit more esoteric post, but I understand why Oculus are including this warning. They are the first to introduce a new technology to the masses, and rather than being sued for people being stupid, they prefer to be proactive with their warnings.

    But I think we will look back on this in a couple of years and laugh at the extreme caution at which we introduced this new technology. It can be compared to the laws (Locomotive Acts) that were passed in Britain in the 1861-1878, which limited vehicles to maximum of 4 mph (6.4 km/h) in the country and 2 mph (3.2 km/h) in the city - as well as requiring a man carrying a red flag to walk in front of road vehicles.

    So every time you see the "health and safety warning", think of the man with the red flag. :lol:



    Haha this is perfect.

    Glad to hear that we can suppress it at least in 0.4.3 SDK. It'd be nice if that was just a standard option in the config utility going forward - there's no legit reason for it not to be (*obviously* if the person disables it there they have agreed to it already, but I digress).

    Just like the absurd reg-flag-man and tiny speed limits, this warning will probably go extinct in time. Unfortunately until then we have to deal with it spamming our faces in unpleasant fashion.
    Twitter IndieDB
    Participant
    October 25, 2014
    Glad it can be removed for development now. It was really annoying.
    Ordered and Received DK1 Ordered DK2 within 18 minutes of announcement!! woot! Concerned about facebook thing, but would have done the same myself. Developing the VR gloves you always imagined(over 1 year full-time development, and looking sweet)
    Up and Coming
    January 12, 2015
    Bump on this, I really think it is essential for developers to be able to remove this warning and replace it with their own. I don't think it's fair to force all VR developers to show an uncomfortable warning when we can show the same message in our own way (for example as a 3D panel floating in front of the user, rather than plastered onto their face.
    Inspiring
    January 12, 2015
    May I ask that the image file for the Health and Safety Warning please be provided in binary form?
    Good places would be in the SDK together with all the other image files in
    \OculusSDK\Samples\OculusWorldDemo\Assets\Tuscany

    or with the Oculus runtime installer at
    C:\Program Files (x86)\Oculus\Tools\Resources


    As I use client rendering my problem is actually opposite to the thread title: I have to write extra code for displaying the Health and Safety warning. That's more or less fine with me, but currently this file is only distributed in source form here:
    \OculusSDK\LibOVR\Src\CAPI\Textures\healthAndSafety.tga.h


    which is the worst format of distribution I can think of. To get it in binary form I currently have to dump the memory it occupies when running one of the SDK samples. I would rather not do this again with every new SDK version.

    Please :)
    Inspiring
    January 12, 2015
    I will look into this. Thanks for the feedback.
    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