Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 5.6.X, 2017.1.X
Votes
0
Found in
2017.2.0b2
Issue ID
930042
Regression
Yes
"Failed getting triangles. Submesh topology is lines or points" error appears when clicking on a Point Mesh with Static Batching
1. Open the attached "ErrorBug" project and "Scene" scene
2. Double click on "case_930...PointChunk..." point mesh in Hierarchy with the Inspector window opened
Expected result: Focus is taken to Mesh by camera, no error appears in the console
Actual result: Focus is taken to Mesh by camera, "Failed getting triangles. Submesh topology is lines or points." error appears in the console
Notes:
1. To reproduce the error again, toggle Mesh Renderer component off and on repeatedly
2. Bug does only happen with Static Batching enabled
Regression introduced in - 5.6.0b2
Reproducible with - 2017.2.0b2, 2017.1.0f3, 5.6.2p2, 5.6.0b2
Not reproducible with - 5.6.0b1
Fixed in 2017.3.0b6
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
DeathRace26
Sep 06, 2019 18:59
This is NOT fixed, it appears in 2018.4.8f1 when baking occlusion. I would like to know what exactly causes this issue because its really annoying...