Hi guys:I wanna get the 560 TI to replace my existing gtx275 -assuming it's an actual upgrade. Question, will the TI reasonably keep pace with FSX under heavy load (I5 @ 5GHz), or do I need to get the 570? My GTX was fine with my E8400, but the GTX 275 gets burried with the new processor unless I use your tweak utility in conjunction with FPS Limiter. I'm looking at the TI because I like the fact that it's 2 inches shorter than the GTX275/GTX570 and burns a little less juice than the 570. I don't plan to use this rig for anything other than FSX?Your thoughts? -Ken

I´m trying to use the tool but over and over I get a messeage: "Your request could NOT be processed.Reason: The [MAIN] section should be unique, there are two or more sections with this name."I do somehing wrong but don´t know what! Help anyone...?

I´m trying to use the tool but over and over I get a messeage: "Your request could NOT be processed.Reason: The [MAIN] section should be unique, there are two or more sections with this name."I do somehing wrong but don´t know what! Help anyone...?

I had the same problem. And the "PROXY ERROR" that I mentioned before is only on Opera.You just have to delete the second [Main] part of your fsx.cfg (you probably added manually a line, as I did).EDIT : how do you use the FPS Limiter you suggested ? The Readme's in german. (maybe another suggestion for a FPS limiter ?)A downloadable version would be great :)EDIT2 : and thank you for this wonderful program ! I had 11 FPS above Kennedy Intl ; I now have ~27 ! (my config file was very bad I suppose...)

You just have to delete the second [Main] part of your fsx.cfg (you probably added manually a line, as I did).

That was it. So easy when you know what to do.After a small flight I am amazed. Fps are a higher but most important is that now FSX super smooth, really a pleasure to fly!!

