To all,I have read the previous (and then some more) threads about fps_limiter but I can't get it to work (I think)After the download, I unzipped the package to a temporary folder (outside Program Files) and I created a bat.file.Running this bat.file FsX starts so at least that part of the .bat is correct.However, when checking the frame counter, I notice that the frames bounce up and down between 25 and 41, even with fps_limiter on 30. The second indication is that no counter is displayed on screen, even if I enabled the counter in the GUI of fps_limiter.So now I wonder what could be wrong...?any suggestions?Luc BrusselmansBelgium

When I was still using FPSLimite I was also experiencing bouncing framerates, but mostly in areas with lots of autogen or while in the clouds with heavy weather. Turning down the resolution of my cloud textures and decreasing the amount of autogen did help me a bit then though I have never been able to eliminate the small surges.

When I was still using FPSLimite I was also experiencing bouncing framerates, but mostly in areas with lots of autogen or while in the clouds with heavy weather. Turning down the resolution of my cloud textures and decreasing the amount of autogen did help me a bit then though I have never been able to eliminate the small surges.

Alexander,The small surges I can live with. But surges between 26 and 45 (as I am experiencing now) are far less acceptable.The whole purpose is to eliminate those fluctuating framerates and to gives a smoother ride... I assume there is something wrong with me, setting up this program but I can't figure out what the problem is.It runs on a windows 7 64bit system and I am beginning to think that that is the problem.Anyway,I will try your suggestion and start 'tweaking' fs-X and see what I get as a result.ThanksLuc BrusselmansBelgium

There is nothing wrong with FSP limiter, its designed to limit the frame rate not boost performance in a system that cannot handle a poorly optimised add-on like PNW for example. Orbx PNW looks beautiful but it seriously needs the autogen optimising like GEX Europe has, this is what causes the big spikes in frame rate, YOU SIMPLY NEED TO LOWER YOUR EXPECTATIONS OF WHAT YOUR SYSTEM CAN HANDLE i.e. turn the autogen slider down a couple of notches and then FPS limiter will help maintain a more stable frame rate.

There is nothing wrong with FSP limiter, its designed to limit the frame rate not boost performance in a system that cannot handle a poorly optimised add-on like PNW for example. Orbx PNW looks beautiful but it seriously needs the autogen optimising like GEX Europe has, this is what causes the big spikes in frame rate, YOU SIMPLY NEED TO LOWER YOUR EXPECTATIONS OF WHAT YOUR SYSTEM CAN HANDLE i.e. turn the autogen slider down a couple of notches and then FPS limiter will help maintain a more stable frame rate.

It's my opinion that the PNW is in general a very good add on. Flying over rural areas and forrest is very smooth with high autogen settings. Over dense urban areas the fps hit i heavy, but reducing the autogen buildings by adding a setting for TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL as adviced on the FTX support forum will take care of that problem. I believe that if you get add ons that add a lot to the visual experience you have to expect some performance hit. But to say that the PNW scenery is poorly optimised seems a bit too much IMO.Spikes in frame rate is a normal behaviour when running FSX in DX9 mode. Limiting the fps to 22 or 30 have given many simmers a smooth flight. Well worth trying.

I'm sorry but this doesn't happen in GEX Europe because it has been optimised in such a way as to not but an undue strain on FSX in major metropolitan area's, if Nick and Anthony can do it I see no reason why Orbx cant do the same. Putting TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL then ruins the optimisation in GEX and its a pain in the backside having to go in a comment out this field when not flying in the PNW region.

There is nothing wrong with FSP limiter, its designed to limit the frame rate not boost performance in a system that cannot handle a poorly optimised add-on like PNW for example. Orbx PNW looks beautiful but it seriously needs the autogen optimising like GEX Europe has, this is what causes the big spikes in frame rate, YOU SIMPLY NEED TO LOWER YOUR EXPECTATIONS OF WHAT YOUR SYSTEM CAN HANDLE i.e. turn the autogen slider down a couple of notches and then FPS limiter will help maintain a more stable frame rate.

Andy,I am probably wrong here but I don't seem to understand your reply.(and I don't like to be shouted at because I know very well what my system can or can't handle)I don't expect FSPL to boost my performance.... How did you get that idea anyway?The whole idea is to use the advantages of the 'unlimited'setting within FSX without the disadvantages...If I limit my framerate within FS-X to let's say 30, I get a relative smooth ride, no spikes (and certainly not upwards). Is it then wrong to assume that FSPlimiter will lock my framerate on the 'driverlevel' to 30 (give or take a few %) while I set the framerate in FSX to unlimited?Because, when I go back to the very first thread about fsp_limiter, that's exactly what it said to be doing.So, if you are telling me that a program called FSP_Limiter is not able to limit my framerate... could you please tell me what's the point of installing/using this program?Still,have a nice dayLuc BrusselmansBelgiumOh, and by the way, can you explain to me why the framecounter of fsp_limiter doesn't show up on screen? Or is this perhaps somthing my system cannot handle?

