Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.3.6f1
2020.2
Issue ID
1230280
Regression
No
Shader fails to compile when Shader header uses non english alphabet characters
Steps to reproduce:
1. Open User-supplied project
2. Inspect the material
Expected: its shader fails to compile.
Actual: its shader compiles
Reproduced in: 2018.4.20f1, 2019.2.21f1, 2019.3.6f1, 2020.1.0b3, 2020.2.0a4
Note: If you comment out the header: [Header(This doesn't work: + - / * ^ ' " å ä ö é @ $ % ? ;)], the shader will compile
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
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Resolution Note:
Currently we do not intend to support UTF-8 character in the shaderlab property fields. This is unlikely to change in the near future.