Implementing dxdiag as student project?

Chris Robinson chris.kcat at
Sun Dec 28 05:21:19 CST 2008

On Sunday 28 December 2008 03:02:34 am Roderick Colenbrander wrote:
> On Windows the main task of dxdiag is to show some diagnostic info and to
> run some very basic network, sound and 3d tests. In case of Wine 3D testing
> would be the most important feature but I'm not sure if it is that useful.
> There are various causes of slowness e.g. no 3d drivers installed, indirect
> rendering, driver bugs (e.g. fglrx falling back to indirect rendering due
> to virtual memory issues in Wine), the use of a composition manager and
> more. Most of this information can't be retrieved using Win32 APIs or we
> would need internal APIs.

I think such a thing could still be useful. It'll help figure out what kind of 
info apps are getting from a given system, and help determine if problems are 
app-specific or more general system/wine-related. It can also serve as a 
basic interactive test bed for various DX functionality that even users can 
run and look at, instead of being delegated to the wine test suite only. Plus 
it can check DirectPlay and DirectSound (a couple other components prone to 
errors), instead of just Direct3D/DirectDraw.

More information about the wine-devel mailing list