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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (fix version 3.2.0-preview.2):
Fixed with 2018.4.24f1 (3.2.0-preview.2)