Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
Issue ID
1274141
Regression
Yes
[Bug] [HLSLcc] Bad codegen on GLES2/3 when using "precise" keyword
Using a shader with a "precise" keyword on a variable produces code that doesn't compile on GLSL ES.
u_xlat_precise_vec4 is not declared.
STR: create a new Until shader, add "precise" qualifier before "float4 vertex : SV_POSITION;".
Compile for GLES or GLES3.
Regressed on 2020.2, so no need to backport anything.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Text Object position shifts when selecting multiple Text Objects and expanding the Extra Settings in the Inspector
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
Add comment