Hi, The black box driver estimating the handler position and velocity
using, it seems, a Kalmann and an inertial filters, obtains degraded
results as compared what it obtained before. More precisely, if the
handler comes from outside the FOV of the t...
Hi,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 ...
Hi,With both Oculus Quest and Oculus Quest 2n in Unity 2021, 2022 (LTS
versions), TryGetFeature(CommonUsages.deviceAcceleration) returns
Vector3.zero. It is also the case with all acceleration features
(rotationAngularAcceleration). This is the case ...
Hi, For my application, I need to access the noisy positions (and if
possible velocities) the Oculus Quest heaset uses as input for its
Kalman filter (and inertial filter) whenever they are available and even
if Kalman filter output positions and vel...
I encounter also feature issues as concerned for OpenXR. Several basic
parameters, like acceleration, are no longer retrieved, which is
problematic, since Meta Quest is an autonomous headset without exterior
handler detectors. When the handler is not...
Thank you @Eire_Max,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.
Hi @Eire_Max,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 vulnerab...
HiThank you @Eire_Max. I will ask them. Each time I see a driver update
on the headset, I feel a cold sweat. My development push the Meta Quest
over its limits, and any regression or modification can put my projects
in jeopardy.
Hi Eire_Max,Thank you for the link, I didn't find a location for bug
reporting to meta. Conversely, I know exactly when the bug appeared
(more than 2 years ago)
