Search Issue Tracker
In Progress
Votes
0
Found in
1.17.0-pre.2
Issue ID
UUM-140128
Regression
No
Time.deltaTime reports high variance and incorrect frame intervals on Meta Quest 3 when using Vulkan with OpenXR
How to reproduce:
- Open the attached project “IN-138156”
- Switch Build Target to Android and ensure Vulkan is the active Graphics API
- Ensure OpenXR is configured for Meta Quest under XR Plug-in Management
- Build and deploy to a Meta Quest 3
- Wait several seconds for startup frame settling
- Observe the on-screen deltaTime metrics and variance percentage
Actual result: Time.deltaTime shows 25%+ variance
Expected result: Time.deltaTime shows 15% or lower variance (Based on GLES)
Reproducible with: 1.10.0 (6000.0.2f1), 1.17.0-pre.2 (6000.0.71f1, 6000.3.11f1, 6000.4.0b12, 6000.5.0a9)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Reproducible on devices:
Meta Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650
Meta Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno (TM) 740
Notes:
- Time.time and other Time APIs exhibit the same incorrect behavior
- Reproducible in Editor with higher variance
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Component Glyphs value is truncated and Ligature Table glyph fields become inaccessible when increasing the Component Glyphs count
- There is no “Overwrite Preset?” popup when saving a Customizable Toolbar preset with a name that already exists
- Customizable Toolbar preset does not switch to the Unity Default Preset when Reverting All Saved Presets or deleting the active Preset
- New Hierarchy visibility and pickability icon behavior differs from documentation
- [Usability] Selected node gets unselected when undoing changes in the Graph Inspector Node Settings tab
Add comment