Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3.0a9
2019.3.0f1
2020.1
Issue ID
1209911
Regression
Yes
Build throws "One of the triangles is too large" when an object with "Mesh Collider" and "Generate Colliders" enabled is present
How to reproduce:
1. Open attached project "physics triangle edge too long.zip"
2. In Inspector window, observe the "golemplains terrain" children have "Mesh Collider" component
3. In Project window, observe the "golemplains terrain" "Generate Colliders" is enabled
4. Build and Run
5. Observe the Console window
Expected result: error containing additional information, for example, which scene contains the object, how large the triangles should be
Actual result: error specifies which object is causing the error
Reproducible with: 2019.3.0a9, 2019.3.0f5, 2020.1.0a18
Not reproducible with: 2017.4.36f1, 2018.4.15f1, 2019.2.18f1, 2019.3.0a1, 2019.3.0a8
-
Marcos-Elias
Mar 26, 2020 21:43
Well... I'm getting this error with 2919.3 with some Probuilder meshes.
How to fix it? I have lots of scenes, it does not say where the object is located:Failed to create Physics Mesh from source mesh "pb_Mesh2982286". One of the triangles is too large. It's recommended to tesselate the large triangles.
Failed to create Physics Mesh from source mesh "pb_Mesh200138". One of the triangles is too large. It's recommended to tesselate the large triangles.
Failed to create Physics Mesh from source mesh "pb_Mesh898780". One of the triangles is too large. It's recommended to tesselate the large triangles.
Even opening scene by scene I cannot see right into the hiearchy, I must select the object, one by one, and see inspector... For hundreds of scenes... That really sucks.
I'll NEVER use any other Unity tool to modelling, tired of Probuilder bugs at some major upgrades. So frustrating. :(
Many days lost just to do a simple upgrade.
-
BuzzJive
Mar 16, 2020 19:11
This is not a resolved issue. In previous builds this would fail silently, which was not the best solution, but neither is the way it will cause full builds to fail now. A PC build with a triangle like this will not succeed. A middle solution of showing the error as the proper warning that it is but allowing a build would be far better than it is now.
-
timbo3DDev44
Jan 22, 2020 02:18
This is not an improvement as the old way still worked very well. Please can more information be provided when this fails at least
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 mecanim::SetValueWeight when switching the AnimationMixerPlayable connection with Animator's UpdateMode set to "Animate Physics"
- The "StringComparer.InvariantCultureIgnoreCase.GetHashCode()" returns different Hash Codes for the same word with the only difference being case sensitivity in WebGL
- 2D Light Textures show the lights of any 'blend style' index higher than theirs (if present) when they aren't visible by the Camera using Render Graph
- [SpeedTree] Wireframe mode not rendering correctly ST assets
- Light2D affecting only the Default Sorting Layer will also affect any Custom Lit Sprite not on that Layer when using Render Graph
Resolution Note:
In the current version of PhysX, a large triangle is one that has at least one of the edges longer than 500 * mesh_scale. This check will depend on PhysX version, and the API doesn't communicate back the details, only the error message and the status. Priorly, in the older versions there wasn't be even a message, just the failed status so it's an improvement compared to how it worked before actually.