WARNING ABOUT ALL NVIDIA DRIVERS

[aussiewannabe]

[quote]I hope I don

[justpassingthrough]

[quote][quote]I hope I don

[aussiewannabe]

By setting that switch, it tells the sim to back off your memory and system and let you decide, saving all that memory for the real flight.

Having that preload was one of the things that really ticked me off about the design of the software. Its like Nvidia telling you what settings you will use without you knowing that if you change them manually, it wont really change.

Excellent :-)

I know FSX is a memory cruncher, but that start-up will make your blood pressure rise :-(

Off to make the change :-)

Thanks again.

[justpassingthrough]

By setting that switch, it tells the sim to back off your memory and system and let you decide, saving all that memory for the real flight.

Having that preload was one of the things that really ticked me off about the design of the software. Its like Nvidia telling you what settings you will use without you knowing that if you change them manually, it wont really change.

Excellent :-)

I know FSX is a memory cruncher, but that start-up will make your blood pressure rise :-(

Off to make the change :-)

Thanks again.

If you have flown FSX without that in the file and then edit it in, make sure to reboot the computer after adding that line or you are not getting the initial load memory back. Rebooting the computer will clear the memory of the original FSX file loads that wre forced on the system without the switch in the file.


Off to start my defrag runs now.. I got it all restored on a single SATA drive instead of RAID

[aussiewannabe]

If you have flown FSX without that in the file and then edit it in, make sure to reboot the computer after adding that line or you are not getting the initial load memory back. Rebooting the computer will clear the memory of the original FSX file loads that wre forced on the system without the switch in the file.

Glad I checked back before logging off

[lost16]

The last driver to be pulled were 162.15 those gave the BSOD when accessing control panel in any way.  I dl 162.18 from station drivers and they have the whql tag on them there.  Newest xp drivers so far and I am running xp64

[justpassingthrough]

[quote]The last driver to be pulled were 162.15 those gave the BSOD when accessing control panel in any way.

[DizZa]

Try adding DirtyRegionUpdateLimit=0 to your [GRAPHICS] section of your fsx.cfg. Phil said that it 'forces full texture updates', so textures don't incrementally sharpen. They are sharp or not sharp.... seems to have good results on me.

You can also try MergeDirtyRegionUpdates=0, I am trying that now.

[ATI_7500]

Sounds intersting, ZeroTime.



Btw: I'm running the 162.15s without any problems.

[DizZa]

Hmmmm... Lots better now!

MergeDirtyRegionUpdates=1
DirtyRegionUpdateLimit=0

Seemed to of worked nicely as has the TBM / SWT chart. Autogen ratio of 4.5/3 is better than 1/2 in my opinion. Now running at 1125/750 Very Dense.

IMAGES REMOVED DUE TO NOT BEING WITHIN FORUM GUIDELINES!
Please read the Guidelines for posting Images here at Simviation!
THANK YOU!

I still get blurries over cities at over 190 knots though. I reckon I'll eventually iron them out... If I don't then maybe the DX10 patch will help. Heck, I reckon fsX isn't even hard on the computer anymore. S.T.A.L.K.E.R was way harder.

I think I'll try water on high 1.0x to see if that resolves the blurries.

P.S. Will converting all textures to DDS help save CPU power? (DDS is upside down which is how it's drawn).

[alrot]

:-/ ,...I ,....I don't know what to do! :-/ Nick I have a good but maybe not enough FX6200, I just download the software Nhanser you recomend, I follow miltestpilot post ..

I know I been kind of anoying ,see ,My problem its too much reading for a nonnative english spoker ,Nick or anyone would you please suggest me a tweak for my FSX.cfg? And if this worth to apply Nhanser it to my video card?..

EDIT: I mean Miltestpilot its been very usefull with his shotsBut I still need a hand in the FSX .cfg

[justpassingthrough]

Try adding DirtyRegionUpdateLimit=0 to your [GRAPHICS] section of your fsx.cfg. Phil said that it 'forces full texture updates', so textures don't incrementally sharpen. They are sharp or not sharp.... seems to have good results on me.

You can also try MergeDirtyRegionUpdates=0, I am trying that now.

Placebo

those are only for the glass cockpit and gauge issue Nvidia drivers had. ATI is not effected by it and Nvidia fixed it in the latest official driver release

[quote]There is a tweak that helps with panel updates, especially the glass panel. If you use the glass panel and notice very slow updates. There is a

[justpassingthrough]

Seemed to of worked nicely as has the TBM / SWT chart. Autogen ratio of 4.5/3 is better than 1/2 in my opinion. Now running at 1125/750 Very Dense.

You can forget about autogen ratios too. NickN posted they are specific to your system now where before we could figure out the ratio.

Why? Quite simple my dear Watson. In case you missed that post by NickN, autogen was originally designed to be 10x FS9 so it was a matter of someone calculating the rendered polys from FS9 to FSX. Mr Bear Grils did that and we had numbers to work with because we knew the same, or very close, value in FSX was 600/300 @ 100% slider.

When they produced SP1 the reduced the major AG radius to 2.5 miles and also took out the alpha fade, then changed the way they were rendered and also changed the files that call for the AG

[DizZa]

I find the 4.5/3.0 ratio much better than 2/1 if some people are still using it. I also have a hard time beleiving autogen was reduced in SP1... I have two screenshots here that show identical autogen.

http://img172.imageshack.us/img172/3123 ... 140wn8.jpg

http://img172.imageshack.us/img172/7337 ... 843jf4.jpg


Bear Grylls? Wtf? Why bring him in? What about Chuck Norris?

http://www.beargrylls.com/

[macca22au]

Yes I have been working on AG of 1000/1000 but its now a matter of preference based on your system.

Alrot:  there are good posts in this forum, and Phil Taylor's blog has a summary document of suggested changes to the FSX.cfg.  But Miltestpilot and NickN in this thread, and FSX and SP1 thread, have good suggestions.

I differ in one way.  I have found Phil Taylor's suggestion to use a very low Fibre Frame Time Fraction and a low Texture Bandwidt Multiple to work.  I use an FFTF of .10 and a TBM of 30.  

Others swear by removing the FFTF line from the cfg altogether and using the TBM and Swap Time Out lines according to that table.

It is horses for courses.  Try what suits you.

But the nHancer really works.  I fussed and fumed until I could comprehend how to make it work,  but it is great when you get it set up.

de nada