Search Issue Tracker
By Design
Votes
1
Found in [Package]
4.1.0-pre.2
Issue ID
FBX-166
Regression
No
Asset gets exported in ASCII when exporting via Script and the Export Format is set to 'Binary'
How to reproduce:
1. Open the attached '1338169.zip' project
2. Open the SampleScene
3. In the Hierarchy select the 'Sphere' GameObject
4. In the top bar menu select 'BugReport' > 'Export selected GameObject as FBX'
5. Open the 'MyExport' Asset in a text editor
Expected result: The Asset is in binary
Actual result: The Asset is in ASCII
Reproducible with: FBX Exporter 2.0.3-preview.3 (2018.4.35f1, 2019.4.28f1, 2020.3.11f1, 2021.1.10f1, 2021.2.0a19), 4.1.0-pre.2 (2019.4.28f1, 2020.3.11f1, 2021.1.10f1, 2021.2.0a19)
Comments (1)
-
Peter77
Jun 23, 2021 12:17
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
- Errors “RenderPass: Attachment 0 is declared as depth attachment but RGBA8 sRGB is not a valid depth format.“ and “BeginSubPass: Not inside a Renderpass“ are present when using Native RenderPass with a RenderTexture that only has depth output
- ArgumentOutOfRangeException is thrown when an empty DropdownField is clicked at runtime
- [tvOS] "EXC_BAD_ACCESS" error is thrown when Painter2D.ClosePath is called
- Bad Naming Convention in Shortcuts Window for Sprite Shape Editing
- Bad Naming Convention in Shortcuts Window for Shader Graph
Resolution Note:
As designed, the public API always uses a fixed set of options.
We are looking into improving the public API so we're taking account of this ticket as a feature request.