Attachment 30043 Details for Bug 20340 – fix fuzzy texture for r200

[patch] fix fuzzy texture for r200

r200blur.patch (text/plain), 1.48 KB, created by Frederic Crozat on 2009-10-04 14:16:36 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Frederic Crozat

Created: 2009-10-04 14:16:36 UTC

Size: 1.48 KB

patch

obsolete

>--- Mesa-7.3/src/mesa/drivers/dri/r200/r200_state.c.r200blur	2009-10-04 22:45:19.000000000 +0200
>+++ Mesa-7.3/src/mesa/drivers/dri/r200/r200_state.c	2009-10-04 22:46:39.000000000 +0200
>@@ -1686,13 +1686,6 @@ static void r200ClearStencil( GLcontext 
>  * Window position and viewport transformation
>  */
> 
>-/*
>- * To correctly position primitives:
>- */
>-#define SUBPIXEL_X 0.125
>-#define SUBPIXEL_Y 0.125
>-
>-
> /**
>  * Called when window size or position changes or viewport or depth range
>  * state is changed.  We update the hardware viewport state here.
>@@ -1706,9 +1699,9 @@ void r200UpdateWindow( GLcontext *ctx )
>    const GLfloat *v = ctx->Viewport._WindowMap.m;
> 
>    float_ui32_type sx = { v[MAT_SX] };
>-   float_ui32_type tx = { v[MAT_TX] + xoffset + SUBPIXEL_X };
>+   float_ui32_type tx = { v[MAT_TX] + xoffset };
>    float_ui32_type sy = { - v[MAT_SY] };
>-   float_ui32_type ty = { (- v[MAT_TY]) + yoffset + SUBPIXEL_Y };
>+   float_ui32_type ty = { (- v[MAT_TY]) + yoffset };
>    float_ui32_type sz = { v[MAT_SZ] * rmesa->state.depth.scale };
>    float_ui32_type tz = { v[MAT_TZ] * rmesa->state.depth.scale };
> 
>@@ -1752,8 +1745,8 @@ void r200UpdateViewportOffset( GLcontext
>    float_ui32_type tx;
>    float_ui32_type ty;
> 
>-   tx.f = v[MAT_TX] + xoffset + SUBPIXEL_X;
>-   ty.f = (- v[MAT_TY]) + yoffset + SUBPIXEL_Y;
>+   tx.f = v[MAT_TX] + xoffset;
>+   ty.f = (- v[MAT_TY]) + yoffset;
> 
>    if ( rmesa->hw.vpt.cmd[VPT_SE_VPORT_XOFFSET] != tx.ui32 ||
> 	rmesa->hw.vpt.cmd[VPT_SE_VPORT_YOFFSET] != ty.ui32 )

Actions: View | Splinter Review

Attachments on bug 20340: 23344 | 23345 | 25653 | 25655 | 30043

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.