nocanwin

Sorry, I should've been more clear. I meant Unity's new OpenXR Plugin. I'm glad you're working on support! I've got inputs from multiple non-handed trackers working in both Unity's Legacy and XR Plug-in system. Nice to see Valve finally added input to the bindings menu for non handed trackers. I'd say that means no more hand editing of binding files, but what gets spit can sometimes be a bit of a mess! 🙂

Is this supported? I tried a while back in Unity and didn't have any luck getting it to work. I spoke to Unity about it and they said I should talk to Valve. I talked to Valve and they said I should talk to Vive, so here I am. @Dario

Thanks for your help @zzy but I'm guessing my GPU just isn't powerful enough. It is a 1060 after all. My CPU isn't at 100%. Did some profiling of and the only thing taking over 1ms is XR.WaitForGPU > Semaphore.WaitForSignal. It bounces between 9m and 19ms. I'm guessing this is because the frame rate is getting halved to 45 when it can't reach 90.

Sorry, an errant PlayerPref was causing my test scene to capture video. That's now fixed and I've made a new standalone build. I'm now getting 12ms in an empty scene with hand tracking. 5ms without hand tracking. Is this more in line with what I should be seeing? 7ms seems high, but my GPU is on the weaker side. I'm using Unity 2019.3 with a Vive Pro Eye. GestureProvider is set to GPU. When I try using CPU I get an error. Start gesture detection failed: CPUOnPC: GetstureProvider.cs:213

Is anyone else running into performance issues? I'm seeing an additional 30ms / frame when I run hand tracking in an empty scene. My gfx card isn't the best, a 1060. What's strange is the sample project runs at 9ms for me. Maybe the quality settings are lower than what I'm building with? @zzy