[fabianfred]

Ihave never had any problems on the Midway map...in my version I changed the layout of the quays...but still use some of those objects...my new computer rocks (DuoE6850/8800GTS).....but my old one was OK on the default map too (AthlonXP 2200+/GF MX440)

If you run large missions like on a SEOW campaign some maps have problems. Small missions on the trouble maps are ok. On some maps there seems to be a limit on amount of objects befora the leak will occur. How powerful your rig is has nothing to do with the memory leak. Our squad has machines of different setups. Couple have powerful rigs. Let me explain the effect.

On some maps with big missions this is what happens. The mission will load lets say Midway, 27 megs at the beggining. The memory will dump once to 25 megs. After that first dump it will steadily climb to 100 megs. At 90 megs you start to get stutters. 100 megs lockup. It is coded in the exe file for 100 megs. You find this by usining the GC command. It will take about 50 min to 75 min and it will lock everybody up.

There are maps you can run big missions on and lets say it starts at 30 megs it will stay for hours around 30 megs. Will never start creeping up to 100 meg lockup. That is how you can tell which maps have the memory leak that shows the memory creeping up to 100 megs.

My squad AG-51 we are a Pacific squad. We fly in the SEOW campaigns. This map is a dream come true and adding the San Jacinto carrier and it is a fantasy. So you see why we are very interested in this and are hopping we can run big missions in this big map.

I hope this will clarify the memory bug and what it does.

so how do you get to view what your memory is....what is the GC command?
and most of the single missions I make are huge and stutter on lesser machines