I noticed that flying near CYEG, frames were dropping while mem seemed to be increasing. Keeping it short, UT seemed to be calling for a effects file that was invalid. Once I renamed the HL917130B.bgl to *.xxx (within the UT Canada Scenery folder) the errors the dropped, and no more mem/fps issues in the area. The recomendation however was to rename all the hl files due to the way the coastlines are created.Anyways, you can read more about this here:http://www.simforums.com/forums/forum_posts.asp?TID=19466Allen has since made a patch that fixes this for UT USA, but he is still working on Canada & Europe. I believe you patch to FS9, then run the port again. Go to the support forum for the patch and the details.Just wanted to make sure that those of you who posted here stating your using UT, are aware of this issue - and the fix (kudos' again to Allen not only for a great product, but for his awesome support and speediness thereof ..)RegardsGarettEDIT: Here's the lnk to the patch post:http://www.simforums.com/forums/forum_posts.asp?TID=19685

Hi Robert,Remove any PoolSize entry from your fsx.cfg and see if the problem still occurs.the "lack of memory" message can also come from your graphic card memory that can't deal with the amount of data received from the scenery cache (poolsize)best regardsDavid

Hi all.When bug-hunting, you really need to restore FSX to it's default configuration... NO ADDONS or TWEAKS!Then look for the problem. If it no longer exists, then sytematically add your tweaks, then addons ( first terrain, then aircraft ).Some of the tweaks floating about are simply no good.. or will crash the sim. Some addons are suspicious. There is even evidence that DLLs like FSUIPC are conflicting with other addons. So strip the sim bare, and re-add in an organised manner.This approach is much better than simply assuming the problem is FSX or hardware. And just because someone thinks they have a similar problem doesn't really help. Start from scratch ( default ) and work towards the problem.Dick

Hello Robert:Being that bad BGL's and/or duplicate or corrupt afcad has already been mentioned, I would suggest monitoring CPU and GPU temperatures through a flight to see if they become suspect when the problem raises its head.For what it is worth, there was a program called "ScanAFD.exe" for FS9 that would identify and/or remove bad AFCAD files. I don't know if it will work in FSX or not but might be worth a consideration.Good luck:RTH

Adam Szofran told me it is possible for FSX to run out of memory, which sounds like what is happening to you. The 32 bit address space is just too limiting.Nobody that I have noticed has given results for lower settings. Do you still hit the FPS wall with lower settings? Have you tried autogen off?I understand this is not how you want to fly, but you should test these things to determine what the problem is.Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)N15802 KASH '73 Piper Cherokee Challenger 180

Hello,I have made the same bad experiences very often: the framerete drops down to 1-2 fps. On different computers with different processors and different grafic cards.That makes the sim absolutely unflyable. It occurs after a certain time. I can't relly tell, after how many minutes it happens.No addons, no modifications.Really frustrating isn't it ?Happy landingsArry

Wow, what a surprise. I go away for a few days and come back to see that my month-old thread has been resurrected. I guess it's that time of year.Thanks for all the new suggestions. Here's what's up with me. After lots of testing, swapping of RAM, etc., I determined that my CPU and GPU were running hot. I replaced my Intel fan/heatsink -which apparently was defective - and increased my exhaust fan speed and my temps are now in an acceptable range. This may have helped somewhat, but I can't be sure. Quite frankly, I just got tired of doing 4 hour flights under tightly controlled situations. There's a big FSX world out there and I got bored doing the same flight over and over again, each time changing a variable such as a scenery addon, display setting, cfg setting, etc. I do think the added cooling has helped, however, but I'm just not doing 4 hour flights under controlled conditions any more to know for sure - at least for the moment.What I'm now encountering most often is an eventual loss of panning after an hour or so in the VC and Spot View, both with and without Track IR. So rather than a full slowdown, it's just the panning that's affected to where it's too jerky to continue flying - although sometimes reducing altitude and preparing for landing will cause the problem to go away. But this problem isn't consistent and I can't always replicate it. And it never happens with the new Siai Marchetti.I tried the new MS Hot Fix suggestion and got an "unable to access memory" error that shut down the sim after about 45 minutes during my first flight after installation of the fix. I removed the fix and I've not encountered the error again even in 2 subsequent flights under identical conditions and using the same flight plan. One of these days I'll reinstall the fix and see if I encounter that error again with the same flight.In sum, I just couldn't seem to find a single cause for this framerate degradation. I think the overheating was a contributing factor, as the degradation no longer occurred as regularly as before the cooling fixes. I found that fiddling with the PoolSize appeared to make no difference, but I can't say for sure as my results were inconsistent from one flight to the next. Similarly, there was no consistency when I deactivated my landclass addons, AI Traffic, etc. So I'm sticking to relatively short flights of 1-2 hours and only encountering the panning problem on occasion. But for 18 of the last 24 hours I've flown nothing but the Siai Marchetti and had no problems at all on these short flights - except for the shutdown after installing the new Hot Fix referred to in this thread. Indeed, this plane seems to avoid even the blurries that I sometimes encounter with the slower default planes I've used for all my testing. The fact that some others are experiencing a similar kind of framerate degradation over an extended period of time suggests to me at least that FSX itself - or some cfg variable - is somehow responsible for what's happening. Why else should relatively high display settings work fine for 3-4 hours and then suddenly bring the machine down to a crawl? Alternatively, as noted in this thread, it may also be an XP/Intel dual core problem. Who knows? I just hope that Aces is looking into this.Thanks again for all the suggestions. Robert

