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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Add comment