Re: [PATCH 4/5] d3d/tests: Table fog does not abs the fog coordinate (v2).

[Henri Verbeet]

On 26 November 2014 at 19:08, Stefan Dösinger  wrote:
> - /* Needed to make AMD drivers happy. Yeah, it is not supposed to
> -
> * have an effect on RHW draws. */
> - static const D3DMATRIX identity =
> - {{{
> -
>    1.0f, 0.0f, 0.0f, 0.0f,
> -
>    0.0f, 1.0f, 0.0f, 0.0f,
> -
>    0.0f, 0.0f, 1.0f, 0.0f,
> -
>    0.0f, 0.0f, 0.0f, 1.0f
> - }}};

Is this the same projection matrix issue as in
fog_test()/fog_with_shader_tests()/etc.?

[PATCH 4/5] d3d/tests: Table fog does not abs the fog coordinate (v2).

[Stefan Dösinger]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 2014-11-27 10:27, schrieb Henri Verbeet:
> On 26 November 2014 at 19:08, Stefan Dösinger  wrote:
> > - /* Needed to make AMD drivers happy. Yeah, it is not supposed to
> > -
> > * have an effect on RHW draws. */
> > - static const D3DMATRIX identity =
> > - {{{
> > -
> >    1.0f, 0.0f, 0.0f, 0.0f,
> > -
> >    0.0f, 1.0f, 0.0f, 0.0f,
> > -
> >    0.0f, 0.0f, 1.0f, 0.0f,
> > -
> >    0.0f, 0.0f, 0.0f, 1.0f
> > - }}};
>
> Is this the same projection matrix issue as in
> fog_test()/fog_with_shader_tests()/etc.?

I can't look into the AMD drivers, so I don't know for sure, but I think this is different. fog_test, fog_interpolation_test want a redundant application of the projection matrix. In this case there's a SetTransform(D3DTS_PROJECTION) already, but the z = 0.0 part breaks AMD drivers in RHW draws.

Why are you asking? Do you have some idea what is causing this behavior?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJUdu/4AAoJEN0/YqbEcdMwYHwP+wfCV/wc3k/UC7rIEuiV3Yb2
Y8UZj790hTsnugODUsy4a/Dk9E/qgko24qBCbL4TLmvKvXz9FDukXxY6Ru2c86JT
Cb2zCMhzoOQ74i8nVhvR0faA4/gwGK3c1GUHEtCruEntUuSEGE3EvFk5l99MgltX
147v+J8qt8InXtH+9IzG1aG0G4i1BB61Uau0ZT3llbEhSkkpq0Rw1gH4UsXHb66j
RWUp8H0cPfRSzv8wBv44xS3dsthUF3V+PuC/tYVIzMghSOaEIPZFcKR0HsGz/2Y0
7QIdlRvzs+k5Lzv6HwGJf4XHFRTJPvexkb8VmIEtYuR6mIDObNqInbQUECw66wGE
Mczc7RihYCufbYl8JVT3mtKaG8fsTp64a6OLNrM3dsSW5CFLsevL6QfH/A+wFopk
eTPo12274ehhzC1DZlqPL6svX/J+PTHJT3FyIxZKsinMaOxqfY5QJhmGFXqMaSYT
RCDz/pSG0LeaXVbl2dR2ABotzWYGwBeLJYzar8fYu00Gv3wvRk9cd/AlbvkIAtl1
SAhmYzvwYWaX16uLRj04fW0M5TmTXW+VUDVjKzrM+0Q2UyblfIkDj/wvRJxROT2S
HC0dVTevof8hVY7MJ1o94L6wV+mAkMktNXwb0ddbrEdt76j1rBe8c43LAi31Ek7E
RdzxUPj8ItbG4GGeb2p1
=5+Vg
-----END PGP SIGNATURE-----

[PATCH 4/5] d3d/tests: Table fog does not abs the fog coordinate (v2).

[Henri Verbeet]

On 27 November 2014 at 10:33, Stefan Dösinger  wrote:
> I can't look into the AMD drivers, so I don't know for sure, but I think this is different. fog_test, fog_interpolation_test want a redundant application of the projection matrix. In this case there's a SetTransform(D3DTS_PROJECTION) already, but the z = 0.0 part breaks AMD drivers in RHW draws.
>
> Why are you asking? Do you have some idea what is causing this behavior?

Mostly just curiosity.