Stutters? Give this a try

 

 

 

This was introduced in another forum

Credit goes to Gizmo and Noel for bringing to our attention

 

This may be one of the all-time best tweaks to use however at this point testing is limited to a small number of users


Download this tool


http://rapidshare.com/files/205205148/FPS_Limiter_0.2.rar

or from here

http://files.filefront.com/FPS+Limiter+02rar/;13233637;/fileinfo.html


Unrar/unzip

Be aware that where you place the folder must remain or it will break its use and you will need to reconfigure the bat file

USE:

Run FPS_Limiter_GUI.jar and click SEARCH EXECUTABLE

browse for and select FSX.exe

set frame limit to 30 under MAXIMUM FPS

Click CREATE BAT

Once complete close the interface and use the created file fsx.exe.limited.bat to start FSX (double click it)

set frame lock to UNLIMTED in FSX and use the AG slider to tune


You MUST have JAVA installed to use that interface

http://www.java.com/en/



Now here is the deal...  this attacks the UNLIMITED FRAME LOCK problem related to Vsync introduced by Aces in SP1/SP2. Instead of tuning the FRAME LOCK you will tune the AUTOGEN slider for smooth results where you are flying. Leave the FSX frame lock slider at UNLIMITED at all times.

You can fine tune this app as well...

 I found 30 was the sweet spot for all occasions. I would suggest no less than 24 and no more than 30 but start with 30.




FSX must always be started by clicking the created command line BAT file.. NOT the FSX desktop icon



See if this has a positive effect... especially you i7 people

and try this WITHOUT the affinity mask setting in the config file (It wont be there if you did not add the affinity mask line)

 

There is no need to change ANYTHING else. You must make sure to start FSX with the BAT file and not the desktop shortcut

Tune using the autogen slider.. do not change frame lock.. leave it at unlimited

 

 

The issue this tool attacks is the one introduced with SP1/SP2 whereby Vsync creates HI/LOW stammer in the frame rate. Using this tool as posted will allow the full priority of UNLIMITED to the application by the hardware but governs the frame rate stammer.

 

 

 

There is no new startup exe

It just locates the FEX.exe file and my instructions said:

 

There is no need to change ANYTHING else.

 

 

This fix is working perfectly here. What I can see at this point is people on lesser hardware, or, those who are not tuning FSX correctly, or, those who have very high overhead such as i7 clocked on 285 cards, may not get any advantage with this because

a. A slow system lacks the overhead higher end systems have and with the higher resources better systems run they are not being properly governed by the application where the slower system never displayed the issue to begin with.

b. A very high end i7 clocked may or may not see advantage with this. I am seeing some positive and some neutral results. Because i7 clocked places a huge overhead on the system, moreso that DDR3 QX, using the frame lock in FSX may accomplish the same goal as this app. I am seeing scenery areas where the app does help with i7 and others where there is no difference.

c. A system which is not set up right for settings as outlined will be so out of balance with the hardware this will produce no result, or, a worse result.


This fix changes definitely the priority to autogen and terrain and appears it may throttle some threads through the Windows service csrss.exe.

Those on faster systems that have the overhead and are getting thread collisions.. this fix eliminates those. Those on slower system that do not have the overhead to begin with and their stutters are related to perf based on hardware limits, this will probably have none or little effect.


It is a YMMV situation.,, but at this point a far better tweak than anything I have come across in a very long time



Everyone should try this to see if it will upgrade their result. It does not harm or change any default files. The only time it is active is when FSX is booted by the produced BAT file

 

 Everyone should try this to see if it will upgrade their result. It does not harm or change any default files. The only time it is active is when FSX is booted by the produced BAT file

What I did was place the framelimter app folder on my backup drive, created the BAT file.. made a shortcut of that BAT file which I sent to the desktop and then assigned the FSX.exe icon to that shortcut. I removed the original Microsoft Flight Simulator shortcut from the desktop and renamed my new one so it looks just like the original.

One must also remember, .. you can NOT start a flight from the flight folder until you have started FSX with the BAT file. After FSX has launched you can double click any flight and the tool will throttle the app correctly.

 

 

 

 

 

 

 

I do not think so.. this must address FSX.exe and not a go-between shortcut

 

 

D39

 

strange about inserting another line. I run XPx64 and see no issue like that. I wonder if it is UAC related

 

 

 

 

I think your first batch line is wrong

 

it should read..

start C:\"Program Files (x86)\Microsoft Games\FSX FPS LIMITER\"FPS_Limiter.exe /r:D3D9 /f:30 /x:ON /l:OFF "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Enabled or Disabled UAC still has a hold on the program files folder with Vista. That is why it is always best to install FSX outside of any program files folder and on its own drive.

Having a bit of trouble with this.  My FSX is loctated in a seperate drive so the download and installed in this drive.

The path shows  start D:\"D FSX\"FPS_Limiter.exe /r:D3D9 /f:30 /x:OFF /l:OFF "D:\D FSX\fsx.exe

I double click the bat file, it just flashes up then disppears and FSX does not start up.

What am I doing wrong?

When I open FSX thru the FPS program a little DOS like popup box opens and stays open I s this normal and does it need remain open?

I've given this a try in a number of different scenarios on my system; GEX/UTX, FTX, VFR London X, Photo Scenery.

