Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
Issue ID
1139180
Regression
No
[FBX Exporter] ASCII Model has incorrect BlendShape normals when exported from FBX
How to reproduce:
1. Open attached project
2. Open SampleScene
3. Look at the to cubes in the scene and notice that their normals are different
Reproducible with: 2018.3.11f1, 2019.1.0b9, 2019.2.0a10
Not reproducible with: 2017.4.24f1 because models did not import correctly.
Actual results: ASCII Model is different from binary FBX Model
Expected results: both ASCII and FBX should look the same once imported
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
The ASCII file contains invalid data.