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
Comments (1)
-
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.