-
Notifications
You must be signed in to change notification settings - Fork 7
Troubleshooting
NeuroGloves is built ontop of pyomyo, you may want to check the pyomyo troubleshooting page.
Triple check you are using a version of OpenGloves above v0.4.2 on Steam and that you have named pipe selected as the communication method, especially after any updates to OpenGloves.
Occasionally changes will happen to the NamedPipe interface that OpenGloves offers, thankfully Dan provided a secret branch on Steam that is confirmed to work with this commit. If you type the password neuroglovesarecool into the betas tab in opengloves it'll opt you into the lock_in branch.
Always check the SteamVR developer console. It will launch in a web browser and log any errors that OpenGloves throws. When data is received by OpenGloves via a namedpipe, it should print in the developer console.
The name of the namedpipe might change too, there's one for each hand defined in DeviceProvider.cpp if using the main branch on Steam then it should match the name that's here.
Always check the SteamVR developer console. It will launch in a web browser and log any errors that OpenGloves throws.
For more info see the OpenGloves wiki.
The OpenGloves UI helps you manage your setup, you may wish to make a copy of the config.
The config file is dependent on where you have installed OpenGloves, for example:
D:\Games\SteamLibrary\steamapps\common\OpenGlove\resources\settings
To develop with OpenGlove, you may want to build it locally which may give you multiple copies of OpenGloves installed.
SteamVR will prefer the locally installed version.
In the openvr.paths file (C:\Users\<user>\AppData\Local\openvr\openvrpaths.vrpath, see opengloves/building.md) index in the driver array matters, so it'll prefer smaller indexes if you have two of the same driver name.