Search Issue Tracker
By Design
Votes
0
Found in
6000.0.12f1
Issue ID
UUM-76558
Regression
Yes
"Show In Inspector" node setting can't be interacted with on project upgrade
Steps to reproduce:
- Download the attached MyProjectt.zip and unzip.
- In the Hub, add this project, and without opening it, upgrade straight to affected version.
- Open Assets > Shadergraphs > 14 to view the shader graph.
- Select the Color property, and try to check Show In Inspector in the Node Settings of the Graph Inspector.
Actual results: This checkbox looks greyed out and can't be interacted with or updated.
Expected results: Checkbox can be updated.
Reproducible with versions: 6000.0.12f1, 6000.0.0b15, 2023.3.0a11
Not reproducible with versions: 2023.3.0a10
Can't test with versions:
- 2021.3.41f1, 2022.3.39f1, project downgrading is not supported.
Tested on (OS): MacOS Intel 12.7.4
Notes:
- This did not occur when upgrading in steps. For example, when I initially opened the project in 2023.3.0a5, then upgraded to 2023.3.0b10, then 6000.0.12f1, I could interact with the checkbox with no problems.
- Project is from UUM-46779, found while following repro steps.
- Attached video of trying to click this checkbox.
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
- [Web][iOS] Web Player keeps restarting on launch when Native C/C++ Multithreading is enabled
- "Add Scene to Scenes in Build" pop-up reappears after Scene has already been added and another Multiplayer Editor Instance is loaded
- TableEntryAdded event is not triggered when a new entry is added in the Localization Tables window
- The macOS Player is built to a different folder than the selected one when the Player is built on Windows
- Editor memory leak in VisualElement when recompiling in a blank URP project
Resolution Note:
A change was made recently to disable the combination of "Global" scope and "Show in Inspector". Global scope is _project global_. Showing it in the inspector means its value will come from the material property declaration, which will effectively prevent it from being set via global settings. Disallowing this option ensures that the global scope property will always be set globally.