I used your tool (already got good framerates normally though, except for when I'm at kinda populated airports like LAX) and it lowers my settings a lot. But it did give me advice on my frame limiter (I got it at 30 now, might improve my spotplane view performance)

The tool added a FFTF=0.1 to my cfg.My understanding of this is that FFTF is completely useless in SP2 on multicore CPU's unless you are using photo scenery. Did something change in this thinking?

Hi *******,I experimented with your tool yesterday evening.I had a relatively good cfg already, giving me a stable +/- 30 FPS using the external limiter.After testing the CFG generated by your tool, I started to experience texture "corruption":-Terrain textures started to "flash" white randomly.-When panning around, lights would appear as black boxes/black cones for a split second.Any ideas what would cause this and how it could be fixed?System Specs:Phenom II X4 @3.8ghz4gb GSkill Ripjaw DDR3-1333Asus Radeon 6850Catalyst 11.2Thanks for your help!

-Terrain textures started to "flash" white randomly.-When panning around, lights would appear as black boxes/black cones for a split second.Any ideas what would cause this and how it could be fixed?

Sure,Set the water slider one notch before the maximum setting, that will get rid of the white flashesLook for the TextureMaxLoad setting in the [DISPLAY] section and increase it a bit, also look forSWAP_WAIT_TIMEOUT and set it to 3 or 4

The tool added a FFTF=0.1 to my cfg.My understanding of this is that FFTF is completely useless in SP2 on multicore CPU's unless you are using photo scenery. Did something change in this thinking?

FFTF is used by the FSX engine to determine the ammount of time to 'allocate' for loading scenery data. The default is 0.33. This means that 33% of the time it took to render a frame will be used for the actual loading of scenery data. So, if rendering a frame took 10 milliseconds, the CPU time slice for loading scenery data will be *RESTRICTED* to no more than 3.33 milliseconds.FFTF also behaves diffently under unlimited frames vs limited frames conditions. (if used whith UNLIMITED frames this value has little impact if set above 0.20 as it seems that a lot of the fiber work has been moved off to the seconday threads) with LIMITED frames is far more effective because the MAIN thread *IS* used for terrain loading when there is available CPU power available. If you have MANY secondary threads doing scenery loading, then you'll probably (using the above example) never will reach the 3.33 milliseconds limit, but the main thread will have to deal with a way to 'merge' the data from the secondary threads into usable data.. this 'merge' produces a... micro stutter, this happens aprox every 60 seconds AND is barely noticeable but is aggravated when your autogen levels are set above DENSE because of the extra work the main thread have to do to merge everything into data the main thread can use... remember, the main thread *IS* the 'real' bottleneck here..If you have a SINGLE CPU, obviously changing the FFTF will have a considerable impact on performance. If you have MULTIPLE CPU's then is not much of an issue because secondary threads will be the ones affected and not the main thread. There is, however still some impact. Secondary threads will have to cooperate with the 'main' thread for terrain/scenery processing/loading and the more 'secondary threads' you have the more chance you have of experiencing stutters/micro stutters if using 'high' FFTF values (this is true if the fiber queue can't keep up with the number of jobs entering the queue in part, because of their inability to handle I/O blocking calls properly. In such cases is probably better to reduce FFTF to .10 or .20 or use an affinity mask to restrict secondary threads to one or two (thats why people use AffinityMask=14 or AffinityMask=12 and report less stutters)The frame rate volatility issue (aka stutters) was something ACES (I believe Phil Taylor or Adam) discussed a while back when talking about 'fibers'.My personal opinion is that the fiber scheduling algorithm in FSX is not very efficient when dealing with blocking calls/asynchronous I/O, thats why no matter if you have a 10Ghz CPU you will ALWAYS experience some kind of stuttering when using autogen! there is simply no way around this, except playing with the FFTF value and lowering autogen a bit. The sad true is that the fiber and multithreading implementation in FSX is not optimal... don't get me wrong, it 'works' its just not up to my obsessive compulsive standars :) is not a big deal for most, but it is for me as we all have different opinions on what 'excelent performance' means.Read more about fibers here:http://www.gexperts.org/articles/fibers/

FFTF is used by the FSX engine to determine the ammount of time to 'allocate' for loading scenery data. The default is 0.33. This means that 33% of the time it took to render a frame will be used for the actual loading of scenery data. So, if rendering a frame took 10 milliseconds, the CPU time slice for loading scenery data will be *RESTRICTED* to no more than 3.33 milliseconds.FFTF also behaves diffently under unlimited frames vs limited frames conditions. (if used whith UNLIMITED frames this value has little impact if set above 0.20 as it seems that a lot of the fiber work has been moved off to the seconday threads) with LIMITED frames is far more effective because the MAIN thread *IS* used for terrain loading when there is available CPU power available. If you have MANY secondary threads doing scenery loading, then you'll probably (using the above example) never will reach the 3.33 milliseconds limit, but the main thread will have to deal with a way to 'merge' the data from the secondary threads into usable data.. this 'merge' produces a... micro stutter, this happens aprox every 60 seconds AND is barely noticeable but is aggravated when your autogen levels are set above DENSE because of the extra work the main thread have to do to merge everything into data the main thread can use... remember, the main thread *IS* the 'real' bottleneck here..If you have a SINGLE CPU, obviously changing the FFTF will have a considerable impact on performance. If you have MULTIPLE CPU's then is not much of an issue because secondary threads will be the ones affected and not the main thread. There is, however still some impact. Secondary threads will have to cooperate with the 'main' thread for terrain/scenery processing/loading and the more 'secondary threads' you have the more chance you have of experiencing stutters/micro stutters if using 'high' FFTF values (this is true if the fiber queue can't keep up with the number of jobs entering the queue in part, because of their inability to handle I/O blocking calls properly. In such cases is probably better to reduce FFTF to .10 or .20 or use an affinity mask to restrict secondary threads to one or two (thats why people use AffinityMask=14 or AffinityMask=12 and report less stutters)The frame rate volatility issue (aka stutters) was something ACES (I believe Phil Taylor or Adam) discussed a while back when talking about 'fibers'.My personal opinion is that the fiber scheduling algorithm in FSX is not very efficient when dealing with blocking calls/asynchronous I/O, thats why no matter if you have a 10Ghz CPU you will ALWAYS experience some kind of stuttering when using autogen! there is simply no way around this, except playing with the FFTF value and lowering autogen a bit. The sad true is that the fiber and multithreading implementation in FSX is not optimal... don't get me wrong, it 'works' its just not up to my obsessive compulsive standars :) is not a big deal for most, but it is for me as we all have different opinions on what 'excelent performance' means.Read more about fibers here:http://www.gexperts.org/articles/fibers/

Thanks for the in-depth explanation!

I can't have VSync in windowed mode, but it's working in full screen. I see in my fsx.cfg that you added two lines for VSync, both on TRUE (1). In my Nvidia Control panel, I set both global and FSX parameters to "use application".Anything I forgot ?

I can't have VSync in windowed mode, but it's working in full screen. I see in my fsx.cfg that you added two lines for VSync, both on TRUE (1). In my Nvidia Control panel, I set both global and FSX parameters to "use application".Anything I forgot ?

Try to 'force it' using the nVidia control panel, I don't run FSX in windowed mode so no idea how to solve it. Another possibility is that windowed vsync is broken with FSX but not sure about that.

Ok, it's not working ; thanks anyway :(

I found something very strange !I'm now running FSX with VSync forced in FSX.cfg, NOT in my Nvidia Panel. When I launch FSX, the aero theme is automatically disabled. Using the repair utility, it can be enabled again ! And this is a miracle -> 60FPS, VSync is working in windowed mode. The only problem is using the Aero repair utility is a long process and I don't think I will use it each time I start FSX. If someone know how to force FSX to NOT disable Aero themes, it would be very helpful...I made a .bat file wich will enable Aero Theme. Double click on it after launching FSX. http://www.mediafire.com/?e5le65ix8yb85zfI think this is pretty useful because I also notice a performance boost. - BTW, thank you Microsoft to make no efforts at all to keep FSX updated :) -

I can't use this tool :(Every time I get this:Proxy ErrorThe proxy server received an invalid response from an upstream server.The proxy server could not handle the request POST /cgi-bin/fsx.cgi.Reason: Too many (10) interim responses from origin serverP.S. I don't use any proxy!--------------------------------------------------------------------------Solved! This problem only appeares, when I use Opera. In IE all works fine.