Search Issue Tracker
Fixed in 1.0.0
Votes
3
Found in [Package]
1.0.0
Issue ID
1375087
Regression
No
[Quest][XR] Dragging a ScrollRect makes it disappear and set NaN values
Reproduction steps:
1. Open the attached user's project "VR.zip"
2. Build for Quest 1/2
3. Use the controller to grab, move and let loose in quick succession
Expected result: Dragging a ScrollRect does not make it disappear and set NaN values
Actual result: Dragging a ScrollRect makes it disappear and set NaN values (see attached Repro.mp4)
Reproduces on: XR IT 1.0.0-pre.2 - 2.0.0-pre.5 (2020.3.24f1, 2021.2.5f1, 2022.1, 2022.2.0b1)
Could not test below XR IT 1.0.0-pre.2 due to errors in the console
Notes:
-Issue does not reproduce in the Editor (with oculus link)
-
eliphat
Dec 04, 2022 03:39
The problem also occurs on several android devices, in Unity 2021.3.1f1
-
rdmont
Apr 01, 2022 09:42
Seeing this in Unity 2021.2.17f1, with XR IT 2.0.1.
-
intexteel
Feb 25, 2022 18:48
Seeing this in Unity 2021.2.10f1.
Upgrading XR IT to latest version seemed to have improved it initially, but then other panels broke anyway.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (fix version 1.0.0):
We discovered a frame timing issue on Oculus Quest builds that causes the unscaledDeltaTime value to get set to 0, cascading to the ScrollRect component which uses that value for a velocity calculation, resulting in an invalid number. A fix has been applied in both places to prevent future issues.
Resolution Note (fix version 1.0.0):
We discovered a frame timing issue on Oculus Quest builds that causes the unscaledDeltaTime value to get set to 0, cascading to the ScrollRect component which uses that value for a velocity calculation, resulting in an invalid number. A fix has been applied in both places to prevent future issues.
Resolution Note (fix version 1.0.0):
Fixed in: 2021.3.2f1
Resolution Note (fix version 1.0.0):
We discovered a frame timing issue on Oculus Quest builds that causes the unscaledDeltaTime value to get set to 0, cascading to the ScrollRect component which uses that value for a velocity calculation, resulting in an invalid number. A fix has been applied in both places to prevent future issues.