by NickN » Fri Mar 06, 2009 3:02 pm
This fix is working perfectly here. What I can see at this point is people on lesser hardware, or, those who are not tuning FSX correctly, or, those who have very high overhead such as i7 clocked on 285 cards, may not get any advantage with this because
a. A slow system lacks the overhead higher end systems have and with the higher resources better systems run they are not being properly governed by the application where the slower system never displayed the issue to begin with.
b. A very high end i7 clocked may or may not see advantage with this. I am seeing some positive and some neutral results. Because i7 clocked places a huge overhead on the system, moreso that DDR3 QX, using the frame lock in FSX may accomplish the same goal as this app. I am seeing scenery areas where the app does help with i7 and others where there is no difference.
c. A system which is not set up right for settings as outlined will be so out of balance with the hardware this will produce no result, or, a worse result.
This fix changes definitely the priority to autogen and terrain and appears it may throttle some threads through the Windows service csrss.exe.
Those on faster systems that have the overhead and are getting thread collisions.. this fix eliminates those. Those on slower system that do not have the overhead to begin with and their stutters are related to perf based on hardware limits, this will probably have none or little effect.
It is a YMMV situation.,, but at this point a far better tweak that anything I have come across in a very long time
Everyone should try this to see if it will upgrade their result. It does not harm or change any default files. The only time it is active is when FSX is booted by the produced BAT file
Everyone should try this to see if it will upgrade their result. It does not harm or change any default files. The only time it is active is when FSX is booted by the produced BAT file
What I did was place the framelimter app folder on my backup drive, created the BAT file.. made a shortcut of that BAT file which I sent to the desktop and then assigned the FSX.exe icon to that shortcut. I removed the original Microsoft Flight Simulator shortcut from the desktop and renamed my new one so it looks just like the original.
One must also remember, .. you can NOT start a flight from the flight folder until you have started FSX with the BAT file. After FSX has launched you can double click any flight and the tool will throttle the app correctly.
Last edited by
NickN on Fri Mar 06, 2009 3:15 pm, edited 1 time in total.