Search Issue Tracker
Fixed in 2018.2.0f1
Fixed in 2018.2.X
Votes
0
Found in
2018.2.0b6
Issue ID
1049204
Regression
No
EditorGUIUtility.PingObject() does not work if Packages root is closed
Reproduction steps:
1. Open the attached project "New Unity Project (13).zip";
2. Make sure the Project View is in single-column mode;
3. Make sure the "Packages" root has its contents hidden (triangle pointing right);
4. Choose Tests>Ping Packaged Asset;
Expected results: Packages folder will be pinged.
Actual results: Only error occurs in the console and nothing happens.
Notes:
Trying the same thing with a user asset (making sure to first hide the contents of Assets, and choosing the appropriate menu item) works as expected.
This bug is not apparent in two-column mode.
Reproduced on: 2018.2.0b1, 2018.2.0b9, 2018.3.0a3. (Packages folder is showed in the Project view only from 2018.2.0b1)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Add comment