Search Issue Tracker
Fixed in 9.0.0
Votes
0
Found in [Package]
7.0.1
Issue ID
1205411
Regression
Yes
[Shader Graph] Property's reference names are allowed to start with a number, plugging it in results in a parse error
Repros in 7.0.1, 7.1.7, and SRP master
Doesn't repro in 6.9.1
Repro steps:
1. Create a shadergraph and open it
2. Add a blackboard property
3. Name the property anything beginning with a number
4. Drag the property onto the graph and plug it into the master node
Expected result: if you name the property something starting with a number, it will prefix it with an underscore (this is the behavior in 6.9.1 and earlier)
Actual result: you are allowed to name the property something starting with a number, and plugging it in will cause parse errors on the master node.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment