ddraw:d3d tests failing consistently

H. Verbeet hverbeet at gmail.com
Sat Oct 27 15:17:03 CDT 2007


On 27/10/2007, Francois Gouget <fgouget at free.fr> wrote:
> [...]
> > > I don't think the caps will really be useful here, but we could
> > > retrieve the card and driver name, and skip the test for some
> > > combinations. IDirect3D9::GetAdapterIdentifier() for example should
> > > return enough information for d3d9. I'm not sure we want to go there
> > > though, Alexandre has said before that the tests should simply fail on
> > > broken setups.
>
> Was he talking about broken Windows setups or broken Linux setups?
> It's find to ignore clearly broken Linux setups (e.g. known buggy driver
> version), but calling every Windows system that does not give the result
> we want 'broken' is refusing to face reality.
>
http://www.winehq.org/pipermail/wine-devel/2007-October/059719.html
Broken setups in general I'd say. Let me put this another way... those
setups would fail Microsofts own DCT as well.



More information about the wine-devel mailing list