Some might disagree, but i find this one much smoother than the FPS Limiter 2.0 and it seems to control the fluctuations closer to your limit setting. Also it does not involve the need for Java to create a .bat file which is needed in Limiter 2.0 to run it in FSX. With Antilag you just drop a .cfg file and another file into your FSX root folder and go fly. You set your fps and render ahead by editing two numbers to your requirements and you're done.

It could also just be smoothing the display of your FPS .. in other words, it might not be any better in controlling fps ... just displaying it different vs. alternative.

You could be right. Sometimes it comes down to personal preference.

Looking at the NGX right now, i'm seeing 22fps, p33fps, 28fps looks very smooth to me. I guess continuity is more important, if you stutter then the illusion is broken.

What is your opinion on the method of limiting those frames. Externally, with FSX to unlimited? Or internally, just using FSX?

I use two config files, one with FSX internal fps set at 30, for not so busy area's and hight Altitude. It prevents the big fps fluctuations, preventing stutters.The second cfg file has the internal FPS set at Unlimitted for busy airports, and scenery like OrbX. It will give you higher framerate and a smoother experience in that environment. The external fps limiter does a good job when you only use one monitor, with fsx in windowed mode and don't unlock any windows. As soon as you unlock a window, the external fps limiter will cut your overall fps in half, and you loose the smooth experience. For instance, if you have a dual screen setup and have the cockpit view on one screen, and the 2D panel on a second monitor. When the external fps limiter is set to 30 fps, you will actually only have fsx running at 15 fps, and plenty of stutters to go with it. I have a multi monitor setup and start my flights with the "unlimited" cfg. after departing the airport anf getting to cruising altitude, I quickly switch to the 30 fps locked cfg file. Just before Top of Decent, I switch back to the "Unlimited' cfg. Also when I fly low alt. vfr I use the "unlimited" cfg, making it possible to enjoy the scenery with a smooth running sim and the sliders mostly maxed out. Mathijs Kok, from Aerosoft, wrote a nice article about setting up fsx and the use of multiple cfg files for different types of flights, that can be found on the Aerosoft forum. Btw, loading a different cfg only takes a few seconds, so I don't see it as a hassle, but that is a pure personal experience. If you want to try an external limiter, try both that were mentioned in earlier posts. Experiment with bot to find out which one work best for you. It will not harm your fsx, as you can just get ride of it, if you don't like what you experience. Manfred Luederitz

what happens if we run the NGX at a lower FPS say 20 or so?

I use two config files, one with FSX internal fps set at 30, for not so busy area's and hight Altitude. It prevents the big fps fluctuations, preventing stutters.The second cfg file has the internal FPS set at Unlimitted for busy airports, and scenery like OrbX. It will give you higher framerate and a smoother experience in that environment. The external fps limiter does a good job when you only use one monitor, with fsx in windowed mode and don't unlock any windows. As soon as you unlock a window, the external fps limiter will cut your overall fps in half, and you loose the smooth experience. For instance, if you have a dual screen setup and have the cockpit view on one screen, and the 2D panel on a second monitor. When the external fps limiter is set to 30 fps, you will actually only have fsx running at 15 fps, and plenty of stutters to go with it. I have a multi monitor setup and start my flights with the "unlimited" cfg. after departing the airport anf getting to cruising altitude, I quickly switch to the 30 fps locked cfg file. Just before Top of Decent, I switch back to the "Unlimited' cfg. Also when I fly low alt. vfr I use the "unlimited" cfg, making it possible to enjoy the scenery with a smooth running sim and the sliders mostly maxed out. Mathijs Kok, from Aerosoft, wrote a nice article about setting up fsx and the use of multiple cfg files for different types of flights, that can be found on the Aerosoft forum. Btw, loading a different cfg only takes a few seconds, so I don't see it as a hassle, but that is a pure personal experience. If you want to try an external limiter, try both that were mentioned in earlier posts. Experiment with bot to find out which one work best for you. It will not harm your fsx, as you can just get ride of it, if you don't like what you experience. Manfred Luederitz

Thanks Manfred for your detailed reply. I do use the Antilag limiter but was interested in your opinion. Your multi config method sounds interesting and i will take a look at. The switching part is what intrigues me.

I'm a gamer since the very beginning on the C64. I am used to have stutters in my games for 30 years. So why should I worry about stutters? It is a game and not reality. Sure, it is better to have more fps, but I will not die for a good frame rate.The only nasty thing with these stutters is that when you start with a new software like the NGX, with each stutter you expect that FSX will crash. So currently I have a lot of light heart attacks every day. Martin

30 is good, but I'm an FPS junkie, so it's 60 FPS. Some games glitch at those rates, and enable you to see things faster, jump higher, etc... 30-40 with FSX is what I can settle with.

If you are a serious flight simulator enthusiast, your eye has been unintentionally trained to detect the difference between 15 , 25 and even 60 fps. For some reason we are constantly looking for frame problems when flying. If you show your gaming to someone who is not a simmer, that person may not see a difference between 18 and 30fps.We, on the other hand, pay closer attention to frames and therefore can see the difference between 25fps and 60fps because we are constantly looking for it. Unfortunately, for us, we are spending less time monitoring our flying and more time looking for frame problems outside the cockpit. It’s the way it is and we are not going to change.The following test will show you that we can detect the difference between 15, 30 and 60 fps. When they tell you that the ceiling is 25 fps, wrong……http://www.boallen.c...ps-compare.html

I like the FPS over 60 fps. 100 fps make me happy. Then I know I am rocking.

Films are render to 23.976 FPS. The eye can detect movement from 3 FPS. Detecting movement is not the same as seeing smooth movement, which is why films in the cinema are at 23.976 FPS. You will see absolutely no difference between something like 24 or 23 FPS and 30 FPS, 40 FPS, 60, 70, 120, 10000, 10000000000 FPS.

Perhaps in a linear environment this statement may be correct but in a 3D environment like FSX's VC cockpits it's certainly VERY noticeable the difference between 24 and higher fps. Throw TrackIR into it and you can see immediately that higher fps gives smoother panning, I like it around 35 or above, anything lower and you get ghosting

I like the FPS over 60 fps. 100 fps make me happy. Then I know I am rocking.

In my dreams!

I can only speak for what I see, and that is that I can notice the difference between 25fps and 50fps. You can do a test yourself in FSX (try to look closely at 25fps, then 35fps and then 60fps). You see a smoother flying as the frames increase. I don't know what the ceiling would be for the human eye, but I welcome a surplus in frames any day. Some would say this is psychological and that 25fps is all the human eye is capable of absorbing. I personally think this number is much higher.

As stated by others, the human eye will see any framerate for 24+ as continuos motion. At that level, the human eye does no longer SEE individual frames, Now that is a fact.

*sigh*When will this myth finally stop?That "fact" is only true for films, where you have motion blur that fools the eye into seeing fluid motion. It absolutely is not true for games like FSX where every single frame is pin sharp. You don't believe me? Watch the action scenes in Saving Private Ryan, Gladiator or 28 Days Later. These scenes use high speed shutters that eliminate most of the motion blur, with the result that you clearly see a stutter and not fluid motion anymore, even though the framerate hasn't changed.

40-60 no lessabove 60 i can not tell but the stutters and non-smoothness becomes quite noticable below 40. however in fsx it took me a while to get use to lower frames but if i can get frames from 25-60 i am very satisified point being u just have to accept lower frame rates and get adjusted to it and then its all good but at least with my setup i usually get 40-60 fps and it works well