Status of dxdiagn?

[Dan Kegel]

On Thu, Jan 1, 2009 at 3:41 PM, Markus <kde at graph-ix.net> wrote:
> ... 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

Thanks for the info and for refreshing your patches!

Are there any games that currently need native dxdiagn that we might fix?
I had a look, and only found two that seemed to need native dxdiagn:

World In Conflict is affected by this, right?
http://bugs.winehq.org/show_bug.cgi?id=11114
Is this problem addressed by your current patch?

I see Final Fantasy XI wants native dxdiagn; there's even a web
site *just for that one game on Wine* that mentions this!
http://www.wineffxi.org
- Dan