A 163.71 driver issue

Mr.E Solved! wrote:
> Dudley Henriques wrote:
>> Downloaded the new 163.71 driver from Nvidia last night and replaced
>> 158.22 on my XP/SP2 system using a BFG8800GTS/640 following my usual
>> procedure (remove driver in add remove, then reboot and run driver
>> cleaner for Nvidia, then reboot and install new driver in safe mode.
>> Noticed immediately that in the Nvidia driver settings I had no AA
>> setting showing. The AF was there but not the AA.
>> I un-installed then reinstalled the driver with the same result.
>> Finally I un-installed the 163.71 and reinstalled the 158.22 and the
>> AA was back showing on the Nvidia list.
>> I should add that the 163.71 driver seemed to be functioning normally
>> in FS2004 which is the only program I use this computer for. No
>> jaggies or issues; just the AA missing from the driver settings.
>> Is this a known issue with this driver?
>
> Dudley, you dear old sock, this problem has been in FS9 since day 1. FS9
> 's FSAA is so broken as to be comical. As you may know, you must use
> whatever AA mode FS9 provides and forcing FSAA from the Forceware driver
> is very bad. You can only "enhance" existing FSAA modes of FS9 with
> Forceware drivers.
>
> That it disappears from the choices in 163.71 is just acknowledgment of
> the problem as it has always existed.
>
> To workaround this, you can use nHancer, which auto-magically modifies
> the xml file the forceware drivers use to make specific adjustments to
> specific games and their specific needs. Such as FS9 and FSAA, give it a
> try.
>
> http://www.nhancer.com
>
> However, be warned, the 163.71's (WHQL) do have an XML parsing error in
> one of the profiles (I have yet to find which one) and might confuse
> nhancer if you try and load the yucky profile.
>
> I had to manually prune the xml file to get it to load, I merely left in
> only those apps I needed. (FS9 being one, so I know it works).
>
> good luck!

Thanks for the reply. I've had Nvidia cards and been using their
reference drivers for many years now with no issues concerning AA. It
has always appeared on the Nvidia settings selection list with AF until
this newest driver release.
In FS9, you are correct that AA has always worked better when assigned
in the driver settings rather than the sim itself as application
controlled...at least it has for me anyway
I've just been checking around a bit and found a post from another user
that AA isn't showing on his list either.
Don't know what is causing this but Nvidia has nothing on it in the
release notes for the driver.
I reinstalled 158.22 and got the AA setting back immediately on the
driver settings in the Nvidia control panel.
Interesting if nothing else )
DH

--
Dudley Henriques
 >> Stay informed about: A 163.71 driver issue 

On Mon, 01 Oct 2007 14:33:43 -0400, Dudley Henriques
wrote:

