I'm just wondering if anyone else has had this problem with Company of Heroes.
I'm also pretty sure this only applies to SLI, and drivers newer and including (by DATE) the 93.71 and greater.
**If you don't want to read the background to it all, just skip all this and go down to were it says Problems**
Now, I reinstalled windows not too long ago, and the newest driver there was, was the 93.71. So I installed it (the XTreme-G one), and everything ran nice and perfect (i gotta say, the 93.71 driver is pretty dam nice)
*****Versions make a difference???? (i don't know)*****
So today I installed Company of Heroes thinking everything will be all find and I've never had a problem with it before.
I think I should note that I'm using version 1.2 of the game. I'm well aware that there's a 1.3, but I like to cheat sometimes
so the trainer only works with 1.2 (1.3 coming out on Nov. 27 though).
Anyway, not sure if this only applies to v1.2, it could possibly be fixed in 1.3, but I didn't see anything in the release notes about it.
******Problems Begin Here********
This is were the problems begin.
(CoH, v1.2)
Now, the problem really isn't the 93.71. It's the nvapps.xml file that goes with it. I could copy the nvapps.xml from this driver, to an older one and get the same problem, so it's not the driver, it's the way it renders SLI.
The ground textures (like terrain, i.e. the ground basically) and only the ground would flash (like it was flashing with AFR) and some of the texture would be seriously corrupt (sry, no screen shot).
*****Want a fix??*****
Find your "nvapps.xml" file in your Windows/system32 folder and open it with Word Pad.
Search for the word "Company" and you should get the profile for Company of Heroes.
Change the system of numbers that are there to this:
0x02430001
It should just be 0x02400001, then change it to whats above.
Fixed it for me.
That fixed number is whats in driver versions 92.91 and before. I have no idea why nvidia would change it to something that doesn't work when the old way worked fine.
Also you can use nhancer to change the bits too. Just take away the 0 after the 4 and replace it with a 3.
Or check bits 16 and 17 in the D3D list.
And, am I the only one with this problem?????
BTW, it took me 2 hours to figure out that the problem was because of one fsck'n number.
And I'm POSITIVE it is the problem. It doesn't just apply to the 93.71 driver. It applies to the nvapps that goes with it. If I'd copy the nvapps file from the 93.71 to an older driver, the older driver would do it too.
I'm also pretty sure this only applies to SLI, and drivers newer and including (by DATE) the 93.71 and greater.
**If you don't want to read the background to it all, just skip all this and go down to were it says Problems**
Now, I reinstalled windows not too long ago, and the newest driver there was, was the 93.71. So I installed it (the XTreme-G one), and everything ran nice and perfect (i gotta say, the 93.71 driver is pretty dam nice)
*****Versions make a difference???? (i don't know)*****
So today I installed Company of Heroes thinking everything will be all find and I've never had a problem with it before.
I think I should note that I'm using version 1.2 of the game. I'm well aware that there's a 1.3, but I like to cheat sometimes
so the trainer only works with 1.2 (1.3 coming out on Nov. 27 though).Anyway, not sure if this only applies to v1.2, it could possibly be fixed in 1.3, but I didn't see anything in the release notes about it.
******Problems Begin Here********
This is were the problems begin.
(CoH, v1.2)
Now, the problem really isn't the 93.71. It's the nvapps.xml file that goes with it. I could copy the nvapps.xml from this driver, to an older one and get the same problem, so it's not the driver, it's the way it renders SLI.
The ground textures (like terrain, i.e. the ground basically) and only the ground would flash (like it was flashing with AFR) and some of the texture would be seriously corrupt (sry, no screen shot).
*****Want a fix??*****
Find your "nvapps.xml" file in your Windows/system32 folder and open it with Word Pad.
Search for the word "Company" and you should get the profile for Company of Heroes.
Change the system of numbers that are there to this:
0x02430001
It should just be 0x02400001, then change it to whats above.
Fixed it for me.
That fixed number is whats in driver versions 92.91 and before. I have no idea why nvidia would change it to something that doesn't work when the old way worked fine.
Also you can use nhancer to change the bits too. Just take away the 0 after the 4 and replace it with a 3.
Or check bits 16 and 17 in the D3D list.
And, am I the only one with this problem?????
BTW, it took me 2 hours to figure out that the problem was because of one fsck'n number.
And I'm POSITIVE it is the problem. It doesn't just apply to the 93.71 driver. It applies to the nvapps that goes with it. If I'd copy the nvapps file from the 93.71 to an older driver, the older driver would do it too.
Facebook
Twitter