Posted: Sat Dec 01, 2007 3:18 pm
mmh,
I think the problem is not directx per se, because many (if not all) opengl-games need directx too and they all work very well. directx is a "wrapper" for graphics (d3d, opengl, glide), sound, netplay, input-devices and so on.
let me summarize/conclude:
- the problem is not related to any specific chipset, but these chipsets have in common an agp-interface version 1.0
- it is not related with a specific version of agp-driver
- the problem is not related to any specific version of directx installed, it shows up with dx7, dx8(a), dx81, dx9c
- the problem showed up only so far with games that need dx7 or up AND don't use opengl but d3d; found exception to that rule: crimson skies (dx5, d3d): runs a minute then freezes
- tests so far have shown that games in 2d don't show this behaviour
- cards effected: any geforce when driver 6x.xx up is used
so I would say nvidia changed something in their d3d-code with drivers 6x.xx up which, when applied on an agp 1.0 board is responsible for that mess.
my believe that this problem is related with agp 1.0 boards is fostered by someone who had quite similar problems on an asus cubx-l board with intel bx-chipset (agp 1.0). (actually this guy and his success-story made me buy a gf6600gt for the asus p5a). he has a very long thread discussing his problems and at the end found a solution. unfortunately for you non-german speakers here his thread is in german, but I can tell you that he solved the problem as follows (I hope I translate correctly):
system win xp
goto device manager / system devices / cpu-to-agp bridge: this driver is to be exchanged manually, one should use the driver for "pci standard-pci-to-pci bridge".
thats it. I was not in the position to do this with the xp-installation on my p5a because there was no such thing as a cpu-to-agp bridge .....
for those who want to read the original german thread, go here
I think the problem is not directx per se, because many (if not all) opengl-games need directx too and they all work very well. directx is a "wrapper" for graphics (d3d, opengl, glide), sound, netplay, input-devices and so on.
let me summarize/conclude:
- the problem is not related to any specific chipset, but these chipsets have in common an agp-interface version 1.0
- it is not related with a specific version of agp-driver
- the problem is not related to any specific version of directx installed, it shows up with dx7, dx8(a), dx81, dx9c
- the problem showed up only so far with games that need dx7 or up AND don't use opengl but d3d; found exception to that rule: crimson skies (dx5, d3d): runs a minute then freezes
- tests so far have shown that games in 2d don't show this behaviour
- cards effected: any geforce when driver 6x.xx up is used
so I would say nvidia changed something in their d3d-code with drivers 6x.xx up which, when applied on an agp 1.0 board is responsible for that mess.
my believe that this problem is related with agp 1.0 boards is fostered by someone who had quite similar problems on an asus cubx-l board with intel bx-chipset (agp 1.0). (actually this guy and his success-story made me buy a gf6600gt for the asus p5a). he has a very long thread discussing his problems and at the end found a solution. unfortunately for you non-german speakers here his thread is in german, but I can tell you that he solved the problem as follows (I hope I translate correctly):
system win xp
goto device manager / system devices / cpu-to-agp bridge: this driver is to be exchanged manually, one should use the driver for "pci standard-pci-to-pci bridge".
thats it. I was not in the position to do this with the xp-installation on my p5a because there was no such thing as a cpu-to-agp bridge .....
for those who want to read the original german thread, go here