Unable to get cognitive load data
I'm working with the HP Reverb G2 Omnicept, to test whether it is a useful addition to our future clients. I have the sample project running in Unity, but have been unable to get any cognitive load data coming from the headset. It does work with the Omnicept Simulator, but not the live HMD. Even after waiting for several minutes while wearing the headset.
I have a Trial license. Omnicept Runtime 1.12 installed.
Output from the Omnicept console, no cognitive load data:
Eye tracking data is correctly showing:
Subscription result list:
Thanks for opening this post. Can you please share the omnicept log located at "C:\ProgramData\HP\HP Omnicept"
Eye-tracking data and subscription list seem okay so with the log we might know why omnicept is not returning cognitive load from the HMD.0
Thanks for the quick reply! Since the log has been getting quite long, and I cannot attach the file itself, I have uploaded the log contents here: https://pastebin.com/fc5na4Kp0
From the logs seems that the runtime is having problems accessing the registry may you please check at the registry editor that "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\HP\HPOmnicept\Config" exists and also that on the tray app under sensor privacy the sensors are enabled.0
I'm not sure which value in the registry you'd like to see?
All sensors are enabled:0
Thanks for sharing this, we have kept on looking at the log, and seems that there are some odd disconnections.
What I will suggest is the following: Uninstall Omnicept and clean the log folder, restart the computer, reinstall omnicept, enable all the sensors from the tray app and try again with just the console. On the console, the idea will be to try to get cognitive load, and if you don't receive any let the headset be connected for 3-4 minutes (so we can see on the log if anything is disconnecting). Remember you will need to accept the request on the tray app.0
I did as you said, but no cognitive load data in the console. Here's the log: https://pastebin.com/cYusrpC2
(Note: as you'll see in the log, the first time I started the console I forgot to connect the headset. The second time the headset was connected, I let the headset be connected from 10:55 - 11:00)
I also tried a different USB port (with the usb c-a adapter) but no success.0
Thanks for sharing that we are looking into this. Will be possible for you to open a ticket (right bottom corner) so we can take a closer look at what's happening?
Also for anyone else reading, we will revive this post with the issue once it's solved.0
Thanks, I have opened a ticket.0
Has there been an update to this thread by chance?0
Please sign in to leave a comment.