Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.4.1p4
Issue ID
851762
Regression
No
Custom mesh made w/ script w/ big vertice coordinates on one axis, shows up mangled
Steps to reproduce:
1. Download an open attached project "DTM.zip"
2. Open scene DTM and play it
3. Move scene view around
Actual result: Mesh is shown as screenspace object, instead of normal world space mesh, with constantly moving vertices when moving view camera (see: https://gyazo.com/1e03f17525379c4817fb3764fe67d3e9 )
Expected result: A warning, or nothing shown as in case of all three coordinates beeing big valued instead of one
Notes: Turning on shaded wireframe or wireframe view lets to see the issue better.
If the view is aligned with one of the axis (press on gizmo on right corner), the mesh disappears.
Tested and reproduced on:
Windows 10
Unity 5.2.5f1, 5.3.7p1, 5.4.1p4, 5.4.3p1, 5.5.0f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment