Implementing b3DAccelerationExists and b3DAccelerationEnabled in dxdiagn

[Markus]

Hello,

can anyone tell me where to find information about the b3DAccelerationExists 
and b3DAccelerationEnabled properties in the display container returned by 
dxdiagn.dll and when they are supposed to be false or true?
In fact, MSDN does not seem to provide information about any of the properties 
returned by that dll.

Thanks,

Implementing b3DAccelerationExists and b3DAccelerationEnabled in dxdiagn

[Detlef Riekenberg]

On Mo, 2009-01-05 at 22:10 -0500, Markus wrote:
> can anyone tell me where to find information about the b3DAccelerationExists 
> and b3DAccelerationEnabled properties in the display container returned by

I suggest to use dxdiag and regmon on Windows.
In dxdiag, you can disable DirectDraw / Direct3D Acceleration.
Regmon will tell you, where the settings are saved.

[Markus]

On Tuesday 06 January 2009 03:58:27 Detlef Riekenberg wrote:
> On Mo, 2009-01-05 at 22:10 -0500, Markus wrote:
> > can anyone tell me where to find information about the
> > b3DAccelerationExists and b3DAccelerationEnabled properties in the
> > display container returned by
>
> I suggest to use dxdiag and regmon on Windows.
> In dxdiag, you can disable DirectDraw / Direct3D Acceleration.
> Regmon will tell you, where the settings are saved.

I do not think the registry is the correct place to look. This value should 
return true if e.g. hardware accelerated T&L is available on the system, which 
is primarily a result of driver and hardware capabilities.
My current understanding is that a D3D caps struct would hold such 
information. The question now is which flag or combination of flags in it 
would cause the dxdiagn values to be 'true'?

Implementing b3DAccelerationExists and b3DAccelerationEnabled in dxdiagn

[Detlef Riekenberg]

On Di, 2009-01-06 at 22:47 -0500, Markus wrote:
> > > can anyone tell me where to find information about the
> > > b3DAccelerationExists and b3DAccelerationEnabled properties in the
> > > display container returned by
> >
> > I suggest to use dxdiag and regmon on Windows.
> > In dxdiag, you can disable DirectDraw / Direct3D Acceleration.
> > Regmon will tell you, where the settings are saved.
>
> I do not think the registry is the correct place to look.

For sure, the settings for enable/disable Acceleration must be in the
registry.
This is for b3DAccelerationEnabled and the primary requirement for that
flag
is a TRUE in b3DAccelerationExists
> This value should 
> return true if e.g. hardware accelerated T&L is available on the system, which 
> is primarily a result of driver and hardware capabilities.

This is for b3DAccelerationExists and native dxdiagn in Wine with some
d3d* debug channels might help a bit.

I have an ATI Radeon 7500 Mobility (R100) here for testing.
W98 with DDraw/D3D support (old driver)
W2K without DDraw/D3D support
 (i use a new driver, that droped DirectX support for R100)

Using regedit on W98:
HKLM\Software\Microsoft\Direct3D\Drivers
 SoftwareOnly  DWORD 1
HKLM\Software\Microsoft\DirectDraw
 EmulationOnly DWORD 1

When DDraw is set to EmulationOnly, D3D is marked (in dxdiag) as
"not available" (d3d needs ddraw on Windows), independent of
SoftwareOnly.
(Using the GUI to set EmulationOnly to 1 also sets SoftwareOnly to 1)

[Markus]

On Wednesday 07 January 2009 06:55:12 Detlef Riekenberg wrote:
> > This value should
> > return true if e.g. hardware accelerated T&L is available on the system,
> > which is primarily a result of driver and hardware capabilities.
>
> This is for b3DAccelerationExists and native dxdiagn in Wine with some
> d3d* debug channels might help a bit.

What I have found so far is that the native dxdiagn.dll retrieves the device 
capabilities using IDirect3D9Impl_GetDeviceCaps. However, I was unable to find 
any values for the caps struct, where the native dll would determine that 
b3DAccelerationExists was supposed to be false. The only result I got in that 
regard was that by setting caps->DevCaps to 0, a human readable warning about 
missing D3d9+ hardware acceleration would be added to szNotesLocalized.

Does anyone have an idea on what else could be the basis for this flag?

[Alexandre Julliard]

Markus  writes:
> What I have found so far is that the native dxdiagn.dll retrieves the device 
> capabilities using IDirect3D9Impl_GetDeviceCaps. However, I was unable to find 
> any values for the caps struct, where the native dll would determine that 
> b3DAccelerationExists was supposed to be false.

You are not allowed to look at what calls the native dll makes, that's
an implementation detail. The only thing you can do with native is to
write test cases to determine the externally visible behavior.