Search Issue Tracker
Fixed
Fixed in 14.0.7, 15.0.5, 16.0.1
Votes
1
Found in [Package]
16.0.0
Issue ID
SGB-466
Regression
Yes
Selection of a node is visible, and “ArgumentOutOfRangeException: Specified argument was out of the range of valid values” errors appear when deleting a “Custom Function” node
How to reproduce:
1. Open the user’s attached “Shader graph issue.zip” project
2. Open “Test.shadergraph” (Assets > Shaders)
3. Create a “Custom Function” node
4. Delete a “Custom Function” node
5. Observe the result
Expected result: Node is not visible, and no errors appear
Actual result: Selection of a node is visible, and “ArgumentOutOfRangeException: Specified argument was out of the range of valid values” errors appear
Reproducible with: 14.0.4 (2022.2.2f1), 14.0.6 (2022.2.8f1), 15.0.4 (2023.1.0b6), 16.0.0 (2023.2.0a4)
Not reproducible with: 10.10.1 (2020.3.45f1), 12.1.10 (2021.3.20f1), 14.0.4 (2022.2.1f1)
Reproduced on:
macOS 13.2.1 (Intel)
Windows 11
Notes:
The selection of a node is also visible in the Scene and Game windows
Errors don’t appear on macOS
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
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- 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
Resolution Note (fix version 16.0.1):
Fixed in: 16.0.1 (2023.2.0a9)
Resolution Note (fix version 15.0.5):
Fixed in: Shader Graph 15.0.5 (2023.1.0b13)
Resolution Note (fix version 14.0.7):
Fixed in: Shader Graph 14.0.7 (2022.2.16f1)