Search Issue Tracker
By Design
Votes
0
Found in [Package]
2.0.3
Issue ID
1193946
Regression
No
[FBX Exporter] is not exporting Game object's LODs
How to reproduce:
1. Open attached project ("FBXExporter.zip")
2. Open SampleScene scene
3. In Hierarchy window right-click Wheel Game object
4. Select menu option "Export To FBX..." and export it
5. Add exported FBX file to the scene
Expected result: Exported FBX contains LODs (LOD group component)
Actual result: Exported FBX is without LODs (LOD group component)
Reproducible with: 2018.4.13f1, 2019.2.13f1, 2019.3.0b12, 2020.1.0a14 (FBX Exporter 2.0.3 P3)
Could not test with: 2017.4.34f1 (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:
It is not currently on the roadmap to export the LOD group from Unity as FbxLODGroup. The reasons for this are that FbxLODGroup does not get imported into Unity, and the LOD group formats do not match (threshold based on screen space height in Unity vs distance in FBX).
To have the LOD group created on import into Unity the naming convention of the objects has to match what is indicated here: https://docs.unity3d.com/Manual/importing-lod-meshes.html