Up and Coming

Getting rid of health and safety warning

261 replies
65444 views

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.

Show previous replies

S

Scawen

Up and Coming

"jherico" wrote:
What bugs me is people appearing to be perfectly capable of using the SDK and then suddenly becoming baffled when they encounter a requirement they don't like.

When I use the SDK, I can use some trial and error, to see if I got it wrong or right.

This warning thing, as it's not absolutely clear, I feel I may have to go over the top in being annoying with it. Or... can I, for example, allow the user to switch it off so it doesn't come up every time?

The risk of getting it wrong is too much to take. It takes me and Victor about half a day to do all the builds, updating the auto updater, changing the websites, updating mirrors, when we make a new official version on our site.

For Oculus to then come and say, "no your submission is rejected, because you acted on yoiur own initiative" would be very bad indeed. I don't want to take that risk. This is why I am asking the simple question: EXACTLY what must we do? But they are not replying. Why? I just want to know what to do! It's not unreasonable!

Live for Speed - www.lfs.net

J

jherico

Inspiring

"scawen" wrote:
The risk of getting it wrong is too much to take. It takes me and Victor about half a day to do all the builds, updating the auto updater, changing the websites, updating mirrors, when we make a new official version on our site.

For Oculus to then come and say, "no your submission is rejected, because you acted on yoiur own initiative" would be very bad indeed. I don't want to take that risk.

Then don't. You can either be conservative and implement the functionality like Oculus has, or you can wait for a response.

What exactly do you think happens when you ask the question? Neither Cyber nor Gypsy are going to take it on themselves to provide what amounts to legal advice at best (and at worst amounts to asking how much you can get away with). The request, if it goes anywhere, will go up the chain of responsibility, probably getting punted up several times. Each step in that chain is an opportunity for someone to just ignore it on the basis of not wanting to contradict the license.

If it ever makes it to someone who's in a position to actually answer authoritatively (which is iffy), it will probably be a lawyer, not an engineer, who in turn will either say that the license expresses what needs to be expressed (because by answering otherwise they risk muddying the waters) or will say that they'll look at making the requirements more clear in the next release. Which may or may not actually happen.

My best guess is that you can implement the warning however you feel like, and as long as you make a good faith effort to comply with the license, you'll be fine. But the fact that you're talking about risk on a public forum kind of undermines that. It implies that you know exactly what you have to do and you're trying to see what you can get away with instead of doing that.

Brad Davis - Developer for High Fidelity Co-author of Oculus Rift in Action

N

n00854180t

Up and Coming

If the requirements were even remotely sane, there wouldn't be a need to work around them. The problem is that there is no legitimate reason to show the warning every single time someone uses the headset, full stop.

No, "liability" is a not a valid reason, or...guess what? We'd see similar messages plastered on anything you can use more than once, but we don't.

No, every other product in the world is covered sufficiently by displaying a warning once (obtuse, crap exceptions, need not apply).

Twitter IndieDB

S

Scawen

Up and Coming

You have good logic there, Brad, but you are kind of avoiding the point that the SDK document is very unclear about what to do. I and some others have pointed out (carefully, thoughtfully and well researched) other flaws in the SDK and we have been totally blanked there as well. So this is their way. Treating people like...

It's pretty bad that no-one responds. It is truly awful customer / developer support to simply ignore reasonable questions and just serves to make me angry. I'm a developer of a serious simulator that is selling loads of Rifts. Nothing I said there means I deserve to be totally blanked as if I am an impudent child.
viewtopic.php?f=53&t=12439

Live for Speed - www.lfs.net

C

cybereality

Inspiring

If it wasn't clear before: yes, the health and safety warning is required. Right now it needs to be shown every time an app is launched, though we may want to investigate ways of reducing the frequency. If you attempt to disable or otherwise circumvent the warning, then your app will be rejected by Oculus. Hope that makes sense.

S

Scawen

Up and Coming

My god, a reply at last! Why wait so many days before replying to a reasonable question? I am working really hard here on DK2 support and LFS is running at the top of Oculus Share Top Rated list. You should just spend a couple of minutes here and there to keep us happy.

Anyway, you still haven't covered my questions. I guess from your response, you don't know much about the SDK, but in the case of the non-SDK rendered approach, it's not a case of disabling or circumventing the warning. We have to implement it from scratch, without any reasonable guidelines.

Live for Speed - www.lfs.net

C

cybereality

Inspiring

Sorry, I was on vacation all last week and internet access was spotty.

If you are working with a custom renderer (not SDK rendered) then you would have to implement the warning yourself. However, it's basically just a flat quad floating in space (with a texture you can pull out of the SDK files). It should be pretty straight-forward to add in your game.

N

n00854180t

Up and Coming

"cybereality" wrote:
If it wasn't clear before: yes, the health and safety warning is required. Right now it needs to be shown every time an app is launched, though we may want to investigate ways of reducing the frequency. If you attempt to disable or otherwise circumvent the warning, then your app will be rejected by Oculus. Hope that makes sense.

This needs to be changed and fixed, immediately.

If the developers here don't like it (and it's very clear the majority hate it), consumers will not put up with it.

It should be shown ONCE at most.

Twitter IndieDB

R

riptwire

Participant

Make your application an always on daemon process which you connect to as required. Shown once when the application is launched :twisted:

R

riptwire

Participant

"n00854180t" wrote:
"cybereality" wrote:
If it wasn't clear before: yes, the health and safety warning is required. Right now it needs to be shown every time an app is launched, though we may want to investigate ways of reducing the frequency. If you attempt to disable or otherwise circumvent the warning, then your app will be rejected by Oculus. Hope that makes sense.

This needs to be changed and fixed, immediately.

If the developers here don't like it (and it's very clear the majority hate it), consumers will not put up with it.

It should be shown ONCE at most.

Are you expecting a debate on this? cyberreality is just the messenger here- he didn't write their legal policy. Maybe you should try to get this message further up the chain...

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO