Another nHancer problem

[raptorx]

Hello, new guy here;

I am using nhancer, lastest version,

[NickN]

That is a strange one.. Never seen or heard of that one

You did follow the directions carefully I assume? Selected to duplicate the FSX profile, Repeated the same settings for "global" as well as "profile"?

And you did set FSX up as I outlined, trilinear and AA unchecked?

Did you verify the profile was indeed duped and the settings are correct?


Its possible that beta driver does not agree with your system. You may wish to try either the latest official driver or a different beta

[raptorx]

Hi Nick,

Yeah, I did it on top of a fresh XP install after discovering your instructions for FSX clean install, XP setup, and nhancer setup.  All my profiles were dup'd & the originals deactivated just like you said it would do.  Did the global settings also.  Is the 169.04 driver a beta?  I had good results w/FSX with that driver, haven't used it with nhancer.

I can't find any other driver on nVidia's website except the 169.21 and you said that was bad.

I was checking my task manager when nhancer was installed and the service was always there and using around 6-9mb of memory.

[NickN]

Sounds like you got it right.

Try another driver... you can find them all here for XP x32: http://downloads.guru3d.com/download.php?id=10

And yes, I found the 21 series drivers to be duds. Sometimes drivers can be funny though... there is an entire list of reasons why they may not work well for many and a few may see better results.

Try a few different ones and you may even wish to consider the official 21's. Although I never checked the officials, the beta 21's were the ones I did not like.



See if a driver change fixes it and if not post back and post which driver revisions you tried

[NickN]

opppsss, almost forgot... you did update DirectX, correct?

[NickN]

and one other thing too... if after you have tried drivers and everything else checks out, grab a screenshot of the inside of the VC and one of the outside which shows the problem you are seeing. You must reduce them to 800x600 and make the file size 100k or less to post them here... then post them so I can see what you are seeing.

Sometimes a picture speaks louder than words

[raptorx]

I can try the release 169.21.  I'll work on the screenshots this weekend.  I uninstall the driver in windows, boot up in safe mode, and use driver sweeper.  Then install the new driver and enhancer and all the rest, right?  By the way, as a new member I am impressed by all the help you provide to folks.

FYI, my sim includes UTX, GEX, and FEX from flight1; FS Global 2008 for the rest of the world, FSgenesis North American mesh; and Megascenery X Socal, Phoenix, and Las Vegas.  All this seems to work well together.  I just can't wait for solid state drives.

Thanks,

Jim

[raptorx]

I think so, I did my latest XP install about 3 weeks ago.  The setup version shows 4.9.0.904 I think.

opppsss, almost forgot... you did update DirectX, correct?

[NickN]

[quote]I can try the release 169.21.

[raptorx]

I uninstalled 169.13 and installed the 169.21 release, then installed enhancer and set it up.  I still have the issue.  It's more like a shimmering appears as soon as I switch views.  Everything in the VC still looks good but the scenery shimmers much more and I can't get it to stop without exiting the flight and reloading it.  But I have to stay in the original VC view, the one that is loaded by default when I "fly now", for scenery graphics to not shimmer.  It also looks like the edges of the airplane loose some AA in the external view.  I'll try to get screenshots but I don't think you'll see the shimmering.

The 169.21 driver seems to be smooth though.  I might stick with it.

I wanted to ask if it was OK to disable the nvidia display driver service and all the other stuff that comes with a driver install (the rundll32 servive, etc.).  I'd go into msconfig and deselect all the nVidia stuff in the startup.  I'd keep enhancer.  Does that sound OK?

I did discover in the nvidia control panel under display settings when I increased the "digital vibrance" to 35-50% it made colors stand out much better.

Anyway I can live with the shimmers for now.  Should I be concerned that nhancer is adversly affecting anything?

-Jim

[NickN]

[quote]I uninstalled 169.13 and installed the 169.21 release, then installed enhancer and set it up.

[flyinjoe]

raptor,

There appears to be some issues with the latest official (not the beta 169.21) Nvidia drivers and Nhancer.   In short, it seems to break the custom profile capabilities, which would explain why you are not seeing any AA in the external view and it may appear that AA is working in the cockpit since AA is not as noticable in the cockpit.  There have been a number of threads I've read that mention this issue and I have also run into the problem myself, although some people claim it still works so I don't know who to believe.  I do know that the suggested fix for those having problems (and it worked for me as well) is to set up Nhancer using the settings that NickN suggests, but do it through the Global setting, not the custom profile setting.  This of course will effect every game you play, but it does allow you to use Nicks's suggested settings as before in FSX.  If you also play any other games, you will need to readjust your global settings before entering that game if you don't want to use the same ones as you use with FSX.

For reference:

http://www.nvnews.net/vbulletin/showthread.php?t=104249

http://nvnews.net/vbulletin/showthread.php?p=1497734


Since some people claim it's not broken, i'm still playing around with Nhancer and these new offiicial drivers to see if it is indeed broken or if I can figure out if it's something i'm doing wrong.  Maybe I screwed up the uninstall of my last driver set in some way as to effect Nhancer with the new ones.  In the mean time, i'm just using the global setting in Nhancer since FSX is pretty much all I play on a regular basis.  

[NickN]

He is seeing this in the 169.13's as well as the 21's

Nv broke AA since 169.17 but the global settings should restore it and he said he duped the profile and set global as well



I am starting to wonder if its specific to the card, or, some type of setting we are missing, or, something he may have swtched off or adjusted past my recomendations.



I was on 169.13 before I started working with a new ATI card and I had no problems with AA in 169.21, only their performance

[flyinjoe]

Oops.  I should have read every post.  I just started at the one where he mentioned he installed the 169.21's and it sounded a lot like what I experienced when I installed the newest official drivers so I thought i'd mention the profile problem with Nhancer.  Since I came to the 169's from the 163's, I was unaware that AA has been broken.  Guess you can disregard my post raptor.  

[NickN]

Jim

I know this may sound strange but I must ask, are you setting the monitor scale and resloution (x32) up in Windows after the driver change?

And going into the FSX settings and setting the monitor resolution (x32) up in FSX to the correct native resolution of the monitor?

I assume so because you said you see no problem without Nhancer installed but I must ask to cover all the bases here


and you are running full screen in FSX correct? Do not run window mode, ever



yes flyinjoe, Nvidia broke FSAA several times over the last year with Nhancer but recently it was in the 169.17 beta thru to date. In the past the Nv changes were corrected by using global which is why I have people use the global setting feature. Its easy enough to change SSAA from within nhancer for other games if needed