wow, thats fast, thanks!

Can you try increasing the RejectThreshold value? in which areas are you experiencing this stuttering? If I were to guess, I'd say you use a non standard Scenery radius value... probably you are using 6.5 / 7.5 correct?

could you please explain what you mean with "non standard scenery radius"?I have a german FSX so its sometime hard to find the settings when explained in english...Which line is that in the FSX.cfg?(If you mean LOD_RADIUS, thats 4.500000 here)

wow, thats fast, thanks!could you please explain what you mean with "non standard scenery radius"?I have a german FSX so its sometime hard to find the settings when explained in english...Which line is that in the FSX.cfg?(If you mean LOD_RADIUS, thats 4.500000 here)

Better send me the 'link' to the 'tweaked' fsx.cfg file so I can take a look at it. Don't post the link here, send it to me privately.

ok, I have sent you via mail out of your profile.Thank you very much for your effort!!!GünterEDIT: going to bed now...just for the case you wonder why you don't hear anything more from me. Thanks a lot!!!)

wow, thats fast, thanks!could you please explain what you mean with "non standard scenery radius"?I have a german FSX so its sometime hard to find the settings when explained in english...Which line is that in the FSX.cfg?(If you mean LOD_RADIUS, thats 4.500000 here)

hmm.. interesting, you fsx.cfg contains wrong info (and the tool did not spot it) here:[bufferPools]PoolSize=0RejectThreshold=131072 UsePools=1 The above section is wrong! here's your original:[bufferPools]// RejectThreshold=98304 // Vertex data at or over 96KB does not get pooled and bypasses the bufferpoolRejectThreshold=131072 // Bojote tweak, //512Kb = 524288, 256Kb = 262144, 128kb=131072, 124Kb = 126976, 96Kb = 98304UsePools=1 // Setting this to 1 will turn the BufferPools ON (stability), setting it to 0 disables them (Performance).// PoolSize=8388608 // Defines an 8MB BufferPoolPoolSize=0Notice that you are telling FSX to use Pools AND to use the RejectThreshold, but then you tell it to use a PoolSize of 0! change the above to:[bufferPools]PoolSize=16777216RejectThreshold=131072 UsePools=1

When I input my fsx.cfg file I get the following message:Your request could NOT be processed.Reason: This tool only reads ANSI files. Your fsx.cfg file is in utf8 format. Can someone please help me with that.ThanksBernd

Your request could NOT be processed.Reason: This tool only reads ANSI files. Your fsx.cfg file is in utf8 format. Bernd[/b][/b]

Bernd, make a copy of your fsx.cfg file in your desktop. Now, open it. Now, save it using the option that says 'save as' and make sure you select the option to save the file as type ANSI.The tool currently reads fsx.cfg files in ANSI format only. I assume your's is utf-8 because your fsx.cfg is in german or japanese. I'm a lazy programmer ;)

Thank you so much for your response, I did what you proposed and it worked, great tool. BTW, this is not German, just English - must have come from some FS German programs I downloaded. Your analysis shows that I still have an old video card on it although I thought I deleted it. Any idea where this might come from.ThanksBernd

vSync FIX => FSX included two options to enable vSync, but they were deprecated, not used anymore. I discovered the 'real' switches to enable vsync in FSX. This will eliminate 'tearing' but will reduce your FPS in half (to 30) due to the inability to keep 60 FPS constant. If 30 can not be kept, then FSX will fall to 20, then 15, 12 and so on.. thats why it is SO important to lock your frames EXTERNALLY to either 30 or 20.. you have to use multiples of 60!!!

*******, could you please explain the above in a bit more detail to me? I used your automated tweaking and tuning tool for FSX and I'm quite happy with the results, but I doubt if my framerate will double if I disable vsync.

*******, could you please explain the above in a bit more detail to me? I used your automated tweaking and tuning tool for FSX and I'm quite happy with the results, but I doubt if my framerate will double if I disable vsync.

