Weird Direct3D problem 6600GT
This is a discussion about Weird Direct3D problem 6600GT in the Windows Hardware category; Anyone else have/had this problem? (6600GT, MB 939SATA2) I started playing GTA:SA and all the peoples (except polices) were grey (models were ok, but there were no textures attached or not shown). I quitted the program and run dxdiag.
Anyone else have/had this problem? (6600GT, MB 939SATA2)
I started playing GTA:SA and all the peoples (except polices) were grey (models were ok, but there were no textures attached or not shown).
I quitted the program and run dxdiag. D3D test showed that first test (DX7) were ok, cube and textures were shown. Problems started at next test (DX8), cube was ok but textures were messed up, same problem was at last test (DX9).
So, for some reason textures are not attached correctly. I changed card for 9800Pro which worked ok, no texture problems.
This morning I brought 6600GT to work, installed it to other computer and it worked ok.
I already have tried different drivers (77.77, 78.01, 81.98 and beta 83.90), reinstalled DirectX 9.0c(built feb 06), upgraded/downgraded MB BIOS and tried other MB drivers, still no luck. I also tried different memory combinations (dual channel, no dual, only 1 memory).
Any ideas?
I started playing GTA:SA and all the peoples (except polices) were grey (models were ok, but there were no textures attached or not shown).
I quitted the program and run dxdiag. D3D test showed that first test (DX7) were ok, cube and textures were shown. Problems started at next test (DX8), cube was ok but textures were messed up, same problem was at last test (DX9).
So, for some reason textures are not attached correctly. I changed card for 9800Pro which worked ok, no texture problems.
This morning I brought 6600GT to work, installed it to other computer and it worked ok.
I already have tried different drivers (77.77, 78.01, 81.98 and beta 83.90), reinstalled DirectX 9.0c(built feb 06), upgraded/downgraded MB BIOS and tried other MB drivers, still no luck. I also tried different memory combinations (dual channel, no dual, only 1 memory).
Any ideas?
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Feb 20
Feb 21
0
3 minutes
Responses to this topic
Have you tried uninstalling, rebooting and re-installing the game yet ?!?
Also, if this fails then I would grab an old HD that you can use for testing and remove your original HD then install this test drive into your box and reformat and install a fresh os copy with all the latest drivers and such.
Then install and test this game out and see what happens.
Could just be something has gotten corrupted on your original OS
Also, if this fails then I would grab an old HD that you can use for testing and remove your original HD then install this test drive into your box and reformat and install a fresh os copy with all the latest drivers and such.
Then install and test this game out and see what happens.
Could just be something has gotten corrupted on your original OS
OP
Aww, this sucks... no really, THIS SUCKS!
So far:
reinstalled GTA:SA, no luck.
After few frustrating hours the problem is clear, nVidia 81.98 causes this problem. Worst of all, I can't revert back to 78.01 because then the d3d is f*cked up! ARGH!
So in short:
drivers before fw 8x.xx series doesn't get textures to work ok.
drivers fw 8x.xx+ cause graphics to be terrible slow
So far:
reinstalled GTA:SA, no luck.
After few frustrating hours the problem is clear, nVidia 81.98 causes this problem. Worst of all, I can't revert back to 78.01 because then the d3d is f*cked up! ARGH!
So in short:
drivers before fw 8x.xx series doesn't get textures to work ok.
drivers fw 8x.xx+ cause graphics to be terrible slow
You might want to try some of the tweaked drivers based upon nVidia but which have been "hacked" particularly for games. One group that seems to get praise in some quarters is Extreme G found here: http://www.tweaksrus.com/
OP
Allright, finally good news.
Problem solved. Problem was with MB:s chipset drivers.
Didn't mention earlier that while doing BIOS update I also updatet few chipset drivers. So the solution was to go back to Forceware 77.77 and also to install Uli 2.13 chipset drivers.
Gotta try tonight those 81.98 drivers if they do any good but this time make a system restore point "just in case"
So conclusion for this, "If it's not broken, don't try to fix it"
Problem solved. Problem was with MB:s chipset drivers.
Didn't mention earlier that while doing BIOS update I also updatet few chipset drivers. So the solution was to go back to Forceware 77.77 and also to install Uli 2.13 chipset drivers.
Gotta try tonight those 81.98 drivers if they do any good but this time make a system restore point "just in case"
So conclusion for this, "If it's not broken, don't try to fix it"
The moral of the story is - always convey the number of things you've done to the computer and not just describe the symptoms.
