Afiya
`IVRSystem::GetControllerState()`, `IVRSystem::GetControllerStateWithPose()`, `IVRSystem::TriggerHapticPulse()`, `IVRSystem::GetButtonIdNameFromEnum()` and `IVRSystem::GetControllerAxisTypeNameFromEnum()` are deprecated in favor of the new input system. Use the `IVRInput` interface, its documented pretty well in the [`openvr.h` header](https://github.com/ValveSoftware/openvr/blob/master/headers/openvr.h#L4906-L5042)
That is indeed weird, considering how a freshly built one only links like 5 libs ```bash $ ldd ./libopenvr_api.so linux-vdso.so.1 (0x00007ffe6b30a000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fa6b6da3000) libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fa6b6bc1000) libm.so.6...
@ChristophHaag huh, didn't know that, that also explains the currently broken builds
@sphaero my bet for that would be no, considering how there were no updates for 9 months now...
`IVRDisplayComponent` is well.... weird and really sensitive to it's props, I wish we had full documentation of this interface
I mean you can make this list yourself if you want to
From the last video it looks like you're translating your rotation values to quaternions incorrectly, i had a similar issue with a math library about a year ago, it was...
Yeah looking at your math it's good, the only other thing coming to mind is maybe the order of operations maybe, but that should not matter also if you don't...
Yeah i meant world global frame and it not being the issue is more important, then you're either passing the quaternions to pose structs incorrectly *or* it's something else before...
Ok now im concerned about the math again... but also your pose struct, can you show your entire pose struct that gets used as the device's pose? And about what...