Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.2.2f1
2019.3.0a1
2020.1.0a1
Issue ID
1179018
Regression
No
Fbx model's textures are not extracted when selecting 'Extract Textures' in Import Settings
How to reproduce:
1. Open user's attached '_pubgTest.zip' project
2. Select 'TestCube' in the Project Browser
3. Select Materials Tab in the Inspector
4. Select Extract Textures button
5. Choose the location where textures will be extracted
Expected result: Textures are extracted
Actual result: Textures are not extracted
Reproducible with: 2017.4.32f1, 2018.4.9f1, 2019.2.6f1, 2019.3.0b4, 2020.1.0a4
-
Jacko_K
Jul 28, 2020 06:13
Funny Unreal Engine seems to handle fbx import and texture extraction just fine, did you try Unreal Engine?
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
- “[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
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (2020.1.X):
The issue is on blender's exporter side, there is an embedded texture in this FBX file but it's named TestCube.fbm ( instead of TestCube.png ) so Unity is unable to extract it. No other DCC I tried is able to extract the texture.
Nothing we can do on our side to fix this.