Getting rid of health and safety warning

Well the functions claim to work and indeed do mention application-based eye rendering.

Currently implementing them into my DLL, for subsequent testing in LFS.

Amazing how low my motivation is compared with the past few weeks. It's very hard to force myself work on something that only serves to annoy people and has no conceivable benefit to anyone. It's why it has been hard to believe the possible meaning of the vague wording on the subject in the Developer Guide.

Right, I can see the "not allowed to dismiss the message for a while" times in LFS now.

The complication now arises from the fact that there are several ways into LFS.

- Straight to entry screen if track is not loaded at startup.
- LFS logo in the middle of the screen for a few seconds if track is loaded at startup (would clash with HSW).
- Replay loaded at startup (will be forced to display HSW over part of the replay in the 15 seconds case).

So basically I now have to display the HSW on a sort of dialog in a position that is suitable for all the screens you could get to while the HSW is being displayed, and modify the code for some of those screens to avoid clashing too badly (i.e. text behind text) with the HSW.

Whoever designed this diabolical nonsense only had in his mind a simple VR demo. Not a complex fully functioning game with menus and entry screens. Zero points for broad thinking. It's funny when some manufacturers don't even know what their product is for. And one of the best uses of a Rift is WITH A SIMULATOR!

I am going to assume I can correct the English in my version of this. As we at Live for Speed take great care to use correct spelling and grammar.

In hsw.tga there are two obvious English errors that reinforce the "rushed out" look of this whole HSW thing.

1) The first time the word "Headset" is used it should not have a capital letter, but does.

2) The second time it is used, apparently it should have a capital letter, because it's the first word of the sentence. But it shouldn't be the first word of the sentence. The first word should be "The".

Another oversight is "Press any key to acknowledge"... as the SDK specifically prohibits removal of the HSW display for 15 seconds or 6 seconds. During that time, it's a false instruction that could appear as a sort of bug, when pressing a key does not dismiss the message. In my version the instruction will change. Maybe a visible countdown and after the countdown, an instruction similar to "Press any key to acknowledge" or perhaps just an OK button.

Here's my corrected version of the text before that.

HEALTH & SAFETY WARNING

Read and follow all warnings and instructions included with the headset before use. The headset should be calibrated for each user. Not for use by children under 7. Stop use if you experience any discomfort or health reactions.

More: http://www.oculus.com/warnings

I will not be part of this stupidity. I'll be disabling the warning in my programs, and if oculus doesn't want to distribute them I don't give a shit. Also, if they want to sue me, I say bring it on.

"n00854180t" wrote:
there's going to be a "Remove Warnings Patch Tool" as soon as the Rift becomes popular enough that that message is pissing off more people.

I hope so. I wonder if Oculus hasn't to solve some real problems rights now apart from implementing penetrating
and senseless 'warnings' for developers...

spyro

Pretty tedious way to spend a day...

Not finished yet...

[edit : removed images, now can be seen in our Test Patch 0.6F8]

Fun times - spending several days wasting work on something that is designed solely to piss people off.

Also, the whole erroneous "press any key to acknowledge" when it doesn't even obey those keypresses... seriously? Any like... amateur UI designer knows that is the worst possible thing in UI design you can even do.

The behavior regarding this HSW is something I'd expect from ANTVR, not Oculus.

"n00854180t" wrote:
The behavior regarding this HSW is something I'd expect from ANTVR, not Oculus.

I am becoming quite convinced they have developed a superiority complex and feel it's ok to treat developers like dirt. It is of no concern to them that without developers they are nothing at all.

They sold out to facebook and that shows a lack of personal pride and a willingness to be controlled by someone else. So they will end up hoping to be in control of us in turn. I suspect young Palmer's lack of world experience caused that sad mistake.

As facebook has a reputation for treating its developers like dirt, the same effect will filter through here.

Anyway it's great that VR has arrived. We can "use" Oculus as our plaything too. It's a testing ground and a development platform for us to develop our stuff that will run on all the other VR hardware coming soon, hopefully from people with a more humble attitude! :)

Anyway, my progress is that the "annoying message" support is all done, dismissible by a keypress after the countdown provide by Oculus SDK. All I have to do now is make various game screens move their things aside to avoid overwriting the message. Only taking about 12 hours of work. :(

The whole thing is annoying as hell and Oculus is handling the situation pretty poorly but let's not be too dramatic about it either. ;)

Just wait and see. One day Palmer will regret it.

He had the chance to run something really great. Now he just does what he is told.