It seems fine with GEX/UTX and FTX, but it was causing me stuttering issues with VFR London X and Photo Scenery. Adjusting the autogen slider helped somewhat, but it wasn't as good as without this fix.

North Texas

You are indeed correct.  FPS Limiter is not starting with my modification above.

I even tried:
pushd C:\Program Files (x86)\Microsoft Games\FSX FPS LIMITER
start C:\"Program Files (x86)\Microsoft Games\FSX FPS LIMITER\"FPS_Limiter.exe /r:D3D9 /f:30 /x:ON /l:OFF "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

This opens FSX fine but FPS Limiter is not running.

I also tried a "run" command running "fsx.exe.limited.bat" - this opens FSX fine but again FPS Limiter is not running

Any solution would be appreciated as I do not want to move FSX to another disk at this point in time.
Regards
PeterH

 

 

Thats not always true...

 

If you are set to UNLIMITED in FSX and the frame counter remains at 30 in a low scenery area.. you know it is working.

I have booted the sim several times and not seen the OSD come up even though it is working fine and I have the ON switch set in the command line.

 

 

Well I have now got the .bat file to work, but with the frame counter set to unlimited the frames go past the 30 mark?

I have the same issue. I set at 30 or 28, and I still see FPS jumping to 50 and 60, averaging well over 30. Less than without the limiter in place, but still not averaging the setting.

GTX9800+, nhancer, XP, and FSX set up to the guidelines here, including VSYNC.

Joe

Not that I am aware off?

Cheers Nick,

Will go back to DX9

 

I have a similar problem - under Vista 32 I cannot get this program to work!

The bat file that the FPS Limiter creates doesnot start FSX, unless I insert a new line as Phase mentions in a post above. But then the FPS Limiter doesnot limit ... anything (even starting it with  Run as Adminitrator).

Can someone with Vista that is able to run this program give some hints?

Thanks

Edmundo

NickN

Did you ever get F11, F12 and F10 to work in FPS Limiter?
I have tried this in both a Vista based and a WinXP based FSX but they both show views as per normal. Does the OSD button do anything?

I have installed FPS Limiter both under WINXP and Vista 64 (running as administrator), I have NOT edited the fsx.cfg to give AVGE frame rates but under both OS's I see FPS rates above 30.

This seems to work in Vista 64 showing the same cmd screen as that seen in WINXP:
pushd C:\Program Files (x86)\Microsoft Games\FSX FPS LIMITER
start C:\"Program Files (x86)\Microsoft Games\FSX FPS LIMITER\"FPS_Limiter.exe /r:D3D9 /f:30 /x:ON /l:OFF "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe  (RUN as administrator).

I have also applied this DWORD edit in the registry without seeing any changes in FPS LIMITER and FSX:
HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System
ConsentPromptBehaviorAdmin" = dword:00000000 (default is 00000002.)
I believe that this totally bypassess the UAC interface.

I'm still not sure that this program is actually working!!
PeterH

I downloaded the file and all I have is a file "FPS_Limiter_0.2.rar".No instructions or zip file.I tried from both locations and get the same.Is this correct?Thanks,Ron

I have Winzip but this is not a zip file.I click on it and it says  "Cannot open file,etc."What am I doing wrong?Thanks,Ron

Thanks,I downloaded the winrar program and got to creating the batch file which showed up as per Nick's instructions but when I double click I get the error message cannot find the file etc.Now I am not sure how to get my winzip program going again.When I try to unzip a file it is using Winrar.I have an old Winzip program that I have been using forever and it works good for what I do. Email rpowers46@yahoo.com.Thanks for the help.Ron

My OS is XP Pro with SP3.  I downloaded FPS Limiter and extracted the FPS Limiter in the folder C:\Program Files\FPS Limiter.  I downloaded JAVA and installed it.  I ran the FPS_Limiter_GUI, directed it to fsx.exe which is in D:\Program Files\Microsoft Games\Microsoft Flight Simulator X\fsx.exe and created the batch file fsx.exe.limited which resides in the same file as the FPS Limiter.  I also set the max FPS at 30.  The FPS slider is also set to limited within FSX.

I click on the batch file to start FSX, however, when running in sparse scenery the fps is well above 30 fps so it is not locking at 30.

Any suggestions to get this to work?  Am I doing something wrong?

Mike

A bit of feedback on my experience with FPS_Limiter.

 Installation went fine; however when FPS_Limiter gen'd the .bat file, it mis-parsed and placed the ' " ' quotes in the wrong places in the command line so I had to manually tweak that. Secondly, I found that my in-flight fps was almost always exactly half of what the command line FPS was set at.  For example, I had the command line FPS parameter set at 30, and in-flight fps was 15.  Ditto at 28/14, 24/12.  I did test at 35, and got about 18.  Not sure why it's taking that much off the in-flight fps...I wasnt expecting that.  Adjusting the auto-gen slider didn't make that much of a difference.

Another interesting effect I saw was that my stuttering actually increased.  Almost exactly every 1 second, it would have a short pause, then resume with a slight jump ahead.  Quite annoying actually and difficult to fly with.  Am going to try some experiments to see if I can shake out what may be causing this.  I don't have this when flying without fps_limiter.  Would love to hear any ideas......

------------------------------------------
AMD 64x2 5000+ OC 2.8
4GB DDR2
BFG 9800GTX+ OC
Vista 64