Skip to main content
Elecman
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

    Show previous replies
    kojack
    kojack
    Honored Contributor
    September 27, 2014
    "BlindingLightVR" wrote:
    I hope it's fixed/improved sooner then later. I even have an issue on some apps I have been running where the warning will not go away, no matter how many times I throw my keyboard or controller at the wall.

    Try slapping the left side of the rift (not too hard of course).
    No, I'm not joking, that's how the unreal demos I tried worked, no keys got rid of the message, the demo checks for a sudden jolt on the accelerometer.
    Author: Oculus Monitor , Auto Oculus Touch , Forum Dark Mode , Phantom Touch Remover , X-Plane Fixer Hardware: Threadripper 1950x, MSI Gaming Trio 2080TI, Asrock X399 Taich Headsets: Wrap 1200VR, DK1, DK2, CV1, Rift-S, GearVR, Go, Quest, Quest 2, Reverb G2, Quest 3
    Lightspeed
    New Participant
    October 7, 2014
    The Unity health & safety warning is dumb. I spent half an hour trying to figure out why it wouldn't disappear. It turns out you just have to wait. Which wouldn't be so bad if it didn't say at the bottom of the text "Press any key to acknowledge", pressing any key having no effect.
    Lightspeed
    New Participant
    October 7, 2014
    Actually I think it's just broken, I can't get it off at all in some cases. More troubleshooting for me. :p
    cybereality
    Inspiring
    October 7, 2014
    You may have a corrupted profile.

    You need to delete ProfileDB.json in this folder:

    C:\Users\YourName\AppData\Local\Oculus


    Then open the Config Util and create a new profile.
    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
    Lightspeed
    New Participant
    October 9, 2014
    Excellent, thanks! It's sorted.
    ElementalSpark
    Up and Coming
    October 9, 2014
    "cybereality" wrote:
    I'm in talks with the team about seeing if we can allow an option to disable the warning while developing. You would still be required to show the warning on final released builds, but this may make the development process easier. I don't know when (of even if) that will happen, but it is being discussed.



    Thank you!
    Sneer
    Participant
    October 20, 2014
    "cybereality" wrote:
    Please don't attempt to disable the warning. It's there for a reason.

    For what reason? Put savety warning in installation and place a sticker on rift...
    Why not let the customer choose, if they like to get rid of this annoying message?
    FrostFire
    Participant
    October 20, 2014
    I understand why it has to be there for consumer-ready software. But it's incredibly annoying for development.

    You're adding time to an iteration cycle when it comes to game design. A few seconds may not sound like a lot, but when you test about 30-60 builds an hour for the feel of cutscenes/animations/game balance, it really adds up and gums up the process.
    cybereality
    Inspiring
    October 20, 2014
    Yeah, I can totally understand this could be annoying while developing.

    We are looking into finding a good middle ground to aid developers, and there should be more info at a later date.
    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
    Fredz
    Up and Coming
    October 22, 2014
    The solution has already been given here : viewtopic.php?f=37&t=12247
    Show more replies
    Terms & ConditionsAccessibility statement