Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
9.0.0
Issue ID
1222539
Regression
No
[Shadergraph] Renaming Enum Keywords appends new reference name to Shader Keywords instead of replacing the previous one
Repro Steps:
1. Assign a Shadergraph to a material
2. Change an Enum Entry Name (Suffix), Save Shadergraph
3. Change Enum Reference, Save Shadergraph
4. On the Material, change the Enum that's currently selected to any other option.
5. Change your inspector to Debug Mode, observe the Shader Keywords field.
Actual Results:
Shader Keyword would be replaced with the new reference prefix+suffix combo
Expected Results:
Shader Keyword is appended with the new reference prefix+suffix combo
Additional Note:
After reproducing the issue, observe the SavedProperties Field. Notice that the old Keyword reference name is still present within the float list. This may or may not be related to this issue.
Reproduced on:
Editor 2019.3.2f1, Shadergraph v7.1.8
Editor 2020.1.0a23, Shadergraph v9.0.0
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
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
- Loading animations are hitching or stopping when using "SceneManager.LoadSceneAsync" to load new scenes
This is a duplicate of issue #1176077