Questioning the depth_clamp_test in d3d8:visual
stefandoesinger at gmx.at
Mon Jan 24 06:14:42 CST 2011
-----BEGIN PGP SIGNED MESSAGE-----
Am 24.01.2011 um 13:02 schrieb <Joerg-Cyril.Hoehle at t-systems.com> <Joerg-Cyril.Hoehle at t-systems.com>:
> - Wylda's Intel-based machine #2 passes the tests. Hurray!
> - One unknown win7 machine with Intel gfx also passes them.
> - Aurimas' machine produces one different error (also Intel gfx).
Afaik the test passes on Windows everything but Nvidia(well, it passes on Intel according to your observations, and I know it passes on my ATI box). I tried to understand the Nvidia failure, as far as I know the depth clamp state just doesn't do anything on this card. A game that depends on the behavior tested by the test is Prince of Persia 3D, a ddraw/d3d7 game. I could not test this game on my Windows 7 machine(s), it failed to install.
Any decent explanation why the test fails on Nvidia on Windows, or clear proof that the driver is broken(e.g. POP3D doesn't render properly) would be very welcome.
> Looking at Wine test data (from 1.3.12), it appears that Wine
> implements exactly the opposite behaviour: the NVidia (+ 1 ATI) machines
> pass the tests, e.g. behave like Intel on native, while the Intel gfx one
> (eeepc) produces the 3 errors known from native NVidia!
We don't have card-specific behavior in wined3d. wined3d implements the behavior according to what the test says is correct. I suspect the Intel driver used to run the failing Linux test does not implement GL_NV_depth_clamp or GL_ARB_depth_clamp, or implements it incorrectly.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
-----END PGP SIGNATURE-----
More information about the wine-devel