I downloaded the FPS_Limiter_2.0 (the one recommended by venetubo) in my attempts to speed up FSX and ran FSX through the BAT file, but I did not notice a performance increase, the FPS was not limited to my specified value of 24 (and yes, I had the FSX limit at Unlimited), and my aircraft textures were a little messed up. Could somebody who has used this please either provide instructions or tell me what I might be doing wrong?

Thanks,
boeing247

Don't get that wrong, but that thing isn't meant to speed up things but to limit and even out some.
It limits the system load by remaining at the given value instead of going 100+ fps over water or less dense areas.
It evens out the sometimes huge fps differences when looking around, on the airport (with low fps then) and then away from it (with high fps).

That's the purpose of the thing, no speed gained, only stability in the simultaneous usage with some (famous) tweaks as they sometimes may overload the system in "too high" fps situations where your CPU "overruns" the GPU.
The famous tweaks remove or shorten the buffer between those two instances, so the fps limit prevents too high loads then which otherwise could lead to a CTD.

Running FSX in unlimed fps mode (speaking of that internal limiter) always includes the downside to end up in blurry textures here and there, more or less severely depending on the load on the actual system in use.

So it evens things out rather than speeds things up, but it still increases performance (so say people who have used it). Anyway, I can't get it to work period. When I pause, causing the fps to go up, I'm getting frame rates over 24. Also, my aircraft textures get screwed up. Do you know hot to fix this?

I could think of a more fluent impression because of the equalized framerate, yes. At least, that's my impression when using such things. Take KSFO. Looking at the airport drives the frames down, looking over the water really goes to unlimited. So if they all stay at e. g. 25, you are getting a nicer experience, maybe smoother.

I've read some reports that it doesn't work for some people (means "doesn't limit anything"), but you're the first one reporting about mixed up planes then.
From my knowledge, this can't be related to the limiter since, by design, he only catches on the frames, nothing more.
Well, they've posted another one over at Avsim, working without that bat file. That's the one I'm using and I'm happy so far. http://forum.avsim.net/topic/322993-alternative-external-fps-limiter/

Maybe it helps.  :-/

Thanks. I set the FPS limit in the .cfg file to 24. What do I then set the FPS limit to in FSX?
Oh, I assume that the "game executable directory" is the main FSX folder? (forgive the question, I just want to be sure  ;))

Set the FSX internal limit to unlimited. The folder assumption of yours is correct.  :)
Does it work then?

I just tried it, and it does not work. In addition, my ground textures are horrible.  :-/

If they get better when setting the FSX internal limit to a fixed value of e. g. 25, the "unlimited" setting is the culprit there.
You could only help the PC with defragmenting the disc and try some lower settings, so his workload includes more of the texture processing when set to "unlimited". With this setting you actually tell him to drop any optics for the winning of fps, so he just does like he should, in a way.

Now the trick is to find an external framelimit which still allows him to take enough time on textures while staying on "unlimited" on the internal limiter of FSX.
Sounds weird, but he actually is faster when his internal limit is set to unlimited, so you want to avoid any other setting there and go with an external limiter then.

Yeah. You don't happen to know of any other limiters, do you?

Only those two, sorry. Normally, they should work one way or the other. I haven't read the whole Avsim thread regarding the newer one, maybe some error sources are named there.  :-/

If you only use the internal FSX limiter together with the tweaks, you'll lose some overall fps, but your textures should be fine. Maybe this solution works for you then.
The drop is noticeable but you still should be ok on the fps most of the times and using this internal limiter will always make sure that textures come in sharp.

There was a guy running this together with some other tweak, fiber frame time fraction (FFFT) set to 0. That was very smooth and fast, but caused huge blurry areas in some scenarios while being overwhelming good in others. I never got that working in any situation though.
http://forums1.avsim.net/topic/283565-fftf0-tweak-against-fps-drop/
As you see, the tweak aspect always is a game of tradeoffs.