Hi all,Finally, with my new system I've got FSX nice and smooth (for the most part), but just wondering would I benefit from using an external FPS limiter. I'm pretty new to using FSX and I have been using the search function in these forums but still not sure. Any advice would be great. Thanks................

I have an external FPS limiter for my FSX installation on my MacBook Pro and I can run FSX in medium high settings. I noticed that the external limiter has been helpful as it provides a more solid target framerate than the FSX internal limiter ever could (actually the FSX internal limiter will kill some of your frames and go below the actual target rate).

Hi all,Finally, with my new system I've got FSX nice and smooth (for the most part), but just wondering would I benefit from using an external FPS limiter. I'm pretty new to using FSX and I have been using the search function in these forums but still not sure. Any advice would be great. Thanks................

Try it and see. If there's no improvement then you will no not to use it. I've never even tried it myself in the last 3 years i've been using FSX since mine seems to work just fine without it, but since everyones set up is different you might find an improvement.

I have an external FPS limiter too, and notice a big improvement over FSX's internal limiter To me, FSX run so much smoother with a external FPS limiter, that I would recommend it right off the bat to any one who is having problems with FSX...opps that could be everyone :(

Hi all,Finally, with my new system I've got FSX nice and smooth (for the most part), but just wondering would I benefit from using an external FPS limiter. I'm pretty new to using FSX and I have been using the search function in these forums but still not sure. Any advice would be great. Thanks................

The only thing the external limiter does is to simply limit the frames to a set value. The reason people say they see a performance benefit to using it is because when using it you need to set your internal limit to UN-limited. If when running unlimited you experience big fluctuations in your FPS/smoothness then you will see a benefit in using it, but if your setup runs fine at unlimited it is likely you wont see much advantage running it. On my system when flying one of the payware more complex aircraft I can run unlimited just fine. If using a default plane less demanding add-on the internal is fine. Opinions on this topic will be all over the board so like some have said it really is a try it and see thing.Jim

I have the external limiter with Bojote's tweak on the dual core / hd 5450 but I am not sure if it's doing anything, I am getting around 35-49 fps with all to max (graphics settings except the traffic which almost 0 and the water is set to low 2.1 , the road vehicles seem to kill the fps) , when flying in NY / Seattle frames drop to around 15 on ground and once above 2500-3000 ft I start getting decent frame rates really enjoying FSX now. I get some stutters at times but nothing that would make me ground FSX and go back to FS9.

I have always been rather skeptical of FSX tweaks, viewing most of them as snake oil. But the effects of Bojote's tweaks (which include using an external FPS limiter) were quite noticeable. I don't get a higher *minimum* framerate over cities and big aiports, but the simulation is smoother, with a more consistent framerate over simple and medium-density scenery like mountains, smaller cities and GA airports.The utility makes just a *few*, well documented changes to your FSX.cfg file, where as most tweaks involve changing parameters more or less at random because a friend of a friend of a poster said it tripled the framerate for his brother.With the Java-based FPS limiter I was getting some micro-stutters and not a consistent 30 FPS (it was jumping between 20-ish and 35 FPS). The dll-based FPS limiter works better, and by loading it from the enbseries.ini file, I can get HDR effects as well.

The only thing the external limiter does is to simply limit the frames to a set value. The reason people say they see a performance benefit to using it is because when using it you need to set your internal limit to UN-limited. If when running unlimited you experience big fluctuations in your FPS/smoothness then you will see a benefit in using it, but if your setup runs fine at unlimited it is likely you wont see much advantage running it. On my system when flying one of the payware more complex aircraft I can run unlimited just fine. If using a default plane less demanding add-on the internal is fine. Opinions on this topic will be all over the board so like some have said it really is a try it and see thing.Jim

I discovered the value of the limiter when it became apparent setting a frame lock within FSX loses some optimizations that happen when you run in unlimited mode and use of the limiter can overcome this. You can test this for yourself by creating a performance-demanding scenario such that when you limit frames internally at say 30, you notice the sim will only run at say 25. The user's assumption at this point is that the scenario is too complex to run at 30, so it settles around 25. Now change to unlimited mode: you'll see the same scenario running several frames higher, perhaps around 30. You can now apply FPS_Limiter.exe, set it at 30, and voila, you're running this scenario at 30. As Jim mentions, if you experience big fluctuations you can then benefit from using the limiter over plain unlimited. As a side note, I was experiencing frequent surges in the video output in some situations and I was looking exactly for a utility that would cap frames after FSX was done processing the video, to prevent these surges, and indeed this is exactly what FPS Limiter offered. The 'surges' I mention are what you would imagine the video would look like if you were flying along then suddenly the video would actually speed up dramatically just for a fraction of a second then revert to baseline rate. I never noticed that the frame counter would shoot up during these very brief and recurrent slips, but perhaps that was because they were too short-lived per event for the counter to pick up.Noel

