fredemmott / HTCC

Hand tracking for flight simulator cockpit clicking
https://htcc.fredemmott.com/
MIT License
61 stars 4 forks source link

Ultraleap driver installation issue #55

Closed guywholikestobreakthings closed 11 months ago

guywholikestobreakthings commented 1 year ago

When trying to make this work for the Ultraleap, if the 3 "workaround" options are enabled PRIOR to launching a Game such as DCS or MSFS, it launched as if there is no Pimax Crystal/VR headset attached and says something along the lines of "OpenXR is not installed or can't launch".

After a lot of troubleshooting, I uninstalled HTCC and everything worked, so tried again, installed fresh copies of everything including 5.16 of UltraLeap, and enabled the 3 Workaround options and got the same thing. If I DISABLED the three options, everything works just fine and launches all of a sudden. It's like the 3 workarounds disable VR in Windows, Odd.

I have a Pimax Crystal. During all of this, the Crystal is recognized by the computer, shows as active, and I can actually hear the game through the headset, it just says there is no VR/OpenXR headset active in the system. I can see the Pimax AND SteamVR home inside the Crystal as well. It's just as soon as those 3 'workaround' settings are enabled, VR is suddenly not recognized at the game level in Windows, but still at the hardware level as Pimax Software still sees it and interacts with it

Make sure you have Gemini v5.16.0 (October 2023) or later installed Set ‘Hand tracking device’ to ‘OpenXR hand tracking’ Optional: enable pinch gestures For v5.16.0, under ‘Workarounds’: Turn on ‘Ignore XR_FB_hand_tracking_aim_pose’ Turn on ‘Force-enable XR_EXT_hand_tracking’ Turn on ‘Force-enable XR_FB_hand_tracking_aim’

fredemmott commented 1 year ago

With the workarounds off, HTCC does nothing with ultraleap due to a bug in their current drivers. If the drivers are not installed correctly , as noted in the configuration app, they will cause game crashes or other issues: they ask for hand tracking even if it’s not supposed to be available when initializing VR, then the VR runtime says “that makes no sense” and refuses to start. If the driver was working correctly, it intercepts that request and prevents it reaching the runtime.

With those options off, it only asks for hand tracking if it’s available; so, either the options result in no change in behavior, or the driver is not working correctly.

Have you tried completely uninstalling ultraleap, installing the new version (not upgrading in place), then rebooting?