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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
FBX Exporter does not currently support object visibility.