I've recently been getting a stuttering problem with my FS, everything fine until about 90mins - 2 hrs into flight, when everything slowly slows down until it's unusable. Are you experiencing this? Check if you have FS Passengers installed. I de installed the demo and now everything works fine, just completed a Manchester - Montego Bay for 9 hrs stutter free! It may be the criminal here. FYI.Horgy

Hi there - interesting post. I've had a very similar problem. The developer of FSP accepts that the use of the 'mini report' can produce low frame rates with certain video cards so the answer may be simply not to use this report.However, for me, that was not the issue as it turned out. It was more of a memory leak-type condition. Dan stated quite categorically that because of the way his .dll was programmed, it could not produce a leak. Interestingly, he did also say that his file could possibly interact with some other .dll file, which was not similarly programmed, and produce a leak. Today, I did a cull of my .dll files, finding that some I no longer needed anyway. Sure enough my 'memory leak' disappeared. It would seem that the culprit in my case was one of the .dll files which had ditched.Bud

What did you use to cull your .dlls?

I simply looked at the list of .dll files in the module folder and removed all which were not M/S originals. I then put back those I needed currently and which I knew [or suspected] were OK. That left about 5 or six modules which I ditched. I have to believe that one of these files was creating my problem because it disappeared after that little exercise.Bud

Thanks for sharing, Bud. Probably I'll try to do the same.

>I simply looked at the list of .dll files in the module>folder and removed all which were not M/S originals. I then>put back those I needed currently and which I knew [or>suspected] were OK. That left about 5 or six modules which I>ditched. I have to believe that one of these files was>creating my problem because it disappeared after that little>exercise.>>BudBud, how did you knonw which belonged to what add-ons? How did those undwanted get there? Interesting, could you please post what is left in your module folder now (if it's not too intimate) along with the list of the add-ons you're using. Would be a good example to follow. Thanks for the new direction.

Hello DirkI have a great deal of confidence in the programming skill of the developer of FSPassengers and am as certain as I can be in the wild and whacky world of 'putes and their various systems that FSP is not the cause of the problem originally reported.FsP does not allocate any dynamic memory during a flight so a memory leak is simply impossible. Dan has indicated that FsP may disturb another third party DLL which could cause a leak if the author used an absolute address instead of a relative address (which, apparently, is a common programming fault).For this reason I had a careful look at my module folder.It isn't difficult to find which DLLs belong where. The title is usually enough, or a quick look at the properties gives enough info to make a choice. My module folder now contains only the original M/S DLLs, plus Act Camera, Aerocore (Aerosoft scenery),Flight 1 (ATR),FSPassengers,FSUIPC,Key2Mouse,and Wideserver.In total, I removed ten DLLs for add-ons I no longer use, or have stopped using for the purposes of this exercise.Bud

Thank you very much, Bud. I'm adding this thread to my FS9 Tweaks folder.