Search Issue Tracker
Fixed in 3.2.0-preview.2
Votes
1
Found in [Package]
2.0.2 Preview 1
Issue ID
1185725
Regression
No
[FBX Exporter] FBX model bone positions are lost when model is exported from Game Object generated in Play mode
How to reproduce:
1. Open attached project ("Runtime FPS Exporter.zip")
2. Open SampleScene scene
3. Enter Play mode
4. Right-click on FBX Model in Hierarchy window
5. In the opened menu click on "Export to FBX..."
6. In Export Options window click Export
7. Drag and drop "FBX Model.fbx" from the Project window to the Scene window
Expected result: Exported FBX looks the same as it is generated during Play mode
Actual result: Exported FBX bone positions are lost and they all are in the same position
Reproducible with: 2018.4.10f1 (FBX Exporter 2.0.2 Preview 1), 2019.2.7f2 (2.0.2 P1), 2019.3.0b4 (2.0.2 P1), 2020.1.0a5 (2.0.2 P1)
Not reproducible with: 2017.4.32f1 (Package Manager was not present)
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 (fix version 3.2.0-preview.2):
Fixed with 2018.4.24f1 (3.2.0-preview.2)