FPS limiter bat file

[drewsaw2 3]

Thanks Paul, I'll give that a go and report back. By the way, I fixed the wild fps by doing another defrag and then restarting the computer

[Paul J 349]

Good! - every little bit helps..

[drewsaw2 3]

Oh, and I just checked my FIBER_FRAME_TIME_FRACTION value in the cfg and its currently set at 0.1

[Paul J 349]

p.r.o.b.a.b.l.y just a tad too low, but how FSX responds is dependent upon so many factors, let alone height and speed. You could have blurries flying a Cub, at 200 feet at 60 knots - over Seattle...

[drewsaw2 3]

The added FIBER_FRAME_TIME_FRACTION value made things much clearer. I notice a bit of a jump in frames, but the pesky stutters remain.

[drewsaw2 3]

Actually Paul, I have managed to trim many of the stutters I was getting in certain situations thanks to your suggestions and some experimenting of my own. locking frames at 40 seemed to help a little in areas with heavy autogen.Now I need to get outside and do something else

[cubs 2]

Y'know - I've been mulling this darned limiter over for a while now. It is a worthwhile mod, as it does make a difference to almost everyone's frame rate, by pushing the frame rate limit off to the operating system, thus freeing up fsx to "work on other stuff".. The problem everyone runs into, is that Java GUI. How to run it, where to put, and so on.. The truth is - you don't need the jar. You can just delete the darned thing and make the bat file manually - it's quite easy once you get away from the 'magic' of Java.. Bare with me - I'm mainly making this for the guys that think they can't do this, or that it's too hard, but the fact is that there are hundreds of posts all from folks having trouble understanding this thing - including me. I must have downloaded 20 different versions of Java, trying to get it to work. And then the problem with Microsoft's "Where do I put the quotation marks?" "Why only one quotation mark?" - all pretty confusing. What I'm outlining below is what I found to be a more straight-forward way of getting it running.Basically - it's put the files in the FSX root, make a batch file on the desktop, name it, and then run it. The parameters in the file are fairly well known by now, and are in the readme.txt, but this is the part we can make a lot more simple by stating where FSX actually is with the dos "SET PATH=" command, instead of making error upon error because of those squirrely quotation marks.So... if you are still having issues making it run, try this.. 1). Make a new folder on your favorite "stuff" drive - not your fsx drive, and name it anything you want to, say "FPS_Limiter_Source_File. Put the zip file into it.2). Unzip the file inside that new folder.3). You will now have another new folder there called "FPS_Limiter_02".4). Inside that folder are seven files:- ......FPS_Limiter.exe......FPS_Limiter_GUI.jar......HookHelper.dll......Limiter_D3D8.dll......Limiter_D3D9.dll......Limiter_OGL.dll......Readme.txt 5). Copy everything inside the folder - except the readme and the jar files - over to the root folder of FSX. Now forget about that folder.6). Now leave Windows Explorer and then Rt-Clk anywhere on the desktop. Select 'New -> Text document'7). Rt-Clk on the icon and select "Edit"8). Notepad will open: Copy/paste the dos script below from between the two asterisk rows "*******" (don't copy the asterisks) into Notepad and then substitute your path to your FSX folder from what mine was. So... highlighting everything from CLS all the way to \fsx.exe..... ************CLS@ECHO OFFSET PATHF=F:\Flight SimulatorF:CD "%PATHF%"start .\FPS_Limiter.exe /r:D3D9 /f:30 /x:OFF /l:OFF "%PATHF%"\fsx.exe************ For example your path might read:- SET PATHX=C:\Flight Simulator C:CD "%PATHX%"start .\FPS_Limiter.exe /r:D3D9 /f:30 /x:OFF /l:OFF "%PATHX%"\fsx.exe It might be: SET PATHX=C:\FSXC:CD "%PATHX%"start .\FPS_Limiter.exe /r:D3D9 /f:30 /x:OFF /l:OFF "%PATHX%"\fsx.exe What we've done is to substitute a parameter (PATHX) for the path to your FSX folder - a lot more simple than trying to figure where to put a quotation mark.. Once you're happy that everything looks good, spaces in the right spot, etc., click on 'save as' and name it "Limiter.bat"... or anything else, as long as it ends with ".bat".Lastly - open up your fsx.cfg and edit the [Display] section - and make UPPER_FRAMERATE_LIMIT=0. If you docant find or don't know how to manually do this, just start FSX as you normally do, and move the frame rate to 'unlimited, then exit fsx.Double-click on this batch file and FSX will start, and will be limited tp 30 frames per sec.. This will work every time. If you are using TripleHead2G - then make "/f:90" for the 3 screens. Also, too, note the "start" command - Following "start" is a space, and then a "." before the "\". If you copy\paste you won't have any trouble. I'm a retired old fart, so you can pm me if it's still as cloudy as before. At least you won't have to worry about java.....

