No Jim; we want the Path to the folder that contains the file - not to the file itself. If we want to call something else in that folder from within that same batch file we can do that by just referring to that path variable. A path is just an alias: nothing else.Below is part of my batch process for starting FSX any single piston-engined aircraft, such as the A2A Cub, etc.:-SET PATHC=C:UserspjAppDataRoamingMicrosoftFSXSET PATHF=F:Flight Simulator...menu goes here...@ECHO OFF:SINGLE_PISTONC:CD "%PATHC%"del fsx.cfgdel .ControlsStandard.XMLcopy .ControlsStandard_.XML .ControlsStandard.XML /Y 2>&1 1> NUL:copy .ConfigsSingle_Piston.cfg fsx.cfg /Y 2>&1 1> NUL:CD "%PATHF%"call "%PATHF%"fsx.exeECHO.ECHO Hit Enter to copy back the config file...PAUSE 2>&1 1> NUL:C:CD "%PATHC%"copy fsx.cfg .ConfigsSingle_Piston.cfg /yCLSGOTO MENUIf I use the Limiter - I put the line :-start .FPS_Limiter.exe /r:D3D9 /f:90 /x:OFF /l:OFF "%PATHF%"fsx.exeso that the call to fsx starts the limiter first, then fsx, reads:-CD "%PATHF%"start .FPS_Limiter.exe /r:D3D9 /f:90 /x:OFF /l:OFF "%PATHF%"fsx.exe ECHO.I am using 4 or 5 USB controllers which are part of a (hardware) modular cockpit that I am slowly building; I use different control xml files for some controls and use FSUIPC for other pieces. I could probably use FSUIPC for all of the controllers, but, honestly - I find it a tough read, a long process, and have difficulty in getting it to consistently recognize an active control, then switch to the calibrate mode and then be able to set the range without messing up - so I call different xml files. For me it's easy.@ Josh: Go here for Teamspeak, download it, set it up, using the OrbX settings, then pm me - OK?http://www.orbxsyste...-password-info/

Paul, I think it works in this case because there are no spaces in "fsx.exe", however here's a hypothetical example using a file in the same folder that does have a space, and that syntax will generate an "access denied" error:set fsxpath=C:Microsoft GamesMicrosoft Flight Simulator XNotepad "%fsxpath%"Phone Activation.xmlOn the oher hand, moving the quote to the end of the line as below does not generate an error and simply opens Phone Activation.xml in Notepad (not that you wanted to open Phone Activation.xml in notepad, I'm just using it as an example because it's one of the few files in the FSX folder that has a space in the filename):set fsxpath=C:Microsoft GamesMicrosoft Flight Simulator XNotepad "%fsxpath%Phone Activation.xml"...that's all I'm saying. The quotes aren't even required if there were no spaces in either the path or filename. Great idea with the menu choices for swapping out the controls xml and stuff prior to starting the sim, BTW. I had a similar thing going with FS9 that would swap out the fs9.cfg prior to starting the sim. Haven't made it that far in FSX yet, I've only been an FSX user for about 3 months now :) .BTw, where can I get a copy of this FPS limiter thingy? I'd like to give it a try.Thanks,Jim

Can FPS limited actually IMPROVE fps?! I thought it just held it steady? I should try getting it working if that is the case.

Found it, got it working, maybe picked up a frame over seattle, but it seems to be at the expense of blurry ground textures, so I guess it's not a keeper for me. BTW, I see where the misplaced quote comes from; with a quote on the end of FPS_Limiter.exe" the dumb thing throws an invalid switch error. Oh well...Jim

No Jim; we want the Path to the folder that contains the file - not to the file itself. If we want to call something else in that folder from within that same batch file we can do that by just referring to that path variable. A path is just an alias: nothing else.Below is part of my batch process for starting FSX any single piston-engined aircraft, such as the A2A Cub, etc.:-SET PATHC=C:UserspjAppDataRoamingMicrosoftFSXSET PATHF=F:Flight Simulator...menu goes here...@ECHO OFF:SINGLE_PISTONC:CD "%PATHC%"del fsx.cfgdel .ControlsStandard.XMLcopy .ControlsStandard_.XML .ControlsStandard.XML /Y 2>&1 1> NUL:copy .ConfigsSingle_Piston.cfg fsx.cfg /Y 2>&1 1> NUL:CD "%PATHF%"call "%PATHF%"fsx.exeECHO.ECHO Hit Enter to copy back the config file...PAUSE 2>&1 1> NUL:C:CD "%PATHC%"copy fsx.cfg .ConfigsSingle_Piston.cfg /yCLSGOTO MENUIf I use the Limiter - I put the line :-start .FPS_Limiter.exe /r:D3D9 /f:90 /x:OFF /l:OFF "%PATHF%"fsx.exeso that the call to fsx starts the limiter first, then fsx, reads:-CD "%PATHF%"start .FPS_Limiter.exe /r:D3D9 /f:90 /x:OFF /l:OFF "%PATHF%"fsx.exe ECHO.I am using 4 or 5 USB controllers which are part of a (hardware) modular cockpit that I am slowly building; I use different control xml files for some controls and use FSUIPC for other pieces. I could probably use FSUIPC for all of the controllers, but, honestly - I find it a tough read, a long process, and have difficulty in getting it to consistently recognize an active control, then switch to the calibrate mode and then be able to set the range without messing up - so I call different xml files. For me it's easy.@ Josh: Go here for Teamspeak, download it, set it up, using the OrbX settings, then pm me - OK?http://www.orbxsyste...-password-info/

