Implementing dxdiag as student project?
thunderbird2k at gmx.net
Sun Dec 28 09:49:54 CST 2008
> On Sun, Dec 28, 2008 at 7:43 AM, Roderick Colenbrander
> <thunderbird2k at gmx.net> wrote:
> >> Also, isn't it annoying that native dxdiag always says
> >> the graphics card is X Windows? Why is that, and
> >> should we change Wine so that the true card's info
> >> is reported by native dxdiag?
> > Native dxdiag is checking the name of the display driver which in our
> case winex11.drv and I guess this is just the identifier of Winex11.drv.
> Inside winex11.drv we don't really have the knowledge about the 3d hardware we
> are emulating. In the end we might need to duplicate some card detection
> code inside winex11.drv and show a real driver name like the Nvidia or ATI
> ones. It would be a lot of work and only be worth if apps really need it.
> OK, alternately, where should Wine's dxdiag.exe get that info?
> - Dan
The best thing would be to get it from the same place as Windows is doing but as mentioned that might not be good right now. Direct3D has info on the card we are emulating (it has emulated pci ids) but right now we only report a generic renderer string. At the moment the best way is to get this info from opengl. (glGetString(GL_RENDERER)
Sensationsangebot verlängert: GMX FreeDSL - Telefonanschluss + DSL
für nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K1308T4569a
More information about the wine-devel