Search Issue Tracker
Fixed
Fixed in 2020.3.45f1, 2021.3.19f1, 2022.2.6f1, 2023.1.0a26
Votes
1
Found in
2022.2.0a15
2023.1.0a6
Issue ID
UUM-13268
Regression
No
Improve error message for: SkinnedMeshRenderer: Mesh has been changed to one which is not compatible with the expected mesh data size and vertex stride. Aborting rendering.
Steps
# open Assets/Repro/SetTangent.unity
# enable gizmos in scene view or game view
# check console for errors
error message : SkinnedMeshRenderer: Mesh has been changed to one which is not compatible with the expected mesh data size and vertex stride. Aborting rendering.
Expected: Mesh and gameobject name is shown in console
Actual: No indication exactly what asset / object caused the error
Repro (error is missing info): 2022.2.0a15
no repro (no error): 2023.1.0a4
NOTES:
* seems either root cause of error is fixed in latest, or a regression happened causing the error to no longer appear in 2023.1
Comments (1)
-
KineticBen
Aug 09, 2023 12:27
Still getting this issue in 2022.3.5
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
- Manual reference page for Grid Selection is missing
- Awaitable.NextFrameAsync causes GC Alloc 0.7 KB when using CancellationToken
- Prefab "Overrides" list item popups are overridden when navigating with keyboard arrow keys
- Alpha Tolerance setting does not affect generated outlines when generating Custom Physics Shape in the Sprite Editor
- The information/help message section misses a margin in the "Profiler" window
Resolution Note (fix version 2023.1.0a26):
Confirmed improvement in 2023.1.0a26 - now the object that caused the error can be located by double-clicking the error message in the console tab (this will ping the object in the hierarchy tab, showing where the error came from).
Resolution Note (fix version 2022.2.6f1):
Confirmed in 2022.2.6f1
When the error occurs, the user can now double-click the error in the console to ping the object in hierarchy which has the SkinnedMeshRenderer component which caused the error.
Resolution Note (fix version 2021.3.19f1):
Confirmed fixed in 2021.3.19f1
When the error occurs, the user can now double-click the error in the console to ping the object in hierarchy which has the SkinnedMeshRenderer component which caused the error.
Resolution Note (fix version 2020.3.45f1):
Confirmed in 2020.3.45f1
When the error occurs, the user can now double-click the error in the console to ping the object in hierarchy which has the SkinnedMeshRenderer component which caused the error.