"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."There's a misconception that's been going around since CFS 2 that MSFS will scale back detail based on a min. frame rate, which is a set percentage of the frame rate lock. It did work that way in CFS2--the idea was battle sequences needed the highest performance possible, so the sim scaled back detail if the sequences started causing fps to drop below the minimum, assuming you had Auto LOD enabled. But for some reason, the "Auto LOD" was it was called was disabled in FS2002 and remains disabled in FS2004 even though the cfg entries are still there. You'll even see posts discussing the min frame rate and ways of tweaking it--but it doesn't work and it's never been documented as working for FS2002 and FS2004. So where does that leave us? Over a period of time, in the flight levels, if the sim is crunching along at 40, 50 fps and you come in for a landing and you're greeted with 20 fps, it has the same effect as cruising down the Interstate at 75 and hitting a 55 mph zone. 55 will suddenly seem like a crawl compared to 75, even though 55 is a lot better than walking from SFO to San Jose :) The fps lock really does help--I keep mine at 25--even though I know I can peak in the 40's given my sim settings and a rather bland scenery area. I find with the lock there, I focus on flying and performance is quickly forgotten. If I were getting anything below 18, that's another story--I'd start adjusting detail accordingly so I can maintain that, but I do that before a flight knowing where I'll be flying and what level of AI and weather I'll be expecting. Once I am flying, I won't pause the sim for any reason--well, almost any reason since time with my family is better than any sim.-John

No I don't think so. It would actually run off of existing data fields like this example:The frame rate LOCK is currently set at 30, and you are seeing a V value fluctuating between 2.0 and 2.9% or so. As you are simming along, you begin to approach a high-demand situation. FS programming senses this as the V value begins to increase up to 6-7%. This is sensed instantaneously, and the frame lock is lowered to that value that will maintain the V value at <3.0% (you could make this variable user configurable with a slider).In this situation, there is no need to sample scenery. The code in FS already displays both variables: frame lock, frame rate variability. All you need is a simple feeback loop that adjusts the lock on the fly. Sounds terribly simple, though I may be missing something. If this indeed were the mechanism, it would hardly take any resources, absolutely minimal.

>In this situation, there is no need to sample scenery. The>code in FS already displays both variables: frame lock, frame>rate variability. All you need is a simple feeback loop that>adjusts the lock on the fly. Sounds terribly simple, though I>may be missing something. If this indeed were the mechanism,>it would hardly take any resources, absolutely minimal.Of course it can be done. Lago did it with their utility program. Unfortunately, they didn't bother sharing their discovery with anyone else, and they are out of business...

Thanks, John. You answered that much more thoroughly than I would have, not knowing about CFS2's auto LOD adjustment feature. I wonder why it wasn't enabled in FS2004, as it sure would be helpful.

I see what you're saying, Noel. Yeah, looking at the fps difference only probably would have minimal effect.

>>In this situation, there is no need to sample scenery. The>>code in FS already displays both variables: frame lock,>frame>>rate variability. All you need is a simple feeback loop>that>>adjusts the lock on the fly. Sounds terribly simple, though>I>>may be missing something. If this indeed were the>mechanism,>>it would hardly take any resources, absolutely minimal.>>Of course it can be done. Lago did it with their utility>program. Unfortunately, they didn't bother sharing their>discovery with anyone else, and they are out of business...Bill,Lago did it for FS2000.It changed the frame rate on the fly and was hardly perceptible when it kicked in. When asked if it could be done for subsequent versions of FS including 2004 Mathijs Kok (who I believe) explained that subsequent versions of FS made a significant change to the way the scenery was handled which made it impossible to do FSAssist (as it was called)for the later versions. So I don't believe it is possible.Keith Cocker