Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
2019.3.0a4
Issue ID
1160337
Regression
No
Transform Component displays Z-Axis and X-Axis values changing when Translating a GameObject through X-Axis using Input Vertical
Steps to reproduce:
1. Open users attached project "OccultVoxel.zip"
2. Navigate to Project -> Assets -> Scenes and open "TestScene"
3. In the Hierarchy select GameObject "Player"
4. Enter Play mode
5. Press W or S to move the "Player"
--Notice the Z axis changes in Transform Position of the Player
Expected results: Transform Component Axis values are only changing when a GameObject is moved through those Axis
Actual Results: Z axis value is changing in the Transform Component when Translating a GameObject in the X-Axis
Reproducible with: 2017.4.0f1, 2017.4.28f1, 2018.4.2f1, 2019.1.5f1, 2019.2.0b5, 2019.3.0a4
Note: If GameObject is moved manually in the scene through Z-Axis, the bug will not reproduce after the GameObject is moved
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
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
- "GetPreferedValue" returns max value when using auto-sizing
Resolution Note:
This is due to floating-point inaccuracies caused by the rotation of "Player" object by -90 degrees around the Y axis. The Z values involved are very close to zero (e.g. -3.951758e-08).
You can avoid this by not rotating "Player" by 90 degrees and changing the PlayerMovementScript component to match.