Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.3.11f1
2018.4.0f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1185338
Regression
No
.obj and dependency .mlt files lost all Materials and Textures when importing them into Unity Editor
To reproduce:
1. Download the project from a Link and open in Unity
2. Open "SampleScene" scene
3. From Resources > bugatti drag and drop "bugatti.obj" file to the Scene
4. Observe that the imported Model is with all his Materials and Textures
5. Resources > IronMan drag and drop "IronMan.obj" file to the Scene
Expected results: Just as previous model, this one also has all his Materials and Textures
Actual results: "IronMan.obj" does not have any Materials and Textures
Notes:
- We looked up the FogBugz and found the case 987190 which is very similar to this issue,
so we suggest the Client change the Material import setting to "Use external Material", but it does not work
- Link to the Project is Shared in Comments section
Reproduced on Unity 2017.4.0f1, 2017.4.32f1, 2018.4.10f1, 2019.2.7f2, 2019.3.0b5 and 2020.1.0a5
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):
Obj imports are done through the FBX SDK, a fix is likely to be difficult and take a long time. We don't have a lot of resources and this issue does not seem to affect a lot of users so 'll close it now but feel free to re-open if you think it's the wrong decision. I'd suggest using another format or re-work the content prior to export as a workaround.