Great job *******!However, last night I had my first CTD, after a two hour flight, and I'm not sure what caused it, since it's the first time I'm using a tweaked fsx.cfg and fps limiter (as suggested). I guess the best place to start from would be the bufferpools???

Hi Kiwi; Yeah - it's the UIAutomationCore.dll that will cause that kind of CTD - not the BufferPools. A wrong BP will give you odd 'jumping', unstable frame rates, hesitations, but generally not a CTD. The HIMEM Fix gets rid of large-scale white flashing, and water=2xhigh gets rid of small areas flashing.

Hi Kiwi; Yeah - it's the UIAutomationCore.dll that will cause that kind of CTD - not the BufferPools. A wrong BP will give you odd 'jumping', unstable frame rates, hesitations, but generally not a CTD. The HIMEM Fix gets rid of large-scale white flashing, and water=2xhigh gets rid of small areas flashing.

Hi Paul J, thanks for your reply.I ran a few more tests, and I think I managed to narrow down some specific results.a) Even after copying the right version of UIAutomationCore.dll to my fsx root folder, I still got a CTD at exactly the same scenery area.b ) What is special about this area is that the flight takes place above ground, and only then I start getting the first glimpses of water.c) Flying with the LDS-767, I get a CTD. However, when changing to a different aircraft I'm getting these odd jumpy unstable fps you described, but no CTD.d) To confirm that water was the main suspect, I opened nVidia Inspector and noticed my GPU load while looking around the scenery. And there it was. When looking over the ocean my GPU load would jump to 99% (with jumpy unstable fps). When looking over the land, GPU load would drop to 40-50% and have stable fps.My water effects are @ high.2x, and my tweaked fsx.cfg has these values[bufferPools]RejectThreshold=131072[GRAPHICS]SHADER_CACHE_PRIMED_10=1693458432SHADER_CACHE_PRIMED=1693458432Ideas?

Thanks for taking the time to make this, really useful.I have one question, I keep getting this message from my cfg, your TEXTURE_BANDWIDTH_MULT is being COMPLETELY ignored under your actual configuration, you can very well forget about it.MAKE SURE to disable Transparency Anti-aliasing for improved smoothness with your NVIDIA GeForce 9800 GTX/9800 GTX+ card. How do I repair this ?

Thanks for taking the time to make this, really useful.I have one question, I keep getting this message from my cfg, your TEXTURE_BANDWIDTH_MULT is being COMPLETELY ignored under your actual configuration, you can very well forget about it.MAKE SURE to disable Transparency Anti-aliasing for improved smoothness with your NVIDIA GeForce 9800 GTX/9800 GTX+ card. How do I repair this ?

TEXTURE_BANDWIDTH_MULT is ignored by FSX if:1) You run frames set to UNLIMITEDor2) If your UPPER_FRAMERATE_LIMIT is HIGHER than your TEXTURE_BANDWIDTH_MULT value.The tool is aware of this, so it warns you so you don't waste time adjusting TEXTURE_BANDWIDTH_MULT.Transparency AA can be disabled in your card Control Panel or nVidia inspector, simply look for the option called Transparency AA and set it to NONE -or- to Sparse Grid 4X SuperSampling

Ideas?

Do you have the Shader 3 mod installed? if so, can you try uninstalling it and try again?

That makes sense, thanks for your help.

Do you have the Shader 3 mod installed? if so, can you try uninstalling it and try again?

I get a CTD with or without Shader 3. I changed water to low.2x and just managed to fly a bit further. In the end... CTD. Here's the event log in case it helps:Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3Faulting module name: terrain.dll, version: 10.0.61472.0, time stamp: 0x475e180dException code: 0xc0000005Fault offset: 0x00055a3eFaulting process id: 0x31cFaulting application start time: 0x01cbc3c751e95f47Faulting application path: E:\Microsoft Flight Simulator X\fsx.exeFaulting module path: E:\Microsoft Flight Simulator X\terrain.dllReport Id: 582b6c86-2fc3-11e0-90c7-d027883e36b4

I get a CTD with or without Shader 3. I changed water to low.2x and just managed to fly a bit further. In the end... CTD. Here's the event log in case it helps:

Delete (or rename) your fsx.cfg and have FSX build a new one for you. Do NOT edit anything on the file manually, simply set settings via the FSX interface and test again. If everything works then forget about tweaking your file, if it crashes again then you have some other problem I can not help you with and I'll suggest reading, understanding and applying NickN's Win7 guide to the letter to see if it helps you with the issue.

You have A/C reflections disabled. They can only be enabled via fsx.cfg manual edit.

First and foremost thank you for such a great aid to FSX. What I am wondering about is this line I quited above. I've searched on the net and here but have not found anything that refers to adding this line to the fsx.cfg. Actually I'm not precisly sure of where in the fsx.cfg file I would append a line to make this change and I'm not sure just what I would need to type; i.e. "A/C reflections=true" or something along those lines?

[/size][/font][/font]First and foremost thank you for such a great aid to FSX. What I am wondering about is this line I quited above. I've searched on the net and here but have not found anything that refers to adding this line to the fsx.cfg. Actually I'm not precisly sure of where in the fsx.cfg file I would append a line to make this change and I'm not sure just what I would need to type; i.e. "A/C reflections=true" or something along those lines?[/size]

[GRAPHICS]ALLOW_SHADER_30=1AC_SELF_SHADOW=0AIRCRAFT_REFLECTIONS=1

This tweak has lowered my FPS a little, could I send you my fsx.cfg ******* ?? Just to double check my settings ?

This tweak has lowered my FPS a little, could I send you my fsx.cfg ******* ?? Just to double check my settings ?

Paul, after uploading your file for tweaking, the tool shows you a detailed text on what to do if you get lower performance. Did you read this text? what steps (from the text) did you follow? and most importantly, how are you measuring this 'lower' performance?

Hi *******,any news about releasing your "secrets"?Michael

Hi *******,any news about releasing your "secrets"?Michael

Like I said before, the new tweaks are NOT for improving 'performance' but to reduce frame rate volatility. They help with the occasional stutters and since I'll be sharing this publicly it needs to be properly documented/tested, so I'm taking my time and using them myself.This is just one of them, If you like it, and it works for you, then probably the others will be also be beneficial.[GRAPHICS]SHADER_OPTIMIZE=0 // (default is 1)The above will compile shaders inside FSX using less efficient optimizacions at compile time for shader effect files (.fx), they will be bigger files, but compilation for this files will be 'INSTANT' so when approaching areas (airports/cities) with lots of scenery (for the first time) you'll not experience stutters due to shader compilation (which happens only ONCE)To test this:1) Set the above option to 12) Clear your shader cache 3) Pick a big airport and try an approach (start AWAY from the airport)4) You'll notice short 500ms microstutters (2 or 3) as shaders are compiled for the first time approaching the airportRepeat the above with SHADER_OPTIMIZE=0 and performance is 'exactly' the same, except for the micro stutters. Does this *IMPROVE* performance? NO!! I never said that, read, test and if you are all about smoothness then you'll find some value to it. Is there any side effects? Not using a GTX480, so No idea what the effect will be with ATI's and/or older cards.Obviously, this is NOT the kind of 'tweak' you 'include' in a tweaking tool. It has to be part of a document with 'things to try' and meant only for advanced users.

I see.Just tested this one,but cannot notice any difference.I use a 285GTX with the latest WHQL Driver.Michael

Hi *******, just like to thank you for your excellent Automated Tweaking & Tuning tool for FSX. My FPS has improved on average 50%.Thank's again, Ray.