Another thing you can play around with is the PRE-RENDER. The default is 3 but I find a setting of 1 works very well. Try it and see.Jim

There are a three posts here where the poster states he's using the FPS Limiter (I presume FPS_Limiter_02) along with the 64-bit version of Windows 7.. I have tried this little app with little or no success on my 7/64 machine, (although I think it did work with the 32-bit OS). I seem to remember a few months back ******* saying that it didn't work on 64-bit machines, and that he was going to approach the author requesting a 64-bit fix.. Was I dreaming this?? .. and JimmiG - this version - FPS_Limiter_02 uses both Java and dll's, so which application(s) are you talking about?

I discovered the value of the limiter when it became apparent setting a frame lock within FSX loses some optimizations that happen when you run in unlimited mode and use of the limiter can overcome this. You can test this for yourself by creating a performance-demanding scenario such that when you limit frames internally at say 30, you notice the sim will only run at say 25. The user's assumption at this point is that the scenario is too complex to run at 30, so it settles around 25. Now change to unlimited mode: you'll see the same scenario running several frames higher, perhaps around 30. You can now apply FPS_Limiter.exe, set it at 30, and voila, you're running this scenario at 30. As Jim mentions, if you experience big fluctuations you can then benefit from using the limiter over plain unlimited. As a side note, I was experiencing frequent surges in the video output in some situations and I was looking exactly for a utility that would cap frames after FSX was done processing the video, to prevent these surges, and indeed this is exactly what FPS Limiter offered. The 'surges' I mention are what you would imagine the video would look like if you were flying along then suddenly the video would actually speed up dramatically just for a fraction of a second then revert to baseline rate. I never noticed that the frame counter would shoot up during these very brief and recurrent slips, but perhaps that was because they were too short-lived per event for the counter to pick up.Noel

The internal FPS limiter in FSX is indeed quite strange and interacts in funny ways with the terrain rendering and general smoothness of the sim. It seems Aces made a lot of assumptions about how this all should work, but it didn't really work out as they expected.

Another thing you can play around with is the PRE-RENDER. The default is 3 but I find a setting of 1 works very well. Try it and see.Jim

This is definitely a setting you should play around with, especially if you suffer from micro-stutters or lag. I found that 3 works very well as long as its set both in the FPS limiter and in the actual driver profile for FSX, using Nvidia Inspector. For those with faster CPUs, for example, maybe a lower setting works better. Here's an explanation of the setting:http://www.nvnews.net/vbulletin/showpost.php?p=1568357&postcount=4

There are a three posts here where the poster states he's using the FPS Limiter (I presume FPS_Limiter_02) along with the 64-bit version of Windows 7.. I have tried this little app with little or no success on my 7/64 machine, (although I think it did work with the 32-bit OS). I seem to remember a few months back ******* saying that it didn't work on 64-bit machines, and that he was going to approach the author requesting a 64-bit fix.. Was I dreaming this?? .. and JimmiG - this version - FPS_Limiter_02 uses both Java and dll's, so which application(s) are you talking about?

FPS Limiter 0.2 worked fine on my Win7 x64 system, but I got better results with the other FPS limiter. The file is d3d_antilag101.zip. It's just one .dll file and a .cfg file, so there's no need to run a .bat file or run any program before you start FSX. You just drop the files into your FSX folder. You can use it together with Enbseries, by renaming the d3d9.dll file of the antilag to something else, and then edit the enbseries.ini file:[PROXY]EnableProxyLibrary=1InitProxyFunctions=1ProxyLibrary=<filename of the antilag .dll file>

The file is d3d_antilag101.zip. It's just one .dll file and a .cfg file, so there's no need to run a .bat file or run any program before you start FSX. You just drop the files into your FSX folder. You can use it together with Enbseries, by renaming the d3d9.dll file of the antilag to something else, and then edit the enbseries.ini file:[PROXY]EnableProxyLibrary=1InitProxyFunctions=1ProxyLibrary=<filename of the antilag .dll file>

Thanks Jimmi - Tried it, too, a while back, but I'll give it another shot. The problem is - plain locked at 30 within the sim - everything is smooth and constant, no matter where I am, or what I'm flying, and I can only attribute this to the proc speed.

Thanks Jimmi - Tried it, too, a while back, but I'll give it another shot. The problem is - plain locked at 30 within the sim - everything is smooth and constant, no matter where I am, or what I'm flying, and I can only attribute this to the proc speed.

...and the external fps limiter gives me blurries close in - whereas the FSX limiter loadsthe textures in time..