Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2020.3.38f1
2021.3.9f1
2022.1.15f1
2022.2.0b7
2023.1.0a10
Issue ID
UUM-13290
Regression
No
Shader error is shown when using a custom shader
Reproduction steps:
1. Open the attached “IN-14498” project
2. Observe Console Window logs
Expected result: No shader error is shown in Console Window
Actual result: Shader error is shown in Console Window
Reproducible with: 2020.3.38f1, 2021.3.9f1, 2022.1.15f1, 2022.2.0b7, 2023.1.0a10
Reproducible on: Windows 10 Pro 21H2
Note: Shader error in 'NewSurfaceShader': Parse error: syntax error, unexpected TVAL_RGBAFLAGS, expecting TOK_SETTEXTURE or '}'
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note:
We can only fix this when we rewrite the ShaderLab parser.
That said, it looks like you can work around the issue by setting the color mask for all render targets first and overriding for all others after that, e.g.
ColorMask [_ColorMask0]
ColorMask [_ColorMask1] 1
Resolution Note (2023.1.X):
We can only fix this when we rewrite the ShaderLab parser.
That said, it looks like you can work around the issue by setting the color mask for all render targets first and overriding for all others after that, e.g.
ColorMask [_ColorMask0]
ColorMask [_ColorMask1] 1