ok i downloaded the teamspeak from the link u gave and its a rar folder with a bunch of stuff in it. I'll be on all morning so when u get this could u either email me [email protected] or quote my post so I get an email that way and Ill respond. I havnt installed anything cus I dont know what file in that rar to use or whatever. I made an account at that orbx site if u wanna use that chat box if its easier just get in touch. Thanks so much!!

No Jim; we want the Path to the folder that contains the file - not to the file itself. If we want to call something else in that folder from within that same batch file we can do that by just referring to that path variable. A path is just an alias: nothing else.Below is part of my batch process for starting FSX any single piston-engined aircraft, such as the A2A Cub, etc.:-SET PATHC=C:UserspjAppDataRoamingMicrosoftFSXSET PATHF=F:Flight Simulator...menu goes here...@ECHO OFF:SINGLE_PISTONC:CD "%PATHC%"del fsx.cfgdel .ControlsStandard.XMLcopy .ControlsStandard_.XML .ControlsStandard.XML /Y 2>&1 1> NUL:copy .ConfigsSingle_Piston.cfg fsx.cfg /Y 2>&1 1> NUL:CD "%PATHF%"call "%PATHF%"fsx.exeECHO.ECHO Hit Enter to copy back the config file...PAUSE 2>&1 1> NUL:C:CD "%PATHC%"copy fsx.cfg .ConfigsSingle_Piston.cfg /yCLSGOTO MENUIf I use the Limiter - I put the line :-start .FPS_Limiter.exe /r:D3D9 /f:90 /x:OFF /l:OFF "%PATHF%"fsx.exeso that the call to fsx starts the limiter first, then fsx, reads:-CD "%PATHF%"start .FPS_Limiter.exe /r:D3D9 /f:90 /x:OFF /l:OFF "%PATHF%"fsx.exe ECHO.I am using 4 or 5 USB controllers which are part of a (hardware) modular cockpit that I am slowly building; I use different control xml files for some controls and use FSUIPC for other pieces. I could probably use FSUIPC for all of the controllers, but, honestly - I find it a tough read, a long process, and have difficulty in getting it to consistently recognize an active control, then switch to the calibrate mode and then be able to set the range without messing up - so I call different xml files. For me it's easy.@ Josh: Go here for Teamspeak, download it, set it up, using the OrbX settings, then pm me - OK?http://www.orbxsyste...-password-info/

this is getting rediculous now, ive reinstalled from x86 to CFSX and same thing except now i get send info to microsoft with same error. I try it on a vista pc and use this exact quote of your batch and if the .bat is on destop it opens my desktop folder. If its in the fsx folder it opens the fsx folder. this makes no sense at all what the fawk im about to "install" this laptop into my wall at a high rate of speed!!! It makes no sense the only thing thats the same from these two laptops is there both dell.

Now its even more odd...using the java gui to make the batch file on the vista pc with fsx in the default (x86) folder it worked fine? Even more crazy is the two .bat files the gui makes for me are identical on both computers except the C:FSX on my win7 and the C:default x86 on the vista machine, so its gotta be the computer. Same install method and gui method with same .bat but one works one doesnt. What could be causing this? Can someone who knows about computers check out the full error log I posted on the "external fps limiter gives this error" thread. Im going nuts for 5 days now with this damn limiter. Thanks!!!

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 OFF SET PATHF=F:Flight Simulator F: 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:FSX C: 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 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.....

PaulI am totally lost trying to get fps limiter to work and I'm not sure on how to setup my path? My fsx is on a seperate drive F: so is this path correct?%PATHXSET PATHX=f:FSX SET PATHF=F:Flight Simulator F:CD %PATHF% start .FPS_Limiter.exe /r:D3D9 /f:30 /x:OFF /l:OFF "%PATHF%"fsx.exeIf this correct then I will move on to the next step.Don

