Search Issue Tracker
Won't Fix
Votes
1
Found in
2022.3.38f1
6000.0.11f1
Issue ID
UUM-75808
Regression
No
Shader Graph "use of undeclared identifier" error when using a custom function that references a graph property
How to reproduce:
1. Open the attached “IN-80312“ project
2. From the “Project” window select the “GeneratedFromGraph-Test“ file
3. See the “Imported Object“ section in the Inspector window
Expected result: The shader compiles successfully
Actual result: Error message "use of undeclared identifier" is shown
Reproducible in: 2022.3.38f1, 6000.0.11f1
Could not test with: 2021.3.40f1(Could not resolve package errors)
Reproduced on: Windows 11 Pro
Not reproduced on: No other environment tested
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Resolution Note:
Recommend creating and input port and linking the material property via the graph. Custom function nodes are not intended around supporting global access to the entire shader (though many things will work), so we likely won't fix this.