I asked this in another FPSLimiter thread, and got no reply, so I'll try here. Is Limiter only for DX9? When I run it, it has a little dropdown box to choose between D3D9, OGL, and D3D8. Nothing about DX10. thanks.

I asked this in another FPSLimiter thread, and got no reply, so I'll try here. Is Limiter only for DX9?

Yes, FPSLimiter won't work with DX10.

Thanks, Alex.

I wasn't shouting I was highlighting the comments, I should have used bold text rather than caps, sorry but I was in a rush and typing on a tiny netbook.To put it more simply if you have your settings too high then FPS limiter wont be able to function as well as it should, because the frame rate is fluctuating so vastly that it never actually gets chance to limit the frame rate properly. If you find a happy medium where your large frame rate spikes a few and far between then you will find that FPS Limiter will do a much better job and you will be much happier with the experience you get. This is why I went on to discuss PNW and GEX, in my opinion PNW isn't anywhere near as well optimised for draw calls per scenery cell as GEX Europe is for example and its the large difference between draw calls per cell that is causing the frame rate to spike massively downwards for a split second or so.

To all,I have read the previous (and then some more) threads about fps_limiter but I can't get it to work (I think)After the download, I unzipped the package to a temporary folder (outside Program Files) and I created a bat.file.Running this bat.file FsX starts so at least that part of the .bat is correct.However, when checking the frame counter, I notice that the frames bounce up and down between 25 and 41, even with fps_limiter on 30. The second indication is that no counter is displayed on screen, even if I enabled the counter in the GUI of fps_limiter.So now I wonder what could be wrong...?any suggestions?Luc BrusselmansBelgium

I agree with UlfB on lowering your FPS lock in FSX. The surges you are seeing is a common issue for those with i7 cpu's. I find that a lock of 26 more or less takes care of it for me. I only need to use 25 or 26 when flying into HEAVY scenery areas like New York or places of the such. Everywhere else I can run 30 FPS locked but hit a BIG heacy hitting area and wham I get the surges you describe. I would set your FPS lock in FSX to 25 and set your TBM to 40 and see if that improves things. Granted it is not as smooth as 30 FPS (please lets not start a debate on that) but you will find a more consistant sim experience flying to and from those problem areas we all have.

I agree with UlfB on lowering your FPS lock in FSX. The surges you are seeing is a common issue for those with i7 cpu's. I find that a lock of 26 more or less takes care of it for me. I only need to use 25 or 26 when flying into HEAVY scenery areas like New York or places of the such. Everywhere else I can run 30 FPS locked but hit a BIG heacy hitting area and wham I get the surges you describe. I would set your FPS lock in FSX to 25 and set your TBM to 40 and see if that improves things. Granted it is not as smooth as 30 FPS (please lets not start a debate on that) but you will find a more consistant sim experience flying to and from those problem areas we all have.

That is absolutely true. Before yesterday, I had never seriously considered locking my framerate in FSX since it decreases my FPS by 10. However, instead of focusing on framerate I started to judge performance on overall smoothness. Even though my FPS are now locked at 25 and are generally lower than before, I have no surges anymore and I am enjoying FSX sooo much more than I used to! Now I don't even use FPSLimiter anymore :)

Hello again,or, maybe I should start with an 'I told you so that was something wrong...'Yesterday I backtracked my steps in installing fsp_limiter.When I first did so, the GUI applet didn't show up and I found that JAVA wasn't active on my system. In fact, it wasn't even installed so I downloaded it from their website.BUT, as I am on a 64bit OS, I downloaded and installed the 64bit version.After that the GUI showed alright so I thought (wrongly) that all was allright now.Well, it wasn't. the GUI created a batchfile alright and I could even start fsX but what it didn't do was put a limit on my framerates.I then installed, out of pure frustration, the 32bit version of Java and see....fsp_limiter now works as advertised. Framerates are kept at bay in the narrow band between 22 and 30 (locked at 25 as suggested by some of you). It's a very smooth ride now without spikes, surges or whatever we name it...I hope some of you can benefit from my frustration too... :( Luc BrusselmansBelgium