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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
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.