There have been a number of questions on how to configure AlacrityPC to work properly with FPSlimiter and FSX. I figured out how to make it work and am sharing it with the community. After making a profile in AlacrityPC for FSX it is easy to add the single configuration line to make everything work as it should. Go to your FPSlimiter folder and you will see the batch file that calls up FPSlimiter and FSX called fsx.exe.limited.bat. Right click on the .bat file and select edit from the menu. This opens the batch file so you can see the contents. It is a simple code that looks something like this, start D:\"FSX\FPS_Limiter v2\"FPS_Limiter.exe /r:D3D9 /f:24 /x:OFF /l:OFF "D:\FSX\fsx.exe This is the code that you will use to configure AlacrityPC. Open your FSX Profile in Alacrity and go to the Autostart tab. Here you will write your Program File Path. Type in the path to FPSlimiter, example; "D:\"FSX\FPS_Limiter v2\"FPS_Limiter.exe" now be sure to remove all quotation marks or it won't work. In the next line labled "Command Line Arguments" you type in the remainder of the .bat file code example: r:D3D9 /f:24 /x:OFF /l:OFF "D:\FSX\fsx.exe again making sure to remove the quotation marks or it won't work. The third and last thing to do is select a "Type" from the pull down menu on the third line and select "Monitored" Lastly save your work and everything should work properly. Mine works perfectly now and if you put a shortcut on your desktop it is simple to use. My computer is a dual core with WinXP 32bit and the operating system won't use all of the RAM on the system so this gets rid of a lot of used memory that can now be used by FSX especially if you have a large amount of video ram. I noticee a major improvement in visuals and stutters using this combination. Enjoy, fisheye

There have been a number of questions on how to configure AlacrityPC to work properly with FPSlimiter and FSX. I figured out how to make it work and am sharing it with the community. After making a profile in AlacrityPC for FSX it is easy to add the single configuration line to make everything work as it should. Go to your FPSlimiter folder and you will see the batch file that calls up FPSlimiter and FSX called fsx.exe.limited.bat. Right click on the .bat file and select edit from the menu. This opens the batch file so you can see the contents. It is a simple code that looks something like this, start D:\"FSX\FPS_Limiter v2\"FPS_Limiter.exe /r:D3D9 /f:24 /x:OFF /l:OFF "D:\FSX\fsx.exe This is the code that you will use to configure AlacrityPC. Open your FSX Profile in Alacrity and go to the Autostart tab. Here you will write your Program File Path. Type in the path to FPSlimiter, example; "D:\"FSX\FPS_Limiter v2\"FPS_Limiter.exe" now be sure to remove all quotation marks or it won't work. In the next line labled "Command Line Arguments" you type in the remainder of the .bat file code example: r:D3D9 /f:24 /x:OFF /l:OFF "D:\FSX\fsx.exe again making sure to remove the quotation marks or it won't work. The third and last thing to do is select a "Type" from the pull down menu on the third line and select "Monitored" Lastly save your work and everything should work properly. Mine works perfectly now and if you put a shortcut on your desktop it is simple to use. My computer is a dual core with WinXP 32bit and the operating system won't use all of the RAM on the system so this gets rid of a lot of used memory that can now be used by FSX especially if you have a large amount of video ram. I noticee a major improvement in visuals and stutters using this combination. Enjoy, fisheye

I must have not attached the .jpg image intended so trying again. fisheye

Great job Fisheye, thanks very much for sharing!

 Thanks, fisheye.  I tried your approach but unfortunately I could not get it to work for some reason.  I did remove the quotation marks like you said, but Alacrity would not start up FSX (even though it did start the FPS_Limiter.exe with the command line inserted).  I am still able to use it with FPS Limiter, however, using another workaround.  I run an ancillary program, Voice Activated Commands (which is excellent, by the way), as the "monitored" program and then direct Alacrity to start the actual fsx.exe.limited.bat as a "program to start after."  The only downside is that I have to manually close the FPS Limiter dialogue box when I am done with FSX, but this is a relatively minor inconvenience.Major V

I had the same result as Major, although I do appreciate the effort to help. I take a similar tactic in that I use Fraps as the monitored program and then just manually launch the FPS limiter.

If you point the program to be monitored at the .bat file, you have no need to insert the Command Line arguments. When pointing to the program to be monitored ensure you click the down arrow and select 'All Files' instead of the default '.exe files'. Then you can select the .bat file and you are finished.

 Thanks, fisheye.  I tried your approach but unfortunately I could not get it to work for some reason.  I did remove the quotation marks like you said, but Alacrity would not start up FSX (even though it did start the FPS_Limiter.exe with the command line inserted).  I am still able to use it with FPS Limiter, however, using another workaround.  I run an ancillary program, Voice Activated Commands (which is excellent, by the way), as the "monitored" program and then direct Alacrity to start the actual fsx.exe.limited.bat as a "program to start after."  The only downside is that I have to manually close the FPS Limiter dialogue box when I am done with FSX, but this is a relatively minor inconvenience.Major V

I probably didn’t write up the instructions as well as could be done but I will try to clear up a couple of things here. First of all you will have to create your .bat file in FPSlimiter before you do anything at all and I was assuming that had already been done by those interested in this tweek. My .bat file was used in the example so you will have to substitute your information for mine. I have my FPSLimiter folder on my “D” drive in my FSX folder. I also noticed that in the explaination text that I left off the slash mark before the second line of code. However if you look at the picture you will see the slash mark there. I am not sure what Scottmm73 is talking about pointing to the .bat file but my way works for me. I did not mention because it happens in FPSlimiter anyway was that you have to press any key after shutting down FSX to close FPSlimiter being it is the monitored program in order to have the AlacrityPC restart process start. I am including my AlacrityPC configuration box and the code for your information. Notice that you break the .bat file code in the middle and put half on the top line and the rest on the second line but don’t forget to remove the quotation marks!!My .bat filestart D:\"FSX\FPS_Limiter v2\"FPS_Limiter.exe /r:D3D9 /f:24 /x:OFF /l:OFF "D:\FSX\fsx.exeupper line code;D:\ FSX\FPS_Limiter v2\FPS_Limiter.exeSecond line code;/r:D3D9 /f:24 /x:OFF /l:OFF D:\FSX\fsx.exeBe sure to pick “monitored” in the pull down boxNotice; keep the code all the same spacing as in the original .bat file only delete the quotation marks. The code in the second line can be changed at the /f:24 to another number and it will change the ‘frames per second’ the limiter will use…hope this helps those having trouble. fisheye

That's exactly how I set mine up, and while fsp_limiter starts, it bails out immediately and everything restarts.

Thank you fisheye for getting me pointed in the right direction ! :( Anyone who is having issues with an immediate restart - if you are not using fisheye's FSX location (I an not either), you have to convert any long file names pointing to FSX to 8.3 format. I have FSX in my D:\ drive, running Win7-64, so fo me I had to convert D:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe into D:\Progra~2\Micros~1\Micros~1\FSX.exe and voila. Also helped me to get some batch files to set my power.cfg and turn off (then on) Security Essentials.Wish I had installed to D:\FSX back when, but do not want to go through a re-install (at least not yet).Joeedit - I was origianlly looking at just the forums and threads on batch files where it was stated to use drive\path\file, but sure enough the 8.3 file names is listed in the on-line manual :(

Doh! That did not occur to me. Thanks for the tip, and to the original poster for the help.