Thanks for the info, I followed your procedure and changed the text to read : CLS @ECHO OFF SET PATHX=C:/FSX C: start./FPS_Limiter.exe/r:D3D9/f:30/x:OFF/I:OFF"%PATHX"/fsx.exe I have the Limiter.bat on my desk top and the other files are in the root folder of FSX. When I double click the Limiter.bat file on the desk top, it just opens. Should'nt FSX start? Doug

[Paul J 349]

Hi Doug: you need to CD into the "%PATHX%" CD "%PATHX%" and then and then put spaces in the command line.... start .\FPS_Limiter.exe /r:D3D9 /f:30 /x:OFF /I:OFF "%PATHX"\fsx.exe Also the Windows OS needs back slashes ( \ ) for its' %PATHX% separator. Note where I've changed yours, and then put a single space in the spots where I've left a large one - ok?

[joshleeman 0]

Y'know - I've been mulling this darned limiter over for a while now. It is a worthwhile mod, as it does make a difference to almost everyone's frame rate, by pushing the frame rate limit off to the operating system, thus freeing up fsx to "work on other stuff".. The problem everyone runs into, is that Java GUI. How to run it, where to put, and so on.. The truth is - you don't need the jar. You can just delete the darned thing and make the bat file manually - it's quite easy once you get away from the 'magic' of Java.. Bare with me - I'm mainly making this for the guys that think they can't do this, or that it's too hard, but the fact is that there are hundreds of posts all from folks having trouble understanding this thing - including me. I must have downloaded 20 different versions of Java, trying to get it to work. And then the problem with Microsoft's "Where do I put the quotation marks?" "Why only one quotation mark?" - all pretty confusing.What I'm outlining below is what I found to be a more straight-forward way of getting it running.Basically - it's put the files in the FSX root, make a batch file on the desktop, name it, and then run it. The parameters in the file are fairly well known by now, and are in the readme.txt, but this is the part we can make a lot more simple by stating where FSX actually is with the dos "SET PATH=" command, instead of making error upon error because of those squirrely quotation marks.So... if you are still having issues making it run, try this..1). Make a new folder on your favorite "stuff" drive - not your fsx drive, and name it anything you want to, say "FPS_Limiter_Source_File. Put the zip file into it.2). Unzip the file inside that new folder.3). You will now have another new folder there called "FPS_Limiter_02".4). Inside that folder are seven files:-......FPS_Limiter.exe......FPS_Limiter_GUI.jar......HookHelper.dll......Limiter_D3D8.dll......Limiter_D3D9.dll......Limiter_OGL.dll......Readme.txt5). Copy everything inside the folder - except the readme and the jar files - over to the root folder of FSX. Now forget about that folder.6). Now leave Windows Explorer and then Rt-Clk anywhere on the desktop. Select 'New -> Text document'7). Rt-Clk on the icon and select "Edit"8). Notepad will open: Copy/paste the dos script below from between the two asterisk rows "*******" (don't copy the asterisks) into Notepad and then substitute your path to your FSX folder from what mine was.So... highlighting everything from CLS all the way to fsx.exe.....************CLS@ECHO OFFSET PATHF=F:Flight SimulatorF:CD "%PATHF%"start .FPS_Limiter.exe /r:D3D9 /f:30 /x:OFF /l:OFF "%PATHF%"fsx.exe************For example your path might read:-SET PATHX=C:Flight Simulator C:CD "%PATHX%"start .FPS_Limiter.exe /r:D3D9 /f:30 /x:OFF /l:OFF "%PATHX%"fsx.exeIt might be:SET PATHX=C:FSXC:CD "%PATHX%"start .FPS_Limiter.exe /r:D3D9 /f:30 /x:OFF /l:OFF "%PATHX%"fsx.exeWhat we've done is to substitute a parameter (PATHX) for the path to your FSX folder - a lot more simple than trying to figure where to put a quotation mark..Once you're happy that everything looks good, spaces in the right spot, etc., click on 'save as' and name it "Limiter.bat"... or anything else, as long as it ends with ".bat".Lastly - open up your fsx.cfg and edit the [Display] section - and make UPPER_FRAMERATE_LIMIT=0. If you docant find or don't know how to manually do this, just start FSX as you normally do, and move the frame rate to 'unlimited, then exit fsx.Double-click on this batch file and FSX will start, and will be limited tp 30 frames per sec..This will work every time. If you are using TripleHead2G - then make "/f:90" for the 3 screens. Also, too, note the "start" command - Following "start" is a space, and then a "." before the "". If you copypaste you won't have any trouble.I'm a retired old fart, so you can pm me if it's still as cloudy as before. At least you won't have to worry about java.....

