During the g3d.dll crash troubleshooting period (see other posts in this forum) I have used a brand new "untweaked" fsx.cfg to exclude tweaks from being the source of any crash. However, once the issue has been resolved I have returned to my "standard" fsx.cfg settings, and despite the hardware I have, I still find that the following tweaks are giving me the best, smoothest, completely blurry-free, (and since Pete's g3d.dll fix, also CTD-free) FSX flying experience, even at very high scenery settings...

• NO external FPS. Max FPS set to 25 internally in FSX
• Bufferpools=0
• FFTF=0.1
• Affinity Mask = 14

This is very controversial as I have read other posts in this and other forums highlighting issues with the above settings, so I am just curious to see other people's experience. I know that maybe what is best for one simmer may be totally bad for another (this would not be a surprise for FSX users....!!).So, in the end, do all you guys with high end systems still tweak fsx.cfg or not ?Regards

On my current system with it's overclock, I get very smooth flight and very decent framerates. The add-ons I have currently are:Genesis MeshUTXGEXREX2 w/OverdriveThe only time I get stuttering, is if on final approach there is a lot of cloud cover, and then only if I switch to external view. Internal VC view remains fluid.I run with most sliders very biased to the right, ie full autogen, full cloud coverage. I do not limit fps in any way, have it set to unlimited within the FSX program, I seem to get smoother flight with this setting.The only changes I have in my fsx.cfg:TEXTURE_BANDWIDTH_MULT=80WideViewAspect=True -> as I run a widescreen monitorTERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1500TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=1000TEXTURE_MAX_LOAD=4096 -> due to running REX2I have thought about the affinity mask tweak, but since it is running so smooth for the most part, figured if it ain't broke...

HIGHMEMFIX is "Must Have".Turning on AM smoothed the stutters. Trees and Building tweek probably not needed, try it and see.DaveIntel Core I7 975 Quadcore OC @ 3.75 Ghz (Air)Asus P6T DLX V2 X58 1366, BD Combo Plextor B310SA6GB (3x2GB) Corsair Dominator DDR3 1866C7GTHIS ATI 6950 2GB, Samsung 24", Saitek X-52 ProLogitech Z680 5.1 Speakers, G15 Keyboard, G5 MouseThermaltake Element S Case, Corsair 850HX PSUC: Intel 80GB SSD w/Windows 7 Home 64D: WD 300GB Velocity Raptor w/FSX+Accel+GEX, F4AFE: WD 1TB Caviar Black w/Data SH4

Using a quad core i7 950 CPU OC'd to 4 ghz should the A.M. be set at 0, 14 or 84 for best results? Thanks.

During the g3d.dll crash troubleshooting period (see other posts in this forum) I have used a brand new "untweaked" fsx.cfg to exclude tweaks from being the source of any crash. However, once the issue has been resolved I have returned to my "standard" fsx.cfg settings, and despite the hardware I have, I still find that the following tweaks are giving me the best, smoothest, completely blurry-free, (and since Pete's g3d.dll fix, also CTD-free) FSX flying experience, even at very high scenery settings...

• NO external FPS. Max FPS set to 25 internally in FSX
• Bufferpools=0
• FFTF=0.1
• Affinity Mask = 14

So, in the end, do all you guys with high end systems still tweak fsx.cfg or not ?Regards

O, yes, we still have to tweak. People who say they don't have to tweak and still get great results are using low settings. BP=0 is the most important one. I use PoolSize=0 BTW. I also use the ingame limiter (been using an external limiter until I found out you get more blurries with it). It's a bit less smooth then with the external limiter but texture loading is a LOT better. I also use the affinity mask tweak (@BogeyFree: 14 is the most used setting afaik) although I am not sure it really makes a difference. Beside those tweaks I use Highmemfix and Disablepreload. WIth all this I get great performance with Extremely dense autogen and all slider settings right (apart from water at High 2x), even above PNW Seattle and Portland.P.S. I also use the Orbx Day Night switcher which is the icing on the cake: without it I would struggle above Seatlle and Portland.

AM=14 is correct. FSX does not use hyperthreading and should be turned off in BIOS. Turning it off makes my cpu run about 4 degrees C cooler (64C).I get a few extra fps with external limiter and it stops atogen spikes with internal at unlimited.Dave

Ok thanks. I just did some experimenting using A.M. settings of 0 then 14 then 84 and found that with H.T. disabled in the BIOS and the A.M. set at 14 that gave me the best results.

Ok thanks. I just did some experimenting using A.M. settings of 0 then 14 then 84 and found that with H.T. disabled in the BIOS and the A.M. set at 14 that gave me the best results.

Interesting I may have to give that a try myself.

Dittto.I used the BP=1 with my 4890 card with LOD=8. I deleted it with my new 6950 card with LOD=0. I have not tryed BP=0, yet.I deleted trees and building tweak since I didn't see any help with it. Like silk and 30 fps!Dave