You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can name a varying in a visual shader nearly however you want and the generated code just copies the name over 1:1, so you can (accidentally) choose protected keywords. E.g.: varying, float, shader_type , ...
which breaks the shader.
A possible solution would be to always add some sort of suffix/prefix or to prevent the user from choosing such a name: varying => Varying_varying float => Varying_float
Steps to reproduce
Create a new project
Create a VisualShader, apply it to a Material and the Material to a Sprite
Tested versions
System information
Windows 10
Issue description
You can name a varying in a visual shader nearly however you want and the generated code just copies the name over 1:1, so you can (accidentally) choose protected keywords. E.g.:
varying
,float
,shader_type
, ...which breaks the shader.
A possible solution would be to always add some sort of suffix/prefix or to prevent the user from choosing such a name:
varying
=>Varying_varying
float
=>Varying_float
Steps to reproduce
Minimal reproduction project (MRP)
VaryingNaming.zip
The text was updated successfully, but these errors were encountered: