Search Issue Tracker
By Design
Votes
1
Found in [Package]
4.1.0
Issue ID
FBX-137
Regression
No
[STRETCH] [FBX Exporter] Game Object visibility is not respected when Game Object is exported as FBX
How to reproduce:
1. Open the user's attached project ("FBXExporter.zip") using the EnvIronman VM (more information in Edit).
2. Open SampleScene scene
3. Right-click on VisibilityBug Game Object
4. Select "Export To FBX..." option and export Game Object
5. Add Exported Game Object to scene
Expected result: FPX Game Object children are not visible
Actual result: FBX Game Object children are visible
Reproducible with: 2.0.1 (2018.4.12f1), 2.0.3 Preview-3 (2019.2.11f1, 2019.3.0b9, 2020.1.0a11)
Not tested 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:
FBX Exporter does not currently support object visibility.