Search Issue Tracker
Fixed
Fixed in 2023.2.0a7
Votes
0
Found in
2021.3.18f1
2022.2.6f1
2023.1.0b5
2023.2.0a5
Issue ID
UUM-27820
Regression
No
Joint.connectedAnchor is different in Player vs in Editor when not set explicitly
Reproduction steps:
1. Open the attached Project “BugRepro”
2. Enter Play Mode
3. Observe how one of the Cubes moves towards the other
4. Build and Run the Project on Oculus 2
5. Observe the Cubes
Expected result: Cube 1 moves towards Cube 2
Actual result: Cube 1 stays in place
Reproducible with: 2020.3.44f1, 2021.3.18f1, 2022.2.6f1
Couldn’t test with: 2023.1.0b3, 2023.2.0a2 (Crashes when launched on a device)
Reproducible on: Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Note: Issue is reproducible in both Play Mode and in Player with version 2020.3.44f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- Inconsistent hotkeys in the Terrain tool with the "Terrain Tools" installed and not installed
Add comment