http://bugs.winehq.org/show_bug.cgi?id=21515
--- Comment #116 from P.Panon ppanon@shaw.ca 2010-03-05 05:24:09 --- RE: debugging drivers vs. Wine.
I've been wondering that a bit myself. It looks like if you're wanting to debug direct3d, you've got all the following trace categories available.
d3d, d3d8, d3d9, d3d10, d3d10core, d3d_caps, d3d_constants, d3d_decl, d3d_draw, d3drm, d3d_shader, d3d_surface, d3d_texture, d3dx, d3dxof, d3dxof_parsing, fps, gl_compat
If you're debugging, you would probably only want to turn on the ones you think are useful or else you're going to get huge logs and not be able to find anything in the flood of results. So If you think the problem is likely to be shader related then you could select d3d_shader. Trace d3d_texture if you think the problem is with texture manipulation, A modern app is unlikely to user D3D retained Mode, and d3d_cap(abilitie)s appears to mainly important for directx initialization (detecting what D3D functions can be supported, etc.)