Simviation Forums

WARNING


NIVIDA ADDS PROFILES FOR FS9 AND FSX TO ITS DRIVERS

THOSE PROFILES OVERRIDE ANY SETTINGS YOU MAKE AND SCREW YOU UP WHEN TRYING TO GET THINGS TWEAKED. GET RID OF THEM AND SET UP THE DRIVERS CORRECTLY.

DELETE ALL THE PROFILES IN THE NIVIDIA DRIVERS AND RESET EVERYTHING WITH THE PROGRAM CALLED NHANCER http://www.nhancer.com/

THIS PROGRAM WAS RECOMMENDED BY A NVIDIA TESTER WHO KNOWS WHAT NVIDIA HAS DONE... ITS WRONG AND FORCES FSX OR OTHER GAMES TO RUN WHAT NVIDIA WANTS... AND YOU NEVER KNEW IT, NO MATTER HOW YOU SET YOUR DRIVERS.

AN ISSUE OF CORRUPT PROFILES HAS SURFACED TOO, SO GET RID OF ALL THE PROFILES AND SET YOUR DRIVERS UP MANUALLY

DOWNLOAD AND INSTALL NHANCER, RUN IT AND REMOVE ALL PROFILES. IT MAKES A BACKUP OF THEM SO YOU CAN RESTORE ONE OR ALL OF THEM IF YOU EVER WANT TO

BUILD YOUR OWN PROFILES FOR YOUR GAMES. DO NOT ALLOW NVIDIA TO MAKE THOSE SETTINGS CHOICES FOR YOU

ONCE ALL PROFILES ARE DELETED THEN SET UP A NEW PROFILE FOR FSX AND THE GLOBAL DRIVERS USING NHANCER AS FOLLOWS:

ENHANCEMENTS:
AA: CHECKED WITH A BULLET IN SUPERSAMPLING TO SHOW THE FOLLOWING SETTINGS:

Combined 8XS

Except the multicore thing the driver settings were old news for me (they work very well).


The FSX settings 'tho, most notably the "frame lock + TBM" hints smell like "smooth but blurry".
And I didn't notice any notable performance difference between max autogen and no autogen, so I doubt those values will have a performance impact at all.

I'll give "Framelock" and "TBM" a try, but I'd be very surprised if they actually improved something.


Thanks anyways, Nick.

Except the multicore thing the driver settings were old news for me (they work very well).


The FSX settings 'tho, most notably the "frame lock + TBM" hints smell like "smooth but blurry".
And I didn't notice any notable performance difference between max autogen and no autogen, so I doubt those values will have a performance impact at all.

I'll give "Framelock" and "TBM" a try, but I'd be very surprised if they actually improved something.


Thanks anyways, Nick.

I have been out of the loop for over a month so I post what I get when I get it and confirm its value.

Its a matter of how the hard drive is delivering the textures which makes TBM valuable to sharp textures. If the HDD is slower and higher TBM compensates, faster a lower TBM can be used with a higher SWTO

things to try

[Display]
TEXTURE_BANDWIDTH_MULT=100 // possible 120
UPPER_FRAMERATE_LIMIT=0

I dont care what you think... you are wacking your system to death running AG at 100% and no limited values  

As long as my CPU doesn't melt...

and I do agree more FSB and memory speed is critical     I run a 3.6Ghz CPU on 450FSB on a memory of 720 (DDR3 1440) @ 6-7-6-6 15 1T

My mem timings are quite bad (5-6-6-9 24), since I whacked my DDR 667 Ram to 800 to keep up with the 400 FSB.
It improved FSX big time 'tho.

Downside: I need to leave my case open or finally cut out the meshes blocking the case fans.

[quote][quote]I dont care what you think... you are wacking your system to death running AG at 100% and no limited values

Sorry to break in on a two way debate, guys.  But NickN you keep bringing up serious stuff that is quite radical.