Im a bit confused with the 2 examples of what my path might be compared to the text Im supposed to copy? Because what i copy is pathf and examples are pathx? Could you show what it looks like if my fsx path is C:Usersjosh"default fsx destination" please? Thanks

[Paul J 349]

The path variable is simply any name that you want to make up, Josh.. It can be PATHY, PATHP, PATHJOSH or even PATHPJ.If you did SET PATHJOSH=C:Usersjosh"default fsx destination, then any time you want to copy something to or from C:Usersjosh"default fsx destination - you would simply say copy whatever "%PATHJOSH%", and it would be copied to C:Usersjosh"default fsx destination.Now - a word of caution as you are quoting C:Usersjosh"default fsx destination as your FSX location. Don't use the default if you're using Windows 7, because it will put FSX in the C:|Program files (x86), and you will have all kinds of grief when you install or delete addons.

[joshleeman 0]

The path variable is simply any name that you want to make up, Josh.. It can be PATHY, PATHP, PATHJOSH or even PATHPJ.If you did SET PATHJOSH=C:Usersjosh"default fsx destination, then any time you want to copy something to or from C:Usersjosh"default fsx destination - you would simply say copy whatever "%PATHJOSH%", and it would be copied to C:Usersjosh"default fsx destination.Now - a word of caution as you are quoting C:Usersjosh"default fsx destination as your FSX location. Don't use the default if you're using Windows 7, because it will put FSX in the C:|Program files (x86), and you will have all kinds of grief when you install or delete addons.

So if my fsx is in win7 default location (unfortunatly it is) my batch file should read like this correct...CLS@ECHO OFFSET PATHC=C:Program Files (x86)Microsoft GamesMicrosoft Flight Simulator XC:CD "%PATHC%"start . FPS_Limiter.exe /r:D3D9 /f:30 /x:OFF "%PATHC%"fsx.exeAnd the CLS is supposed to be off-center 1 space from the rest, because thats how it pasted? Any other errors? And this can be kept on desktop and double click it to start sim with limiter? Thanksedit-CLS didnt off-center on my post but when pasted the "L" lines up with first letter of all lower lines correct?

[joshleeman 0]

It still wont open fsx. It gives me the same error. cmnd promp opens sais starting, then error

[Paul J 349]

Open a cmd window, then copy/paste,SET PATHC=C:Program Files (x86)Microsoft GamesMicrosoft Flight Simulator X ..............hitting the Enter key after it - then type inecho "%PATHC%"........................It should return the path to your fsx.exe. If it doesn't - then you have a syntax error.Do you have TeamSpeak on your PC?

[joshleeman 0]

Open a cmd window, then copy/paste,SET PATHC=C:Program Files (x86)Microsoft GamesMicrosoft Flight Simulator X ..............hitting the Enter key after it - then type inecho "%PATHC%"........................It should return the path to your fsx.exe. If it doesn't - then you have a syntax error.Do you have TeamSpeak on your PC?

I will get it if thats a convenient way to comm. with you because I'm very bad with computers LOL. When I looked teamspeak up there were a few different choices, which one should I download and install?

[Jim Robinson 122]

"%PATHX%"fsx.exe should actually be "%PATHX%fsx.exe" (note the quote moved to the end of path and filename)."%PATHX%"fsx.exe effectively means: "C:Program Files (x86)Microsoft GamesMicrosoft Flight Simulator X"fsx.exe"%PATHX%fsx.exe" means "C:Program Files (x86)Microsoft GamesMicrosoft Flight Simulator Xfsx.exe", which is what you want I think.Jim