#1
|
|||
|
|||
Vizard 5.2 and Oculus health warning
I recently updated to 5.2 and noticed that the health warning can't be turned of pressing a key using render mode oculus.RENDER_SDK, so no direct to rift mode - or edit the windows registry to ad the disable option to the Oculus config.
Just for the record ... |
#2
|
|||
|
|||
Hi,
I am experiencing this problem, too. How can I fix it? I have the Vizard 5.2 version and the Oculus Runtime 0.4.4 regards, armo |
#3
|
|||
|
|||
I got the same issue. Is this problem specific to Vizard 5.2? It could be bug, I guess. By the way, I added the key in the windows registry, but it did not work. Don't know why.
Last edited by Zhi; 09-25-2015 at 04:36 AM. |
#4
|
|||
|
|||
Go to your sys tray -> right click on Oculus -> Configuration Utility -> Advanced -> check "disable health and security warning"
|
#5
|
|||
|
|||
The health warning is caused by the Oculus runtime version, not the Vizard version. If you're running runtime 0.5.0.1 or above you'll need to create a registry key. Once you've done that an option to disable the warning should be shown in the Oculus runtime app. You can find instructions online for the registry edit.
|
#6
|
|||
|
|||
Hi jeff,
I have installed the Vizard 5.2 version and the Oculus Runtime 0.4.4, but I am still encountering this problem. Specifically, when I run the "oculusExample.py" file, the warning stands still on the screen and does not disappear, whatever I do (pressing a key, pressing the mouse button, waiting for a long time without pressing anything, ecc.) |
#7
|
|||
|
|||
Add "disable health and security warning" to Oculus config util
You'll have to edit the registry open a command window as Administrator
and run RegEdit.exe If your Windows is 32-bit go to: HKEY LOCAL MACHINE\Software\Oculus VR, LLC\ If it is 64-bit, go to: HKEY LOCAL MACHINE\Software\Wow6432Node\Oculus VR,LLC\ then add a new key called LibOVR to this key add new string called valueHSWToggleEnabled and set it value to 1. When you open the Oculus config util and click advanced there will be a new line with the "disable health and security warning" Option. Good luck |
#8
|
|||
|
|||
Hi,
I have this problem too. I use vizard 5.2, Oculus runtime 0.6.0.1 on widows 8, 64bit. I have added the key and value in windows registry as suggested above. But it doesn't work, the warning message remains there. Anyone has solution? I am thinking about re-installing vizard 5.1. Does anyone know if vizard 5.1 has the same problem? Thanks. |
#9
|
|||
|
|||
tap tap
Ok, so does anyone have a fix for this yet?
I've stumbled across a work around (I wouldn't go so far as to call it a fix). I've setup the registry key (see above) for a W8.1 x64 box but the safety warning messag isn't cleared by key presses, *however* if I gently tap the side of the rift unit (as if tapping my temple) then the message is cleared. Bizarre! I'd be interested to know if this is just for my unit? A proper fix would be appreciated. Thanks (vizard 5.2 x64 & HMD firmware 2.12 ) |
Tags |
oculus rift, vizard 5.0 |
Thread Tools | |
Display Modes | Rate This Thread |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Blank screen on external monitor when running a Vizard script with Oculus DK2 | mstan | Vizard | 4 | 09-03-2015 05:58 AM |
oculus DK2 in vizard 5 | green951 | Vizard | 1 | 06-18-2015 08:12 AM |
Vizard 4 Oculus Rift support? | NIgroupOS | Vizard | 1 | 03-09-2015 03:43 AM |
Oculus DK1 and DK2 in Vizard 5 | Jeff | Vizard | 3 | 10-02-2014 11:00 AM |
Oculus DK2 and Vizard 5 | seal | Vizard | 0 | 08-28-2014 12:46 PM |