Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.0.1-preview.5, 3.0.0-preview.2
Issue ID
1201937
Regression
No
[FBX Exporter] Embedding of resources is not possible when exporting FBX files
How to reproduce:
1. Open the attached project ("case_1201937-FBX-Hierarchy.zip")
2. Open the repro scene ("SampleScene")
3. In the Hierarchy tab, right-click "Group" object and select "Export To FBX"
4. Export it to any directory in the Assets folder
5. Drag the newly exported FBX file in the scene and compare it to the original
Expected results: Both FBX files have the same textures
Actual results: Newly exported FBX file has different textures
Reproducible with: 2018.4.16f1, 2019.2.19f1, 2019.3.0f5, 2020.1.0a20
Couldn't test with 2017.4 (package is not supported)
Reproducible with package versions: 2.0.1-preview.5, 3.0.0-preview.2
Workaround: Ensure unique material/texture names, or remap materials manually after the export.
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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
Resolution Note:
We evaluated embedding textures and that comes with its own headaches when doing a round-trip.
What we do instead as of 3.1.0-preview is that when you convert to a prefab (different from doing an FBX export), the Unity materials get kept, so the DCC gets something with mediocre reference materials -- but the Unity scene looks fine.