Search Issue Tracker
In Progress
Fixed in 2022.3.13f1, 2023.3.0a8
Fix In Review for 2021.3.X
Votes
0
Found in
2021.3.29f1
2022.3.7f1
2023.2.0b5
2023.3.0a4
Issue ID
UUM-46774
Regression
No
(Built-In) Custom Editor GUI for a ShaderGraph is not used when the GUI name starts with any letter after U
Reproduction steps:
1. Open the “ShaderCustomEditor“ project
2. Select the “MyMaterial“ asset and observe the Inspector
Expected result: “Hello World!“ is visible
Actual result: “Hello World!” is not visible meaning the specified Custom Editor GUI is not used
Reproduced in: 2021.3.7f1, 2022.3.7f1, 2023.1.8f1, 2023.2.0b4
Not reproduced in: 2021.3.8f1, 2021.3.29f1
Reproduced using: macOS 13.4.1 (Intel), macOS 13.5 (M2)
Workaround: Rename the custom Editor GUI script and its class to start with U (Unity) or any prior letter
Similar old bug: [https://issuetracker.unity3d.com/product/unity/issues/guid/1380485/]
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment