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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
Add comment