The following text was taken from: http://www.brighthub.com/computing/hardware/articles/27719.aspxDouble BufferingYour graphics card has a frame buffer and a back buffer. It draws a picture in the back buffer, and when it’s ready, it moves the back buffer image into the frame buffer. Your monitor gets the screen from the frame every time it refreshes, as many times per second as its refresh rate.Tearing occurs when the monitor takes the image from the frame buffer while it is being copied over from the buffer. The monitor ends up displaying a picture made up from horizontal section of two different, consecutive frames.VSync fixes that by only letting the copy from the back buffer to the frame buffer begin immediately after a refresh. That, however, means the graphics card has to wait to start on the frame after the one in the back buffer until the monitor refreshes. That’s fine if your frame rate is higher than your refresh rate, since your graphics card has enough time to get a new frame ready.If your FPS drops below your refresh rate however, the frame in the back buffer won’t be ready in time to move to move to the frame buffer on the next refresh, and your monitor will just show the same frame twice. Assuming your frame rate is below, but greater than half, your refresh rate, the next (different) frame will be ready to move from the back buffer at that point, and get picked up on the next refresh. That’s why VSync can cut frame rates in half.Triple Buffering By adding a third, behind-the-back-buffer, buffer, the graphics card can get to work on the frame after the next one as soon as soon as the frame in the back buffer is done. It doesn’t have to wait for the next refresh to clear the back buffer.Now, if your FPS drops below your refresh rate, the graphics card can still supply frames as fast as possible. Depending on how far below, you will still have a certain number of pairs of frames that remain identical, but your FPS will be whatever it is, not halfed.As a common example: you’re playing with VSync on, a 60Hz screen, and a frame rate of 60 or more, which VSync caps at the screen’s 60Hz refresh rate. Some sweet looking explosions cut your frame rate to 50 FPS. Without triple buffering, the graphics card can only get one screen out every other refresh. Every other refresh just repeats the previous frame, for an effective 30 FPS.With the extra buffer, you only have as many identical frame pairs as the graphics card can’t supply. Continuing our example, you would get nine good refreshes, and only every tenth would be identical to its predecessor. That’s 50 FPS, almost as much as your card could do without VSync and triple buffering.Why almost? Well, triple buffering fixes the problem with VSync at the cost of its own problem. Otherwise, we could just turn them both on and forget about it. The third buffer, when you think about it, has to go somewhere in memory. Depending on how much memory is on your graphics card, triple buffering might trim its overall performance slightly.So VSync On or Off? It depends on your monitor’s refresh rate and how fast your computer can run the games you play. Depending on the game, you may want to turn it on or off. Conveniently, its easy to setup your graphics card to do this automatically.

Hi *******,just as a little information:unfortunately your settings (see posts above) have lowered my frames from stable 30 (fps limiter) to about 20 and lower.The (micro)stutters aren't solved so far.But I have found out, that they are present despite if autogen or scnenery density is on or off. Absolutely no difference.I have deleted my fsx.cfg now and let it rebuilt, because there was so much tweaking stuff in it, I'll start from scratch.The FSX.cfg rebuilt haven't solved the stutters...Simply I run out of ideas right now... Maybe I have to accept them.

Maybe I have to accept them.

No matter how many tweaks you have, if your hardware is not up to the task and/or your OS is not tuned you'll experience problems. I'll suggest you start fresh with a fsx.cfg and read NickN guide here http://www.simforums.com/forums/topic34141_post198187.html#198187 let me know how it goes after you tune your OS.

Hi *******,thanks a lot for your tool, truly very useful and well done!I'm running FSX SP2 with W7/64 on a rather slow PC by today standards (a 6600 quad o/C to 3.0 GHZ, 4GB DDR2/800 mem, GTX 8800 768 MB, SONY CRT 28" at 1280x1024 for FSX). Recently, I migrated from XP/32 to W7/64 and I got a definite improvement in performance.W7 is tuned to the max and FSX already runs very smoothly. A couple of comments about your tool:I submitted my fsx.cfg and in the briefing page and got... congratulations about an optimal TextureMaxLoad value, but I don't have such a line in my fsx.cfg, I have only a "Texture_Max_Load=1024" line. Is it a bug or does it refer to my default setting?I have briefly tried the new settings and, at least at first, they don't seem to make much of a difference from my old ones (really, my PC was already running FSX very smoothly with quite no stutters and/or blurries, even with "heavy" settings, so I didn't expect much change).In any case, I think I'll keep these new settings and test them in depth, to see if there is difference in some situations.Again, thanks for your outstanding contribution.CiaoFulvio.

Hi *******,:blush:I have made now an other approach of the whole "problem":I have searched on youtube for similar PCs showing FSX in action.And what I have seen was that every other FSX video is showing "my stutters", also your latest one!Mostly there where much bigger stutters that on my machine...And I have to apologize, but I have bite myself into this little stutters like a Jack Russel Terrier.Every time the last days I've started FSx I just have looked onto these little stutters and they where driving me crazy and I've thought I get more and more of them.So, in my case, the best tweak is now to turn off FPS display and starting some difficult approaches so I have no time to pay attention to these little stutters...I relly appreachiate your effort for the simming community and your patience with us!thanks again!

. congratulations about an optimal TextureMaxLoad value, but I don't have such a line in my fsx.cfg, I have only a "Texture_Max_Load=1024" line. Is it a bug or does it refer to my default setting?Fulvio.

Not a bug, Fulvio.Under [GRAPHICS] you should have:-TEXTURE_MAX_LOAD=1024and under [DISPLAY] you should have:-TextureMaxLoad=12Both do different things.

congratulations about an optimal TextureMaxLoad value, but I don't have such a line in my fsx.cfg, Fulvio.

Fulvio, thanks for pointing that out. I just noticed I was not adding it if that line was not present. It has been corrected.