Another nHancer problem

[raptorx]

OK, I will not turn off any of the services except nvwiz.  The digital vibrance I only adjusted for the first time, today, from it's default setting of "0".  The nhancer/shimmering scenery issues were happening before I discovered DV.  I only just experimented with a higher setting and the only thing it did was make my graphic colors more "vibrant".  It didn't seem to affect any other performance.  If you advise against setting this higher than "0" then I will follow that.

I am guilty of shutting down a few more services then you mentioned, mostly networking related I believe.  I have a solo computer at home, cable broadband internet, no wireless, nothing but windows XP and FSX.  I have not had any other issues connecting to websites, using digital content, or program hangups.  In fact, except for this wierd nhancer thing my sim works like a charm (except at LAX and Seattle, of course).  I will try to attach a list of the services I disabled, or pm it to you.

I didn't mess with the FSX.cfg more than your recommendations.  I set TBM to 70, widescreen view on, Buffer pool size to 6000000, no SWTO added, and I deleted the FFTF=.33 setting that megascenery put in (was told with SP2 that FFTF=.33 is not needed anymore).


I should also mention that today I noticed that the behavior I am seeing (less "filtered looking" graphics after a change in views from VC to spot, tower, etc) was happening without nhancer installed.  In other words:

Earilier today and for last 2 weeks)  169.13 beta driver, no nhancer, shimmering scenery graphics after change in views
Right now)  169.21 WHQL, fresh nhancer install, crystal clear scenery out of VC, until I go outside the plane, then shimmers



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

[raptorx]

Yes my monitor is set to 1600x1050x32, and FSX is too.  And I only use windowed mode if I need to look at task manager or other diagnostic utilities like coretemp or cpuz, but never for casual flying.

-J

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

[raptorx]

Here is my list of disabled services.  


Ad-Aware 2007 Service Disabled
Alerter Disabled
Automatic Updates Disabled
ClipBook Disabled
Computer Browser Disabled
Error Reporting Service Disabled
Fast User Switching Compatibility Disabled
Help and Support Disabled
Indexing Service Disabled
LightScribeService Direct Disc Labeling Service Disabled
Messenger Disabled
Net Logon Disabled
NetMeeting Remote Desktop Sharing Disabled
Network DDE Disabled
Network DDE DSDM Disabled
Network Provisioning Service Disabled
NMIndexingService Disabled
Performance Logs and Alerts Disabled
Print Spooler Disabled
QoS RSVP Disabled
Remote Desktop Help Session Manager Disabled
Remote Registry Disabled
Routing and Remote Access Disabled
Secondary Logon Disabled
Security Center Disabled
Server Disabled
Smart Card Disabled
System Restore Service Disabled
Telnet Disabled
Terminal Services Disabled
Uninterruptible Power Supply Disabled
Wireless Zero Configuration Disabled


I turn on updates and adaware when needed.

-Jim

[NickN]

Ok Jim, thanks for the run-down. That at least covers the basics

Justy an FYI, Black Viper (if you know who that is) is one of the most dangerous websites on the internet. Shutting down services such as DCOM, Scheduled Tasks and a few others are a NO NO and his site does not list the right way to shut things down either.

The only services that need to go away are the ones I listed but there are more if the system does not need them and you know they can be shut down. Black Vipers lists screw up a system

Use the LOGON tab in the service to disable them at boot, not just set them to DISABLED in the dropdown.

Its 10pm here and time for me to hit the sack.. I will look at this again tomorrow

In the mean time you may want to try the 169.09 beta driver, or, the last official, 163.75 WHQL




EDIT: OK, I see the list.. good choices but not everyone should shut those down (for those reading this thread)

Those are good to go

[NickN]

Oh yes, one last question, you seem to be a tweaker so I must ask this...  did you enter this line anywhere in the FSX.cfg file?

MipBias=X ( x= number ranging from 4 to


If so, delete then entire line(s) and try FSX again

[raptorx]

No I didn't.  That's a new one for me, haven't heard of that before.

[quote]

Oh yes, one last question, you seem to be a tweaker so I must ask this...

[NickN]

[quote]No I didn't.

[raptorx]

Thanks for the info on Black Viper.  I won't use that site anymore.  Actually what I did was look at several different sources for XP services and looked for a concensus on what was safe to disable.  Black Viper was one of them (but no longer).  I discovered your advice right before my last XP install and then followed your disable procedure.  Then I got a little bolder and disabled a few others that looked safe for me.  Thanks for putting my mind at ease as to what I have tweaked.   I also learned through previous XP installs that shutting down the wrong stuff (like task scheduler and Dcom, and a few others) can cause problems (a lot of grief by me trying to figure out what I messed up).

-Jim

[quote]


Ok Jim, thanks for the run-down. That at least covers the basics

Justy an FYI, Black Viper (if you know who that is) is one of the most dangerous websites on the internet. Shutting down services such as DCOM, Scheduled Tasks and a few others are a NO NO and his site does not list the right way to shut things down either.

The only services that need to go away are the ones I listed but there are more if the system does not need them and you know they can be shut down. Black Vipers lists screw up a system

Use the LOGON tab in the service to disable them at boot, not just set them to DISABLED in the dropdown.

Its 10pm here and time for me to hit the sack.. I will look at this again tomorrow

In the mean time you may want to try the 169.09 beta driver, or, the last official, 163.75 WHQL




EDIT: OK, I see the list.. good choices but not everyone should shut those down (for those reading this thread)

Those are good to go

[raptorx]

OK, thanks.

[quote][quote]No I didn't.