Search Issue Tracker
Fixed
Fixed in 2023.3.0a11
Votes
0
Found in
2021.3.29f1
2022.3.7f1
2023.2.0b5
2023.3.0a4
Issue ID
UUM-46779
Regression
No
Shader Graph property default values are lost when the property is no longer exposed
When making a property not exposed in Shader Graph, the default value is lost/reset
Repro steps:
* Download this project: [https://drive.google.com/file/d/1u2UPlJULOjRtKe-hwUOeKcOGXwvVUIu4/view?usp=sharing]
* Open the shader graph asset number 14
* Open the Sample Scene too - a sphere with the material using that shader graph shader should be loaded.
* select the color property and make it not exposed anymore
Expected result:
* the material in the scene should still have the blue outline, like the material preview in the shadergraph editor and like the previously set default value
Actual result:
* the material has no glow (as if the color property reverted to black instead)
Note: I tested this with 2023.2, 2023.1 and 2022.3. (all with their latest respective shadergraph packages) . This issues doesn't seem to be a regression.
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
- “[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
Resolution Note (fix version 2023.3.0a11):
verified as fixed in 2023.3.0a11 and ShaderGraph 17.0.1