Search Issue Tracker
Fixed in 2018.2.16f1
Votes
7
Found in
2018.2.13f1
Issue ID
1092186
Regression
Yes
The "Materials" tab in the Inspector window is empty when inspecting an imported .fbx file
How to reproduce:
1. Open the attached project (materials.zip)
2. In the Project Window, navigate to "Assets", select "cube"
3. Navigate to the "Materials" tab in the Inspector Window
4. Observe the error in the Console as well as an empty "Materials" tab
Expected result: Materials are able to be viewed and edited, no errors are thrown
Actual result: Materials tab is empty, errors are thrown
Reproducible with: 2018.2.13f1
Not reproducible with: 2017.4.0f1, 2017.4.13f1, 2018.1.9f2, 2018.2.12f1, 2018.3.0a1, 2018.3.0b7, 2019.1.0a5
Notes: The error which appears has been attached by the user (error message.txt)
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
- Warning 'Unable to find player assmebly' is thrown when building some Project Templates
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
Acid-NN-9
Nov 14, 2018 20:59
The same bug is back in 2018.2.15f1
Zyrathius
Nov 14, 2018 18:53
Yes, same for me, Issue returned with latest update 2018.2.15f1.
jerbuckeye
Nov 13, 2018 17:58
Issue seems to be re-introduced into 2018.2.15f1
rawalanche
Nov 11, 2018 12:23
Yes, I can confirm that this bug is back in 2018.2.15f1. :(
playemgames
Nov 10, 2018 02:05
This bug is back in 2018.2.15f1
jerbuckeye
Oct 25, 2018 21:04
When is 2018.2.14f1 coming out?
DennisVH
Oct 23, 2018 10:29
Same here, is an issue since 2018.2.13f1. Older versions work fine.
cmyd
Oct 22, 2018 06:58
Agreed, Getting the same issue on 2018.2.13f1.