> Downloaded the new 163.71 driver from Nvidia last night and replaced
> 158.22 on my XP/SP2 system using a BFG8800GTS/640 following my usual
> procedure (remove driver in add remove, then reboot and run driver
> cleaner for Nvidia, then reboot and install new driver in safe mode.
> Noticed immediately that in the Nvidia driver settings I had no AA
> setting showing. The AF was there but not the AA.
> I un-installed then reinstalled the driver with the same result.
> Finally I un-installed the 163.71 and reinstalled the 158.22 and the AA
> was back showing on the Nvidia list.
> I should add that the 163.71 driver seemed to be functioning normally in
> FS2004 which is the only program I use this computer for. No jaggies or
> issues; just the AA missing from the driver settings.
> Is this a known issue with this driver?

Translation please, "AF" & "AA" ?



--
==== Tecknomage ====
All technology which is sufficiently advanced becomes
indistinguishable from magic.
 >> Stay informed about: A 163.71 driver issue 

"Tecknomage" wrote in message

> Translation please, "AF" & "AA" ?
> --
> ==== Tecknomage ====
> All technology which is sufficiently advanced becomes
> indistinguishable from magic.

You must only be an apprentice mage.

Anisotropic Filtering and Anti-Aliasing, respectively.

RF.
 >> Stay informed about: A 163.71 driver issue 

Workaround:
Start fs9, then set the AA setting in the forcedriver to none. Close fs9 and
restart. Set AA in the driver to the setting you want. AA wil be back. It
worked for me.
Peter


"Dudley Henriques" schreef in bericht

> Downloaded the new 163.71 driver from Nvidia last night and replaced
> 158.22 on my XP/SP2 system using a BFG8800GTS/640 following my usual
> procedure (remove driver in add remove, then reboot and run driver cleaner
> for Nvidia, then reboot and install new driver in safe mode.
> Noticed immediately that in the Nvidia driver settings I had no AA setting
> showing. The AF was there but not the AA.
> I un-installed then reinstalled the driver with the same result.
> Finally I un-installed the 163.71 and reinstalled the 158.22 and the AA
> was back showing on the Nvidia list.
> I should add that the 163.71 driver seemed to be functioning normally in
> FS2004 which is the only program I use this computer for. No jaggies or
> issues; just the AA missing from the driver settings.
> Is this a known issue with this driver?
> --
> Dudley Henriques
 >> Stay informed about: A 163.71 driver issue 

Peter wrote:
> Workaround:
> Start fs9, then set the AA setting in the forcedriver to none. Close fs9 and
> restart. Set AA in the driver to the setting you want. AA wil be back. It
> worked for me.
> Peter
>
>
> "Dudley Henriques" schreef in bericht
>
>> Downloaded the new 163.71 driver from Nvidia last night and replaced
>> 158.22 on my XP/SP2 system using a BFG8800GTS/640 following my usual
>> procedure (remove driver in add remove, then reboot and run driver cleaner
>> for Nvidia, then reboot and install new driver in safe mode.
>> Noticed immediately that in the Nvidia driver settings I had no AA setting
>> showing. The AF was there but not the AA.
>> I un-installed then reinstalled the driver with the same result.
>> Finally I un-installed the 163.71 and reinstalled the 158.22 and the AA
>> was back showing on the Nvidia list.
>> I should add that the 163.71 driver seemed to be functioning normally in
>> FS2004 which is the only program I use this computer for. No jaggies or
>> issues; just the AA missing from the driver settings.
>> Is this a known issue with this driver?
>> --
>> Dudley Henriques
>
>

Thanks for the reply. Fixed it last night. AA can be accessed by right
clicking the desktop instead of using the taskbar icon. Have no idea
what the heck they did it this way but it works that way.
DH

--
Dudley Henriques
 >> Stay informed about: A 163.71 driver issue 

On Wed, 03 Oct 2007 19:48:20 -0400, Dudley Henriques
wrote:

>Peter wrote:
>> Workaround:
>> Start fs9, then set the AA setting in the forcedriver to none. Close fs9 and
>> restart. Set AA in the driver to the setting you want. AA wil be back. It
>> worked for me.
>> Peter
>>
>>
>> "Dudley Henriques" schreef in bericht
>>
>>> Downloaded the new 163.71 driver from Nvidia last night and replaced
>>> 158.22 on my XP/SP2 system using a BFG8800GTS/640 following my usual
>>> procedure (remove driver in add remove, then reboot and run driver cleaner
>>> for Nvidia, then reboot and install new driver in safe mode.
>>> Noticed immediately that in the Nvidia driver settings I had no AA setting
>>> showing. The AF was there but not the AA.
>>> I un-installed then reinstalled the driver with the same result.
>>> Finally I un-installed the 163.71 and reinstalled the 158.22 and the AA
>>> was back showing on the Nvidia list.
>>> I should add that the 163.71 driver seemed to be functioning normally in
>>> FS2004 which is the only program I use this computer for. No jaggies or
>>> issues; just the AA missing from the driver settings.
>>> Is this a known issue with this driver?
>>> --
>>> Dudley Henriques
>>
>>
>
>Thanks for the reply. Fixed it last night. AA can be accessed by right
>clicking the desktop instead of using the taskbar icon. Have no idea
>what the heck they did it this way but it works that way.
>DH

Ah. That explains why mine was working. I don't enable the icon
thingy.
 >> Stay informed about: A 163.71 driver issue 

Folk wrote:
> On Wed, 03 Oct 2007 19:48:20 -0400, Dudley Henriques
> wrote:
>
>> Peter wrote:
>>> Workaround:
>>> Start fs9, then set the AA setting in the forcedriver to none. Close fs9 and
>>> restart. Set AA in the driver to the setting you want. AA wil be back. It
>>> worked for me.
>>> Peter
>>>
>>>
>>> "Dudley Henriques" schreef in bericht
>>>
>>>> Downloaded the new 163.71 driver from Nvidia last night and replaced
>>>> 158.22 on my XP/SP2 system using a BFG8800GTS/640 following my usual
>>>> procedure (remove driver in add remove, then reboot and run driver cleaner
>>>> for Nvidia, then reboot and install new driver in safe mode.
>>>> Noticed immediately that in the Nvidia driver settings I had no AA setting
>>>> showing. The AF was there but not the AA.
>>>> I un-installed then reinstalled the driver with the same result.
>>>> Finally I un-installed the 163.71 and reinstalled the 158.22 and the AA
>>>> was back showing on the Nvidia list.
>>>> I should add that the 163.71 driver seemed to be functioning normally in
>>>> FS2004 which is the only program I use this computer for. No jaggies or
>>>> issues; just the AA missing from the driver settings.
>>>> Is this a known issue with this driver?
>>>> --
>>>> Dudley Henriques
>>>
>> Thanks for the reply. Fixed it last night. AA can be accessed by right
>> clicking the desktop instead of using the taskbar icon. Have no idea
>> what the heck they did it this way but it works that way.
>> DH
>
> Ah. That explains why mine was working. I don't enable the icon
> thingy.

Probably the reason Nvidia did it this way was because they "optimized"
many games in the advanced section for what they consider an optimum AA
setting for that program. This would require a seperate section which
they have.
I'm still trying to figure out why they couldn't have put a link to that
section in the icon's menus as before so people wouldn't have had to
spend time searching for it like I and many others have been doing.
No biggie really, and there must be a valid reason, but I just haven't
found it as yet

--
Dudley Henriques
 >> Stay informed about: A 163.71 driver issue 

On Thu, 04 Oct 2007 14:25:05 -0400, Dudley Henriques
wrote:

>Folk wrote:
>> On Wed, 03 Oct 2007 19:48:20 -0400, Dudley Henriques
>> wrote:
>>
>>> Peter wrote:
>>>> Workaround:
>>>> Start fs9, then set the AA setting in the forcedriver to none. Close fs9 and
>>>> restart. Set AA in the driver to the setting you want. AA wil be back. It
>>>> worked for me.
>>>> Peter
>>>>
>>>>
>>>> "Dudley Henriques" schreef in bericht
>>>>
>>>>> Downloaded the new 163.71 driver from Nvidia last night and replaced
>>>>> 158.22 on my XP/SP2 system using a BFG8800GTS/640 following my usual
>>>>> procedure (remove driver in add remove, then reboot and run driver cleaner
>>>>> for Nvidia, then reboot and install new driver in safe mode.
>>>>> Noticed immediately that in the Nvidia driver settings I had no AA setting
>>>>> showing. The AF was there but not the AA.
>>>>> I un-installed then reinstalled the driver with the same result.
>>>>> Finally I un-installed the 163.71 and reinstalled the 158.22 and the AA
>>>>> was back showing on the Nvidia list.
>>>>> I should add that the 163.71 driver seemed to be functioning normally in
>>>>> FS2004 which is the only program I use this computer for. No jaggies or
>>>>> issues; just the AA missing from the driver settings.
>>>>> Is this a known issue with this driver?
>>>>> --
>>>>> Dudley Henriques
>>>>
>>> Thanks for the reply. Fixed it last night. AA can be accessed by right
>>> clicking the desktop instead of using the taskbar icon. Have no idea
>>> what the heck they did it this way but it works that way.
>>> DH
>>
>> Ah. That explains why mine was working. I don't enable the icon
>> thingy.
>

>I'm still trying to figure out why they couldn't have put a link to that
>section in the icon's menus as before so people wouldn't have had to
>spend time searching for it like I and many others have been doing.
>No biggie really, and there must be a valid reason, but I just haven't
>found it as yet

I don't understand why people would want the icon down in the system
tray. It has no functionality that you can't get by right-clicking on
the desktop, so why have yet another resource-sucking application
constantly running?

I guess I'm old-school, but I just don't like a bunch of worthless or
functionally duplicated apps sitting in my system tray doing nothing.
 >> Stay informed about: A 163.71 driver issue 

Folk wrote:

>
> I don't understand why people would want the icon down in the system
> tray. It has no functionality that you can't get by right-clicking on
> the desktop, so why have yet another resource-sucking application
> constantly running?
>
> I guess I'm old-school, but I just don't like a bunch of worthless or
> functionally duplicated apps sitting in my system tray doing nothing.

Correct, while it's nice to have multiple ways to set a setting, when
the choice is made, the other options should be hide-able. Luckily,
nVidia's are. FWIW, not all tray icons or applets are cpu-cycle sucking,
interrupt crazy code warts. nVidias are, WERE, well behaved.

nWiz can be (should be) disabled if you have a single monitor. I would
leave the control panel dll active in all cases, it's what gives you all
of the nVidia tabs in the display pages and desktop access.

Also, the nvidia driver helper service is important for CRT users and
gamers who change resolutions, leave it running as it serves as an
overseer for certain settings that do not like to stay set.

Oh, I am so close to going on a a 163.71 rant right now...I finally
found out how to get them stable. I had to uninstall ntune completely,
Did you know it does not like to be uninstalled? (All of the useful
stuff of ntune is done in other and better ways)

Then I had to change both PCI-e and system speed timings. I had to drop
the PCI-e bus to 110MHz from 125MHz (100MHz is stock but 125MHz is
common and officially supported) and I had to slow RAM by 1MHz. Video
card core and memory timings were unchanged.

You know what I think? I think the new Punkbuster A (not Punkbuster B)
24/7 service does funny things with nVidia drivers. It might not be
nVidias fault at all. <throws up hands in mock disgust>
 >> Stay informed about: A 163.71 driver issue 

"Mr.E Solved!" wrote in message


[...]

> I would
> leave the control panel dll active in all cases, it's what gives you
> all of the nVidia tabs in the display pages and desktop access.

nvcpl.dll is hugely important. Not enough people know it has an API which
apps like RivaTuner rely on.
 >> Stay informed about: A 163.71 driver issue