• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Nvidia Users Only

I have had several years of experience with Nvidia graphics cards and their drivers. I have found that newer drivers on older cards, even though the older card is "supported", tend to make the card run slower or induces instability. I've experienced this with a 6800 Ultra, a 7950GT, now a 8800GT. I hear the 182.50 is the best of the 18x or later drivers, but I stopped at 181.20 and have considered reverting to the 178.24 or even going back to... the 175 drivers.
 
All I see on Nvidia's site is 191 series drivers - regardless of GPU model...*Shrugs*
 
Hmmmm


maybe they are now back and experienced a glitch on their site...

very odd indeed
 
Anyways, thanks for the sort-of-HU though, Harleyman. I'm gonna try out the new 191.56s. They're actually for Quadros but said to work very well on regular cards.
 
By the way, is anyone aware of a 182.50 version for Win7 64bit? I also liked that driver the most under XP but I cannot find a proper version for Win7 of it. Only Vista ones so far.
 
I just installed the 191's in my puker. I had the 186's which were pretty good too. See my post in the Cub thread.
 
Meh, the 191.56 doesn't work out much for me. Kind of low 3D Mark 06 score and problems with ALT+Enter in FSX.

Trying the official 191.07s now.
 
For me the 191's have been an unmitigated disaster and I have a factory overclocked GTX 260. The main reason is that Anti Aliasing refuses to enable and Nhancer seems to have lost the ability to enforce AA within FSX.

I have tried 191.03, 191.07 and earlier 190 versions. I have read and reread the Nhancer forums and it seems I am not alone. Although FSX specific users appear slim on the ground in the forum, it is obvious they are encountering the same issues. Martin Korndorfer has released 2 or 3 versions of nhancer lately the latest being 2.5.7 and even with that I cannot get AA to work reliably in FSX. (and believe me I have reinstalled and installed, deleted NVAPPs etc etc as per instructions on each occasion)

The issue for me (and here I am happy to receive educated alternative advice), is that it is my understanding Nhancer enables the direct AA usage from the card, whereas forcing AA on inside the application, chews into the available CPU power?). Indeed, in the past I have enabled AA only through Nhancer and it has worked a charm, forcing AA on to a higher degree and giving a better result, with good FPS.

After a lot of frustration with the latest drivers, (191 etc) I have decided to revert back to 186.18 for the time being. All is well there. I await any intelligent debate on this matter for resolution from Nvidia, but know full well that is unlikely to be taken seriously, after all FSX is 3 years old now.

Spike
 
dexthom said:
Running the 191.07 on Win 7 64 bit just fine...
Click to expand...

You lucky dog. ;)
That's what they give me:




Spikehughes said:
I have tried 191.03, 191.07 and earlier 190 versions. I have read and reread the Nhancer forums and it seems I am not alone. Although FSX specific users appear slim on the ground in the forum, it is obvious they are encountering the same issues. Martin Korndorfer has released 2 or 3 versions of nhancer lately the latest being 2.5.7 and even with that I cannot get AA to work reliably in FSX. (and believe me I have reinstalled and installed, deleted NVAPPs etc etc as per instructions on each occasion)

The issue for me (and here I am happy to receive educated alternative advice), is that it is my understanding Nhancer enables the direct AA usage from the card, whereas forcing AA on inside the application, chews into the available CPU power?). Indeed, in the past I have enabled AA only through Nhancer and it has worked a charm, forcing AA on to a higher degree and giving a better result, with good FPS.

After a lot of frustration with the latest drivers, (191 etc) I have decided to revert back to 186.18 for the time being. All is well there. I await any intelligent debate on this matter for resolution from Nvidia, but know full well that is unlikely to be taken seriously, after all FSX is 3 years old now.
Click to expand...

Well, the 190.62s worked perfectly for me (AA et al) until I've decided to upgrade them yesterday. Ever since then, nothing but trouble.

Still need to figure out a procedure for a good, clean driver installation in Windows 7.
 
*Bump*

Fixed my problem (reverted back to the 186.18s) and I think I also have a good driver installation procedure for Windows 7 now:

1. Uninstall your video card via Device Manager, also select "Delete Driver".
2. Reboot, let 7 install the generic WDDM driver. Don't reboot after that just yet, but instead run a cleaning tool like Driver Sweeper first, then reboot.
3. Install the new drivers, reboot and done.

Worked for me, would be cool if someone else could test that.
 
Bjoern said:
All I see on Nvidia's site is 191 series drivers - regardless of GPU model...*Shrugs*
Click to expand...

Google search the driver number ya want. Example..(NVidia 182.50 Vista) in Google. Don't do like me and for get to add in the search your Operating system as well. I did that last night when I looked for and found the 182.50 driver. My DL speed is just this side of a snail race. Took bout 2 hours for 77mb. Then I find out it's for XP...I have Vista. I am such a knucklehead.
Will download the Vista version later.
 
Tried the whole procedure again. Works extremely well.

I don't know how FSX does with the 191.56s yet.
 
Spikehughes said:
For me the 191's have been an unmitigated disaster and I have a factory overclocked GTX 260. The main reason is that Anti Aliasing refuses to enable and Nhancer seems to have lost the ability to enforce AA within FSX.

I have tried 191.03, 191.07 and earlier 190 versions. I have read and reread the Nhancer forums and it seems I am not alone. Although FSX specific users appear slim on the ground in the forum, it is obvious they are encountering the same issues. Martin Korndorfer has released 2 or 3 versions of nhancer lately the latest being 2.5.7 and even with that I cannot get AA to work reliably in FSX. (and believe me I have reinstalled and installed, deleted NVAPPs etc etc as per instructions on each occasion)

The issue for me (and here I am happy to receive educated alternative advice), is that it is my understanding Nhancer enables the direct AA usage from the card, whereas forcing AA on inside the application, chews into the available CPU power?). Indeed, in the past I have enabled AA only through Nhancer and it has worked a charm, forcing AA on to a higher degree and giving a better result, with good FPS.

After a lot of frustration with the latest drivers, (191 etc) I have decided to revert back to 186.18 for the time being. All is well there. I await any intelligent debate on this matter for resolution from Nvidia, but know full well that is unlikely to be taken seriously, after all FSX is 3 years old now.

Spike
Click to expand...

I've run into this problem in the last couple of days while setting up Win7 and I think I've found what's wrong.
I've found that when forcing the AA in NHancer with the new drivers only Multisampling works, Supersampling and Combined seem to be broken.

If you set any Supersampling or Combined AA settings in NHancer then open the Nvidia control panel they show up as Custom under Antialiasing-Setting and don't work in game,

Its not just FSX that's affected, it seems to be in all games.
So far I've tried it in FSX, GTR2 and GPL with the same results.

I don't know if its the drivers or NHancer that's at fault so I'm going to post about it on the Nhancer forum and see what happens.

EDIT: Just found this at the NHancer forum and it worked http://forum.nhancer.com/announcement.php?f=5
 
You must log in or register to reply here.
Back
Top