Dunno...I still think it's a video memory runout problem..And... I don't think it's just the duo cores that do it. I can make my machine do that if I want to. All I have to dois turn up all the scenery sliders to the right, go to a bigairport like Miami, etc, and fly around for a while. If I do enough panning, view changes, etc, eventually mine will do that too. And I'm almost certain it's a memoryrunout problem. Mostly video. When this happens you will noticea few things. #1. The panel bmp reduces res, and gets blurrier.#2 The landclass does the same thing outside, and gets blurrier.#3 Panning becomes a painful procedure. #4 frame rates take a major dump. As long as I don't overdo the scenery sliders, this does not happen. With my normal "medium" scenery settins, I never see thishappen. I can fly all over the world for hours and hours at a timeand not get a glitch. I've already flown numerous overseas flightsin the jets. Nary a problem. But if I get greedy with the slidersin a big city, I'll get that too. So...My suggestion is to lowerthe settings a notch or two and see what happens. I think you arepushing too much video for the memory, etc you have. Eventuallythe sim runs outa gas.. When you go to 2 fps, stutter, lousy pan, trust me, you have run out of memory.BTW, my box is a single core P4 prescott at about 3.15 ghz and a128meg 9800 pro.. 1 gig ram. Nothing special at all..MK

@MK: Sorry MK, what you're describing is not the discussed problem.@Others: What Windows version do you use? I reinstalled my pc with XP Pro instead of XP Mce, and the problem appears to be gone.Marco.

I have just spotted this bumped thread and read through all the posts with interest. Whilst all of the suggestions around memory loss over time or overheating are well founded, I personally believe that there may be a fundamental memory handling issue in the software, that I suspect ACES are fully aware of and hopefully will fix in their reported planned patch sometime this month.....please ACES could you comment on this thread?My reason for stating this, is that I installed FSX, after Xmas, on a clean new harddrive, defragmented the drive after install, no other addons at all, I started the sim and - set all settings to low to medium only with all the known frame rate killers turned off/down. - Opened a FREE flight with the Caravan at London City active runway.- FPS 10-15 - not good but initially expected.- Decided to slew to the parking area.- FPS still OK- Thought I would try the Shift-F for the fuel-truck, which eventually appeared - nice touch.- I wasn't intending flying but just seeing what the sim looked like, so I went into Slew mode again and pressed 'Q' to gain a little height and whilst climbing to around 1000' used the pan in VC to look around. Graphics not great but eh - only my first tryout.- Then all of a sudden slideshow - 1-2 FPS, FPS display disapeared, no key-press would work, at least for 10-20 seconds when it would seem to recognise that I pressed a key - basically the software locked up.I have also noticed once, after minimising the FSX software, to access the desktop, and then restoring FSX that I suddenly received a memory address error in FSX.exe.Now I have not flown anywhere, other than for a few minutes, whilst trying various settings to try and find something optimum for my lower end hardware, and yet as the story above demonstrates, this FPS drop can still occur.Lets all hope that whatever patch ACES/MS may be considering will address many of these performance issues. ACES staff - Any comments would be welcome.Regards,StuartLow-med Hardware: AMD Athlon 2.6+, 2 Gb DDR RAM, FX5900XT 128RAM.

High there,Just to add some thoughts here.Been doing some of my own research and I'm getting the same issue also and guess what.It's a core 2 duo again 6600.The new top of the range AMD processors is the way to go for stutter free flying for anything over about 30 mins.RAM memory on my machine is 2GB and there's not much point in getting more than this.Video card should be Nvidia 7900/50 and with 512mb. ATI cards do not work well with FSX.I'm not sure if ACES studio will acknowledge this very obvious memory leak. Don't expect it to be fixed in a patch and don't expect Intell to acknowledge a fault either.Time will tell time will tell but my personal experience with ACES studio is that they are not very interested in what I've got to say. Ideas and input I had on the beta was pretty much ignored.

-

>High there,>>Just to add some thoughts here.>>Been doing some of my own research and I'm getting the same>issue also and guess what.>>It's a core 2 duo again 6600.>>The new top of the range AMD processors is the way to go for>stutter free flying for anything over about 30 mins.>>RAM memory on my machine is 2GB and there's not much point in>getting more than this.>>Video card should be Nvidia 7900/50 and with 512mb. ATI cards>do not work well with FSX.>>I'm not sure if ACES studio will acknowledge this very obvious>memory leak. Don't expect it to be fixed in a patch and don't>expect Intell to acknowledge a fault either.>>Time will tell time will tell but my personal experience with>ACES studio is that they are not very interested in what I've>got to say. Ideas and input I had on the beta was pretty much>ignored.Well for me I traced the problem to the BufferPools tweak! If I set it to any setting I get this same drop in performance stated here. I removed the BufferPool section from my fsx.cfg and never had the problem since. I just completed a transcontinental flight with no problems. I did this over a month ago, and haven't had the problem since. The downside, is Autogen will pop up closer to your aircraft then if you used the BufferPool tweak, but it's not too bad, and much better then having this FPS drop! My system is a Core 2 Duo E6700 2Gb system with ATI X1950 XTX Crossfire cards!

Same thing happens to me....well not quite 2FPS, but much much lower, like FPS are cut in half, so If I get 25, they will be about 10-15 in 1-2hrs, especially if I'm doing a lot of task switching (ie firefox, explorer etc)

Robert,My system is very similar to yours, and this happenned to me for the first time last night, while in a mission over Tokyo. Very strange.