Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
Issue ID
364916
Regression
No
We should collect FBX exporter errors and warning during conversion
Attached mesh looks corrupt when imported from FBX. FBX exporter gives a bunch of warnings and one error when exporting it. The error is:
"The polygon mesh contains invalid faces and needs to be corrected by the application.
The following nodes are affected and only their transform data has been exported:
-giraffe"
I believe it's causing the problem. We should gather errors and warnings from FBX exporter (when importing directly from mb, max, and so on) and show them in Unity, so users are aware that something went wrong.
This will allow us to throw errors from within mel scripts too.
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 JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment