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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Add comment