wine users - Oct 2010 - d3dx9_36 : How to handle bug reporting

Howdy folks,

The implementation of DirectX 9 in Wine has gone much forward, to the point
where most of the lacking functions in the helper dlls are in a single dll :
d3dx9_36. It is becoming much less necessary to run winetricks d3dx9.

At the moment I am in the process of testing all the game apps I have (around
100) without any overrides. I am looking in particular at d3dx9_36 and msvcrt.
At least 50 of them are DX9 or better apps. My procedure is to copy the game
contents to my HDD, delete any override install program that could be included
with the game (vcredist, directx, etc..), and installing only the required
software which has not been implemented yet or ever will (eg. PhysX, GFW).

My tests results so far with d3dx9_36 have been varied. Sometimes I get an easy
log with a missing function (eg. http://bugs.winehq.org/show_bug.cgi?id=24530),
but most of the time I get a humongous log with a load of stubbed functions
which is most likely unpractical for devs. There is also an extensive list of
bugs related to this particular dll :
http://bugs.winehq.org/buglist.cgi?quicksearch=d3dx9_36

I was wondering if a dev or an experienced user could recommend me a method for
bug reporting about this dll which is practical for devs, in particular when I
test apps which yield a humongous log. I technically can fill a bunch of reports
like this one : http://bugs.winehq.org/show_bug.cgi?id=24884 , but I don't
feel that it's very practical because there is little information available.

Cheers!

Forgot to add.. The method of removing the overrides install programs does not
always work because some games setup program will not install the game if they
don't find the overrides setup program. I was wondering if someone knows a
way to work around this, maybe a switch in the console or something?

austin987 wrote:
> The mscodescan.pl script from winezeug can help here.

Yes, Dan is giving me a tutorial right now.