Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3
2019.3.0a8
2020.1
Issue ID
1201330
Regression
No
Prefabs have their Y position displayed incorrectly when they are Instantiated with Transform.Position.Y 0
Steps to reproduce:
1. Open user's attached project "StylizedPrototype1.zip"
2. Open "OwnPrototypeTry2" scene
3. Click Play.
4. Move to an area with good visibility using WASD.
5. Using the mouse, aim at the flat area of the terrain
6. Repeatedly press F aiming at different areas(for different GameObjects to be spawned)
7. Look into the console. There you should find as many entries saying: "Spawned Terrain *objectSpawned* *y-value*". Some of these y-values should be 0, some -2.384186e-07 and some +2.384186e-07.
Expected results: Transform.Position.Y is 0 if an object is at Transform.Position.Y==0
Actual results: Objects that are at Y=0 have their Transform.Position.Y displayed as +2.384186e-07. or -2.384186e-07. or any other strange numbers
Reproducible with: 2019.3.0f1, 2020.1.0a15
Note: Unable to open 2019.2 and lower due to error "Failed to load 'C:/Users/augustinas.zigunis/Downloads/case_1201330-StylizedPrototype1/Assets/New Terrain 1.asset' because it was serialized with a newer version of Unity. (Has a higher SerializedFile version)
"
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
- [Scene View][Ubuntu] Prefab mode UI ghosting in HDRP
- Deleting AudioMixer asset throws MissingReferenceException and breaks the Audio Mixer window
- Crash on ScheduleGenerateTilingShape when modifying PolygonCollider2D path count and setting path vertices
- Crash when a scene is created with LocalPhysicsMode::Physics3D
- [HDRP] Light doesn't bounce off terrains
Resolution Note:
Physics raycasting and other are not guaranteed to give exact values due to floating point precission