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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment