August 3, 201114 yr I have been trying for the last 2 days to install the FPS limiter with no luck at all.Firstly, no matter what i do i cannot get Java (latest) to create a .bat file Secondly i have tried creating my own .bat file. Again no luck and i have tried every text string that has been sugested on this and many other forums. Still no luck so i am just about ready to give up. I would like to use the alternative FPS limiter but do not like the messing around every time i want to alt+enter (i use Radar contact & EzDok) to get around the black screen thing. Anyone got a tried and true method of creating a .bat file (i.e. A text string that works) or has had the same problem with java on w7x64 and knows how to fix it? Rick Hobbs
August 3, 201114 yr I had this problem before, but I found this great website with a tutorial on it. You need to place the entire contents of the download into the main FSX directory and create the .bat file from there. Make sure that you've put the correct file path for fsx.exe. Once you've done that, simply create the bat file and it should appear in the main FSX directory as "fsx.exe.limited". Just make sure you then use the bat file to start FSX. I'll try and dig out a link for you in the mean time as it had a few other tips on it. :) Edit - Found it: http://virtualfsx.wordpress.com/2011/07/05/unlimited-frames-external-frame-locking/ Calum Martin
August 3, 201114 yr make a .bat file called fsx.bat and put the following start C:\"my\path\FPS_Limiter_0.2\"FPS_Limiter.exe /r:D3D9 /f:30 /x:OFF /l:OFF "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Where the first part is the path to the fps limiter.
August 3, 201114 yr hmmm, when did a new version come out? Anything worth upgrading for? I tell you, between new hardware and finding this little gem, my FSX is REALLY smooth now, even at ultra-high levels. :) John Binner, MCDST U.S. Dept Of Veteran Affairs, Senior IT Analyst OI&T, SPM, Clinical Imaging 2022 Build: Thermaltake Core X71 Full tower case, ASUS Prime X570-P Motherboard, AMD Ryzen 7 5800X 8-Core CPU, ASUS TUF Gaming Radeon RX6900 XT GPU, G.SKILL Ripjaws 32GB DDR 3600 RAM, Thermaltake Toughpower GF1 850W 80+ Gold PSU, Cooler Master MasterLiquid ML240L Water Cooler
August 3, 201114 yr Try this; http://www.wikihow.c...te-a-Batch-File But remember to save as All Files type not TXT. Then manually add the .bat format at the end. Whereas if its in TXT format it gets saved as myfile.TXT.bat which is wrong.
August 3, 201114 yr Author Got the .bat file itself created, it's the text string that won't work. Donald, are the excamations and spaces to be included? Rick Hobbs
August 3, 201114 yr Author Take a look at the pinned thread in this forum started by Ryan on the Nvidia Inspector set up (Which also is not PMDG specific) and you will see this subject discussed in there.Just trying to get some help here, how about you? Edit: Forgot to post as 'Quote'. This post is in answer to 45_DME Rick Hobbs
August 3, 201114 yr I've done all the instructions. Googled hours for the answer on the error I get.Running the .bat gives me the error message (it's in Dutch, so I've to translate it):"cannot start application correctly (0xc000005). Click OK to quit the application" I've added the message in the attachment. I've got the strange idea that I'm the only one who got this specific error message.Help will be appreciated! Running W7 64b on a Dell XPS (i7, gt555m, 4GB) Goof vd Biggelaar g
August 3, 201114 yr Author I've done all the instructions. Googled hours for the answer on the error I get.Running the .bat gives me the error message (it's in Dutch, so I've to translate it):"cannot start application correctly (0xc000005). Click OK to quit the application" I've added the message in the attachment. I've got the strange idea that I'm the only one who got this specific error message.Help will be appreciated! Running W7 64b on a Dell XPS (i7, gt555m, 4GB) Goof vd Biggelaar I can't even get that far. The only way i can bring up the command prompt is to ceate my own .bat file. Then i get a 'cannot find path' message. If i try opening the .jar file i just get a mometary flash of the command prompt and then nothing. Rick Hobbs
August 3, 201114 yr Just use a different framerate limiter. There is a different FPS limiter called d3dantilag. It is much better than FPS Limiter 0.2 because it requires no .bat file, and FSX can be started normally. Here are the instructions that I posted in a different thread: Go to: http://www.kegetys.n..._antilag101.zip Once it's downloaded, Extract, Drop both files into your FSX main directory, Open up the antilag.cfg file, You should see two settings...set the input latency part of it to 0 and use the other part to set the framerate. (ie. 30, 40, whatever) Now you just start FSX and you're good to go. (For those who had the Limiter 0.2 where you have to run a batch file, you no longer have to use this method. Just abandon it, and start FSX normally.) Ethan Rayhorn My Office: (Taken at FL410)
August 3, 201114 yr Author Just use a different framerate limiter. There is a different FPS limiter called d3dantilag. It is much better than FPS Limiter 0.2 because it requires no .bat file, and FSX can be started normally. Here are the instructions that I posted in a different thread: Thanks Ethan. Yes i know about that one. Only thing is, you have to put up with a black screen every time you want to go to windowed mode when you fiddle with EzDok or when you start Radar contact. I have been waiting for a fix to come up on that one and then, yes it is a better limiter. Besides, i hate giving up on something when i know there,s an answer.Regards, Rick Hobbs
August 3, 201114 yr Author Run as admin or disabled UAC already Rick? Yup. You name it. The strange thing is that i had this installed on my previous build. Since i have upgraded to the 2600k and reinstalled my W7X64, first i had a problem installing Java untill found a locked directory. Since then i have taken over just about every directory i think i need to but still that .jar will not open. Rick Hobbs
Create an account or sign in to comment