Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.35f1
2021.3.5f1
2022.1.6f1
2022.2.0a17
2023.1.0a2
Issue ID
UUM-768
Regression
No
Assigning transform.position can be inaccurate when the transform's parent is rotated
How to reproduce:
1. Open the attached Project "PositionDebug.zip" and load Scene "PositionDebug"
2. Enter Play Mode
3. Observe the Game View
Expected results: The Cube in the Scene is stationary
Actual results: The Cube is moving
Reproducible with: 2019.4.39f1 2020.3.35f1, 2021.3.3f1, 2022.1.2f1, 2022.2.0a15
Note:
- Issue is dependent on the values of transform.rotation of the parent GameObject and the transform.position of the child GameObject that gets the transform assignment. Not all value combinations will reproduce the issue
- It appears like some value combinations provide more movement than others
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
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
- Operations on the Color32 array are not reflected in WebGL Player when HDR is off
- Rigidbody moves away from the original GameObject when Center of Mass is set in every frame
- WebGL Player does not proceed beyond logo screen when "Target WebAssembly 2023" is enabled
Resolution Note:
Due to floating point imprecision there can be a small difference between the global position returned from GetPosition() than that which was set with SetPosition().
The difference depends on the object's specific transform hierarchy and depth.
It is therefore expected that an object might move very slightly when running the script code: "transform.position = transform.position;"