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
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
On Thu, Jan 1, 2009 at 3:41 PM, Markus kde@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
On Thu, Jan 1, 2009 at 5:13 PM, Dan Kegel dank@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). 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.
This is promising, though. The student could have the goal of fixing dxdiagn so that wic's demo starts.
Is this problem addressed by your current patch?
Guess not, I tried it, no joy (not surprising, it only implements one of the ten or so properties the game queries). - Dan
On Thursday 01 January 2009 22:35:51 Dan Kegel wrote:
On Thu, Jan 1, 2009 at 5:13 PM, Dan Kegel dank@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.
On Fri, Jan 2, 2009 at 7:36 AM, Markus kde@graph-ix.net wrote:
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.
Got another game that needs dxdiagn fixes?
Or they could go ahead and do dxdiag on top of dxdiagn.
On Friday 02 January 2009 10:58:48 Dan Kegel wrote:
Got another game that needs dxdiagn fixes?
Personally, I don't know of any other games that need dxdiagn fixes but I guess you already identified potential candidates earlier.
Or they could go ahead and do dxdiag on top of dxdiagn.
That might be a good idea as it would simplify dxdiagn development by offering a GUI showing the retrieved values and those still missing.
-
Dan Kegel -
Markus