I had never heard of Nvidia doing its own thing regardless of my settings.  Is this nhancer straight forward or are there steps which you have left out for the sake of brevity?

Many times it has dawned on me as I follow the instructions of you gurus that you are so familiar with computers you take our knowledge for granted - and leave out small steps that are obvious to you, but to which we are totally blind.  It causes much cursing in the southern hemisphere.

OT I spoke to my tech about your other post on RAID 0 stripes.  He went into convulsions.  He believed anything like that can only be done at the time of setting up a new system.  To do it after would mean re-formatting the hard drive and losing all of the contents - unless backed up and then reinstalled.  

Is he right or wrong?

is this the nV control panel games stuff, or something else?

like, u go into the control panel, and u find a whole list of games with custom profiles for each one.  if that's what u mean, then nVIDIA does do that, but i suppose its for the benefit of those who dont care about those settings.  its a shame that they do it to the FS series, because they know very well that we tweak through the CFG, not much through their thing, and in their way...

Last I knew a RAID 0 array was not possible without reformatting on the array. Why? because in a R 0 is a striped set of disks. When data is writen to the array it breaks up the files so your file lets say "clouds.bmp" is broken into two fragments on two or more harddrives. So the whole reason for Raid 0 is it can essentially access 2 or more parts of a file at a time(parallel)l. So while one hard drive retrieves the beginning of a file the second gets the second part and they are pieced together. So theoreticaly speed is increased by 2x. So unless there had been a huge technology advance in the past years that I missed where the OS can somehow take itself from one disk and all it's files and divide them between two disks.

EDIT: I read Nicks post about Raid down below and he says it can be done but by using a backup software such as Norton Ghost or ASR. So IMO it means complete restore for most users as Ghost can get a lil complicated.

This did nothing to me except lose me a frame or 2. Every time I do some of the tweaks you guys post here, something negative happens. So I'm done with tweaking. It runs fine with default AG numbers and sliders to MAX. As soon as I touch anything in the .cfg, it screws up. Oh well whatever. It's just too much of a hassle now to tweak it. We'll just have to wait for the newer hardware to come out because that'll be the only fix to run it maxed and smooth.

Well Nick, I must have done something wrong.  I followed your instructions and while the sim LOOKS better, it jumps between high frame rates and low frame rates which gives a HUGE stutter.  I tried lowering TBM but that didn't alleviate the problem.  Any other suggestions for a setting that needs to be changed?

Here

Tried a framelock of 31 and it was VERY smooth.... blurries were horrendous though.

P.S. What about ATi?  :-?  8-)

[quote]Tried a framelock of 31 and it was VERY smooth.... blurries were horrendous though.

P.S. What about ATi?

I lost some smoothness and at least a frame or 2 with the frame lock at 31 or higher, so that's staying at 18. I'm still running those settings that Nick gave us, along with a TBM of 70 and a radius of 4.5. I tried it at 6.5 and TBM at 120 and I got some stutters.

I really don't see too much of a difference between the 4.5 radius and 6.5 either.

But DO NOTE THIS>..

The higher the TBM and SWTO as compared to the AMOUNT of Autogen, the more likely stutters may occur

Do not set Autogen to ZERO that is a mistake.

Work the line numbers and test the slider at each of the following: DENSE, VERY DENSE, 100%

Now remember, cars and road traffic in the city can be a factor in microstutters so as you come out of KSEA toward Seattle you might get a small amount of stutter until you get just past the city.

I set up a system using ONLY the default 747 on runway 34R during the day using the weather pattern BUILDING STORMS. By doing so I am calibrating the sim to the heavy load of the 747 and the weather in a decent city environment and airport. Once its calibrated for that, pretty much any other plane and situation is covered.

I fly out of KSEA toward Seattle, stay strait, go up to 6000ft @ a 1300 FPM autopilot setting, fly down the coast till I hit water, turn around and land at KSEA on 16L. That circle takes me through 3 scenery environments and if its good, its set.