gallium/hud: do not specify potentially invalid depth-range
Setting the depth-scale to 1 while leaving the depth-translation at 0 means our near-plane is at -1 in OpenGL semantics, which is out-of-range on some drivers. In particular, Zink has this limitation. But since we'll only pass a zero z in here anyway, we might as well multiply it by zero, and get the same result. This avoids the problem. Reviewed-by: Marek Olšák <marek.olsak@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5408>
This commit is contained in:
parent
978285f69a
commit
67ad75a282
|
@ -523,7 +523,7 @@ hud_draw_results(struct hud_context *hud, struct pipe_resource *tex)
|
|||
|
||||
viewport.scale[0] = 0.5f * hud->fb_width;
|
||||
viewport.scale[1] = 0.5f * hud->fb_height;
|
||||
viewport.scale[2] = 1.0f;
|
||||
viewport.scale[2] = 0.0f;
|
||||
viewport.translate[0] = 0.5f * hud->fb_width;
|
||||
viewport.translate[1] = 0.5f * hud->fb_height;
|
||||
viewport.translate[2] = 0.0f;
|
||||
|
|
Loading…
Reference in New Issue