When you insert the statement:AVE_FRAME_RATE_DISPLAY=1into fs9.cfg, you get to see the low, ave and high frame rates during sim operation. From a post I read, last character set relates I believe to the variance, and is expressed as a percentage. He mentioned he sets his frame lock such that the variance value displayed is around 3% or less, giving him the best compromise between smooth and highest frame rate. I think it's a sound concept.How hard could it be, for someone who understands programming, to make a very simple module that would do just that: adjust the frame lock based on the V level, to be as close to 3% as possible, in real time (or nearly so as the case may be). Since this info is all builtin to FS, it seems very doable. Then, when you fly thru various complexity loads, you will always be tuned optimally (within the context of your otherwise well tuned system.What do you think?Noel

I think the main problem here is that I don't think frame rate lock could be adjusted on-the-fly like that.

I don't really understand what's going on here, but I don't think changing the lock value on the fly is a problem. The program could keep a log and test various values on several restarts of FS. It would take a while to run, but automating it for people might be useful.Thomas

With all due respect Ken, what information do you have that would lead you to this conclusion?

I'm just not familiar with any method to do it. Just changing the value in the cfg files will not tell FS to reload that value. And I have not heard of any way to re-load this value programatically via SDK or FSUIPC. But I could be wrong...if someone would post a way to reload the lock value, your idea could be implemented.

Hello kenThere was a module for FS2000 called FSassist that let you choose the required frame rate for different stages of flight and it adjusted scenery complexity on the fly.http://www.avsim.com/pages/1100/utility2/u...w_part_two.htmlSo maybe the variables still exist in FS9.

I have been using this concept for quite some time -- I noticed that if I lowered the maximim FPS setting to a point where the % variation is also low (yes, below3%), I get smoother flight with less stutters. It certainly works.But the trouble is that you do fly through different areas and hence you are stuck with these lower FPS rates in areas which could allow higher rates.Although all the sliders have some impact on FPS, I find that the biggest killer of FPS is buildings (non- autogen)at airports and clouds (especially when using real weather).Barry

>Hello ken>There was a module for FS2000 called FSassist that let you>choose the required frame rate for different stages of flight>and it adjusted scenery complexity on the fly.>http://www.avsim.com/pages/1100/utility2/u...w_part_two.html>So maybe the variables still exist in FS9.>That looks great -- I wonder if anybody has it and would be willing to see if it works with FS2004 Barry

It wouldn't be hard to program, but there are some clarifications to this idea that merit mentioning.A computed standard deviation shows how variable frame rates are over a set period of time. However, in order to generate smooth, steady display you want to pick a target frame rate that is the lowest tolerable frame rate, and no consideration given for how variable frame rates are.When you lock frame rates at a very low level then there is no variability in frame rate display rates, because the computer can easily handle the demands of the display. At higher frame rate locks then there is increasing variability in frame rates because the limits of the hardware are reached. This idea says, in effect, to set an optimal frame rate, set the target frame rate high enough so that frame rates start to vary, but no higher.The current concept of target frame rate is intended to smooth out differences between heavily modeled areas (where frame rates are low) and lightly modeled areas (where frame rates are high), by selecting the lowest tolerable frame rate, so that the frame rate the same irrespective of how densely modeled an area is. With the new idea, frame rates would continue to vary between areas with heavy modeling (such as airports and cities) and areas with relatively sparse modeling (for example rural areas), because the target frame rate would be dynamically changing in response to variation in the frame rate of the display.This leads to the second consideration, that is, whether or not MS2004 allows target frame rate setting to be dynamically manipulated programatically while the game is in progress. I don't know the answer to that question.

>However, in order to generate smooth, steady display you want to >pick a target frame rate that is the lowest tolerable frame rate, >and no consideration given for how variable frame rates are.I disagree. The whole point of the of the concept is to be able to maximize frame rates in areas that can handle it, and lower the frame lock dynamically when frame rates can't be maintained any longer. With the model you descibe, you are sacraficing upper end performance, with arguably better sim fluidity, in order to prevent occasional poor performance in the most demanding situations. When I can predict the sim will not function well due to the type of scenarios involved, I manually set the frame lock lower. As soon as things improve situation-wise, I sometimes jack up the lock to enjoy the more fluid experience. Your other point, whether or not you can set frame rate dynamically, is obviously critical. I think the big challenge would be just exactly what to look at and when in order to automate the process.

you said that in less demanding situations you jack up the lock to enjoy the more fluid experience?! - well, sorry, but eeew!

You are depraved Cindy!

Maybe something for MS to take note of and implement in future versions of FS? A feature such as "Auto detect framerate lock"?/assuming MS rep is reads this threadJames

It sounds like a good idea in theory, Noel. But accomplishing it would require an additional process of some sort of regular sampling of visual detail to be displayed. I

"Another possible approach to this issue that has crossed my mind is to build in an auto adjustment of scenery detail level in order to maintain a given frame rate."Isn't that exactly what the FPS lock in FS does? I thought it adjusted scenery density, clarity, etc. in an attempt to maintain the preset FPS setting.Does the FPS lock just keep the FPS from exceeding this value? I'm getting confused.