Whatever the Meta Quest version 1, 2 & 3, whatever the node or device, on Unreal Engine 5.4.4 and on Unity 2021 to 6000, the requested acceleration is (0, 0, 0) and the requested angular acceleration is (0, 0, 0).
In Unity, these (0, 0, 0) vectors are obtained using the TryGetFeatureValue(CommonUsages.deviceAcceleration, out deviceAcceleration) and TryGetFeatureValue(CommonUsages.deviceAngularAcceleration, out deviceAngularAcceleration) methods (but also using OpenXR)
In UnrealEngine, they are obtained using the GetRawDeviceData in a blueprints.
The bug has 100% repeatabilty and is very easy to reproduce
Consequently:
There is no way to get the acceleration for the Meta Quest
The problem is neither Unity nor UnrealEngine nor OpenXR --> is has to be a Meta bug
This type of issue is out of my expertise unfortunately 😅 but if you haven't done so already, I would recommend submitting a Bug Report to alert the Engineering Team of you issue. The steps to do this can be found here!
Unfortunately, the page of your link is inadequate for a developer debug. I can't send projects and not even provide screenshots. "Meta's Bug Bounty Programme" is the appropriate format for bug report, but it is stated "security vulnerability". Would an issue concerning non returned inputs be appropriate for the "Meta's Bug Bounty Programme" ?
Thanks for getting back in touch, I don't believe your issue would apply for the Meta Bug Bounty program, as you said, it doesn't really qualify under "security vulnerability".
As I say, I'm not really a developer by trade but I would recommend accessing the developer support resource found hereto see if there is a resolution for your issue.
I just sent a bug report. I looked in detail at OVR_Plugin.h. So much is lost when using OpenXR. That is a pity that Meta forces our hand toward a much less detailed access to Meta Quest input.
