Status of dxdiagn?

[Markus]

On Thursday 01 January 2009 22:35:51 Dan Kegel wrote:
> On Thu, Jan 1, 2009 at 5:13 PM, Dan Kegel <dank at kegel.com> wrote:
> >> 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
> >
> > World In Conflict is affected by this, right?
> > http://bugs.winehq.org/show_bug.cgi?id=11114
>
> Looks like it (the demo, too).
Yes, World in Conflict is what I am trying to fix dxdiagn for. The 
szDeviceIdentifier property added by the above patch is a prerequisite to have 
the game continue checking for 3D capabilities of the system. If 
szDeviceIdentifier is not present, the check will already consider 3D not to 
be available.

> I got the demo to start by dropping in a native dxdiagn and disabling
> d3dx10 as described in the full game's howto at
> http://appdb.winehq.org/objectManager.php?sClass=version&iId=9237
> Sadly, I get no video other than the cursor, and I haven't
> the foggiest idea of how to quit the game, so I have to kill
> it from another terminal.
The game used to run very well with previous versions of Wine. I am seeing the 
black screen too with HEAD, so this is possibly an unrelated recent 
regression. As long as the game starts, you're ok in regard to dxdiagn.

> This is promising, though.  The student could have the goal
> of fixing dxdiagn so that wic's demo starts.
If my patch above is accepted, only the two b3D properties remain to be 
implemented and then WiC should start fine. I don't think that is big enough 
of a project.

-- 
Markus