Wrong timing for animations in XR

If there are no animations already running, the progression of an animation in XR will be calculated from the time the application started instead of when the animation was started. This means that e.g. a Behavior on a property will normally be ignored, and the value will immediately jump to the final value

The root cause is that QQuick3DXrAnimationDriver::elapsed() returns the time since the app was started.