Status of dxdiagn?

[Markus]

Hi Dan,

I have not worked on dxdiagn for a few months due to a lack of time. As far as 
missing functionality is concerned, I have only investigated properties 
related to the display container. I suspect that many games are trying to read 
the b3DAccelerationExists and/or b3DAccelerationEnabled properties in it to 
determine if 3D acceleration is available. However, compared to dx9, there are 
more than 45 other properties missing for this container alone, so there is 
still a lot of work left to be done.

In order to reach support for the two acceleration properties, I have just 
submitted an updated patch based on my code from mid-2008:
http://www.winehq.org/pipermail/wine-patches/2009-January/066929.html

I will try to re-submit the test case in the next days depending on my time.

Regarding an implementation of dxdiag.exe, it might be a good idea to first 
add all the missing properties to the dll, at least as stubs. Without them, 
there doesn't seem to be that much to retrieve and display with dxdiag.exe

Markus

On Sunday 28 December 2008 00:28:56 Dan Kegel wrote:
> Hi Markus,
> what's the status of dxdiagn these days?  I see a number
> of games that say they need a native copy:
> http://www.google.com/search?q=dxdiagn+site%3Aappdb.winehq.org
> Do you know what needs doing before we can get
> native dxdiag working,
> http://bugs.winehq.org/show_bug.cgi?id=1429 ?
>
> Also, how about your dxdiagn conformance test?
> http://www.winehq.org/pipermail/wine-patches/2008-May/055355.html
> I know it didn't do much, maybe you could have it check a
> few required properties?
>
> I ask because I'm looking around for a student project,
> and implementing dxdiag.exe came to mind; looking
> around a bit, I saw dxdiagn, and figured it might be nice
> to tie up some loose ends there, too.
> - Dan

-- 
Markus