Vista/DX10 and hardware OOTB features

[Reverend]

Sorry but I haven't been too up-to-date with Vista and DX10 but from what I had read (which was quite sometime back) it appears that the forcing of things like AA and AF via drivers (using the current mode of display properties/control panel) seems to be, um, "outlawed" for anyone using Vista.

This is not true, right?

 

[lopri]

If that's true wouldn't it be attributed to the drivers' immaturity? (Or Vista's)

 

[Demirug]

The "defaul" drivers don’t have panels. If you install one of the newer beta drivers you should get your panel back.

 

[AlexV]

But is it possible to force settings through those panels?I don`t know about NV, but I seem to remember that the CCC hardly allowed it under Vista, but things may have changed since i toyed with it.

 

[Demirug]

But is it possible to force settings through those panels?I don`t know about NV, but I seem to remember that the CCC hardly allowed it under Vista, but things may have changed since i toyed with it.

The nVidia panel I used last allows such changes but it had some bugs too.

 

[DmitryKo]

The latest Vista drivers from NVIDIA do not have controls for DirectX antialiasing, this is mentioned under Limitations in this release, and What's New lists OpenGL ICD and Antialisasing for OpenGL. So I guess it's just driver immaturity...

 

[INKster]

The priority right now is the Desktop Composition Engine compatibility, only later comes performance.

 

[Rys]

Bear in mind that Reverend is talking about D3D10 hardware, not current D3D9 parts. Do any restrictions apply for future hardware, essentially.

 

[DmitryKo]

Bear in mind that Reverend is talking about D3D10 hardware, not current D3D9 parts.

http://www.microsoft.com/whdc/devtools/wdk/betawdk.mspx

 

[Reverend]

Bear in mind that Reverend is talking about D3D10 hardware, not current D3D9 parts. Do any restrictions apply for future hardware, essentially.

Actually, I was thinking of both parts.