Skip to main content
Up and Coming
March 30, 2016

How to disable the health and safety warning for development purposes in 1.3?

Is there a registry hack or similar since the option is no longer available in the settings panel it seems?

    48 replies

    Up and Coming
    April 22, 2016
    anyone found a way yet?
    Check out my Unity VR development blog: http://talesfromtherift.com @peterept
    Participant
    May 8, 2016
    I'm just getting pissed because of that screen! How a hell am I supposed to implement something when most of the time I'm staring at the damn LookAtBox! Please add an option to get rid of this f*** health screen. It can be aregistry hack or whatever but pleeeeese DO it!
    Up and Coming
    May 19, 2016
    +1 for an option to disable! This is coming up every time I run a build. I'd really like to see this built into OculusDebugTool as opposed to a registry hack.

    Inspiring
    May 19, 2016
    It should not come up every build. I believe it's on a timer (maybe 30 minutes) so if you are quickly building and testing things you should not see it every time. Unless you are on DK2, then I think it may be more frequent. Can I ask what headset you are using and which engine?
    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
    May 20, 2016
    null

    Even if it once a day (or reboot), it is still an annoyance, for me as an user, but it scale to frustration for devs !
    Participant
    May 20, 2016
    Hope they can come up with an update on this as soon as possible.
    Up and Coming
    May 22, 2016
    I have a DK2 and it comes up *every time*. It makes testing during development a huge pain in the ass.
    John Tsiombikas webpage - blog - youtube channel
    wbskAuthor
    Up and Coming
    May 23, 2016
    Comes up every time on a DKII.  Absolutely tedious for development as is Oculus Home running Unity and taking up the machines resources when we just want to be running our game and the HMD driver.
    May 23, 2016

    We test both DK2 and CV1 for serious work - molecular structures visualisation related for pharmaceutical R&D. Unfortunately the Oculus Home forced visualisation + Health and Safety warning makes professional use of Rift almost impossible ... To be honest we are starting to test HMD products form other manufactures purely from this reason (otherwise the HW is good, the changes introduced in 1.0.0 SDK are bad). We are even open to pay more for some professional HMD model, but without this Oculus Home and Safety Warning childish obstructions .... It is a bit pity we were lured by pre 1.0.0 SDK to focus on Rift and hoping no drastic changes will be introduced . We have lost a lot of time in this way ...

    Up and Coming
    May 23, 2016


     Unless you are on DK2, then I think it may be more frequent. Can I ask what headset you are using and which engine?


    I'm using a DK2 and unfortunately it is very frequent. I have a Rift and I'm in the process of updating but as @husakm pointed the HSW is a real problem for professional use. I understand the Rift is a consumer product,  not a professional one and that those consumers need to be protected. That being said allowing devs and pros to disable the HSW would greatly appreciated.