How do u guys close fsx when using this, because when I exit flight the normal way, fsx crashes and all the stuff I did or changed isnt there after reboot? Do I close the limiters cmnd promp first or what?

Don - all we need is the path to fsx.exe. Find fsx.exe in Windows Explorer, then look in the long thin address window at the top - that is your path, and if you rt-click on it you will be given an option to copy this address as text. Chosse that option, then paste it into your script.I can't tell from your posted line whether it's correct or not - you have it all on the same line.

%PATHXSET PATHX=f:FSX SET PATHF=F:Flight Simulator F:CD %PATHF% start .FPS_Limiter.exe /r:D3D9 /f:30 /x:OFF /l:OFF "%PATHF%"fsx.exe

Open up a Windows Explorer window: go to the place that you have downloaded the FPS_Limiter_02.zip or .rar to. Unpack the zip/rar file: highlight and copy these files into the root folder of FSX:-FPS_Limiter.exeLimiter_D3D9.dllHookHelper.dllRt-click anywhere on the blue desktop. Click on "New". Select "Text document". Name it "Start FSX.bat". Rt-click on the new icon. Select "Edit".If your fsx.exe is in "F:Flight Simulator" - simply copy/paste this:-@ECHO OFFCLSSET PATHF=F:Flight SimulatorF:CD "%PATHF%"start .FPS_Limiter.exe /r:D3D9.dll /f:30 /x:OFF /l:OFF "%PATHF%"fsx.exePAUSEEXIT... then save it. When you double-click on this icon - the bat file will find your fsx path, then it will find the FPS_Limiter.exe, run it, and then start fsx.You have to know exactly where fsx is - ok?

@ Josh;-There might be a different issue with fsx crashing as you exit the program (maybe EZCA?)but - put a "pause" on another line after the "start -blah-blah" line, and then an "exit" on a second line after that, per the example above. Providing there are no other problems with fsx quitting - when you quit FSX - the FPS_Limiter.exe will give you a "Press a key to quit" message. At this time fsx has fully stopped, and is unloaded.The bat file itself will then give you the opportunity to "Press any key to continue" - which will cause it to close the cmd window.

Don - all we need is the path to fsx.exe. Find fsx.exe in Windows Explorer, then look in the long thin address window at the top - that is your path, and if you rt-click on it you will be given an option to copy this address as text. Chosse that option, then paste it into your script.I can't tell from your posted line whether it's correct or not - you have it all on the same line.Open up a Windows Explorer window: go to the place that you have downloaded the FPS_Limiter_02.zip or .rar to. Unpack the zip/rar file: highlight and copy these files into the root folder of FSX:-FPS_Limiter.exeLimiter_D3D9.dllHookHelper.dllRt-click anywhere on the blue desktop. Click on "New". Select "Text document". Name it "Start FSX.bat". Rt-click on the new icon. Select "Edit".If your fsx.exe is in "F:Flight Simulator" - simply copy/paste this:-@ECHO OFFCLSSET PATHF=F:Flight SimulatorF:CD "%PATHF%"start .FPS_Limiter.exe /r:D3D9.dll /f:30 /x:OFF /l:OFF "%PATHF%"fsx.exePAUSEEXIT... then save it. When you double-click on this icon - the bat file will find your fsx path, then it will find the FPS_Limiter.exe, run it, and then start fsx.You have to know exactly where fsx is - ok?

Okay I got it to start but see pic? What are the two black boxes for? Also I normally I use ASE weather programand to start fsx , so how will I be able to get my weather now?http://

WOW! Success! Well done Don!Somewhere on your desktop is the ASE icon. Simply double-click on that before you start fsx. I would give that a minute or so before launching fsx, too, as it uses a lot of pc resources when it starts the first time. If you want to get more sophisticated - we can do that, too, but get it all going first.

OK - that little bat file - to start ASE automatically - as you did with finding the path to fsx.exe - find the path to ASE_Exec.exe and add it as below. It is probaby identical to mine, so you can put it in exactly as here:-@ECHO OFFCLSSET PATHF=F:\Flight SimulatorC:CD C:\Program Files (x86)\HiFi\ASEstart .\ASE_Exec.exeF:CD "%PATHF%"start .\FPS_Limiter.exe /r:D3D9.dll /f:30 /x:OFF /l:OFF "%PATHF%"\fsx.exePAUSEEXIT

PaulI'm not sure how to edit that .bat file I created, cause I rt click on it and it started fsx up? Also my ASE is in the same path as yours. Thanks