Search Issue Tracker
Fixed
Votes
1
Found in
5.3.5f1
Issue ID
799597
Regression
No
FindScriptByClassName Does Not Account for Namespace-Qualified className
Icons for Scriptable Objects with namespace are displayed incorrectly (default asset icon).
To reproduce:
1) Open the attached project.
2) Go to the Assets folder.
- In the Editor folder there are 2 scripts 'SampleScriptableObject1' which uses a namespace and 'SampleScriptableUnity2' which does not. There are also 2 scriptable objects 'New Sample Scriptable Object 1' and 'New Sample Scriptable Object 2' derived from the scripts.
- The icon of 'New Sample Scriptable Object 2' is shown as the default Unity asset icon, even though the script associated with it has a green icon. The scriptable object derived from the script which doesn't use the namespace is displaying as expected.
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
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Prodigga
Jun 06, 2017 02:02
Nevermind - just something funky happened, had to reimport the assets with the icons to make it appear after I changed the scripts namespace.
Prodigga
Jun 06, 2017 02:02
Nevermind - just something funky happened, had to reimport the assets with the icons to make it appear after I changed the scripts namespace.
Prodigga
Jun 06, 2017 01:52
Still an issue in 2017.1 guys