Skip to main content
Up and Coming
October 25, 2014

where to turn off health and safety warning in 0.4.3?

Where in the configuration utility can you suppress the health and safety warning? .4.3 says that is a new feature.

the config utiilty looks exactly the same for me but when i go in help it says that it is .4.3
am i missing something?

thanks

    15 replies

    Inspiring
    October 25, 2014
    No, they haven't really documented it. Perhaps they hope that only the hardcore developers will be clever enough to track down the code to disable it and act accordingly. Or perhaps it was just an oversight.

    Regardless, they way to disable the HSW is via your user profile. Unfortunately the required setting isn't exposed in the config util so you'll need to edit the profile file directly. On Windows it will be in <HomeDir>\AppData\Local\Oculus\ProfileDB.json.

    Find the section under "TaggedData" where the tags contains only the name of your profile (not your name and a Rift model). In the vals section you should see things like gender and player height. You need to add a boolean "HSW" value to the profile and set it to false. After editing mine this is what the relevant section looks like:



    "vals": {
    "HSW": false,
    "Gender": "Male",
    "PlayerHeight": 1.778000,
    "EyeHeight": 1.675000,
    "IPD": 0.063511,
    "NeckEyeDistance": [0.080500, 0.075000],
    "EyeToNoseDist": [0.032874, 0.030637]
    }


    Save the file and run your application. the HSW should be gone.
    Brad Davis - Developer for High Fidelity Co-author of Oculus Rift in Action
    Up and Coming
    October 25, 2014
    thanks so much for the help. weirdly that didn't work. i restarted the config utility and turned the rift on and off but nothing. anything i'm missing? i have it on the correct user in the utility.
    the code i have is:
    if there's nothing else i need maybe it will just start working eventually?
    thanks!
    "tags":	[{
    "User": "me"
    }],
    "vals": {
    "HSW": false,
    "Gender": "Unknown",
    "PlayerHeight": 1.778000,
    "EyeHeight": 1.675000,
    "IPD": 0.064000,
    "NeckEyeDistance": [0.080500, 0.075000],
    "EyeToNoseDist": [0.032000, 0.032000]
    }
    Up and Coming
    October 25, 2014
    Doesn't work for me.. :( strange
    Inspiring
    October 25, 2014
    Are you compiling against 0.4.3?
    Brad Davis - Developer for High Fidelity Co-author of Oculus Rift in Action
    Up and Coming
    October 25, 2014
    i'm using unreal engine 4. testing the game by doing "play -> standalone game" and the warning pops up before every time. is that a ue4 thing? noticed the warning isn't showing up in tuscany demo

    edit - just tried hmd hsw in ue4 and that didn't do it either! jesus this thing is so annoying.
    Inspiring
    October 25, 2014
    Support for disabling in Unreal will probably have to wait for the next Unreal release, when they update to the new SDK.
    Brad Davis - Developer for High Fidelity Co-author of Oculus Rift in Action
    Participant
    October 25, 2014
    The first pdf in the documentation section has all the details on this
    System: i5-3570k / GTX 670 / 8GB / Xonar DGX / Win7 64bit
    Up and Coming
    October 27, 2014
    Doesn't work for me, either. Still seeing this silly and message all over my face every single time.
    Inspiring
    October 28, 2014
    Sorry for the confusion. The option is documented, though it's a little hidden away (developers only remember).

    See section 7.2 of the Developer Guide:

    http://static.oculus.com/sdk-downloads/documents/Oculus_Developer_Guide_0.4.3.pdf
    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
    October 29, 2014
    Hi,

    I think this option should be more easily available in the configuration tool, even for consumers. It should be hidden under an Advanced tab, but it should be possible to turn off for anyone, as a global setting (at your own risk, of course).

    Currently, it's pretty messy, as it conflicts with the controls of many programs, and doesn't delay the program from starting. I'd even say it makes the Rift more dangerous, at least for me, when I need to rush to click away the warning message before the demo starts, reaching out for the keyboard blindfolded in a hurry.

    I don't see any legal risks with disabling it as long as the user agrees they're using the Rift at their own risk (which I assume they have to do anyway).

    EDIT:
    I just noticed the registry fix, which enabled the checkbox in the config utility. Great job, that's exactly what I had in mind. I still believe that you sooner or later will have to give consumers access to it by default.