[Stanger]

Was there ever any data on the midway map minus thee quay objects?

That was it for problems with the Slot, and they are easy to select and delete if there is indeed a problem.

I can not find anything conclusive from my testing yet on the Midway map. I was deleting different objects and testing and amount of objects too. Ships seem to be heavy on memory. I do have a exe file that raises the 100 meg limit to one gig. All that does is pronlong the effect for many hours. I can test the slot with a very big mission like you would have for a SEOW campaign with 24 people to check it out.

As oon as I am sure what it is I will let you know. The new Italy map seems to be memory bug free. Our squad campaigns have no ill effect on that map and memory keeps getting dump on that map.

[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)

[Stanger]

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.

[FA_Cheech]

December 1943 aerial photo of Sesapi Motor Torpedo Boat (MTB) base, Tulagi - courtesy of PT Boats Inc.


Sesapi MTB base, on The Slot - note floating dry dock caissons
Some fine tuning remains, but you get the idea 8)

[Neil Lowe]

Spot on Skunk

Cheers, Neil

[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

[spud]

Nicely done.

A buddy of mine's dad was a SeaBee (officer) who worked on PT bases in the SWPA. I'll have to show him next time he comes over for a beer.

[Stanger]

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

In console hit GC capital GC enter.
You will get how much memory is being used. 100 megs is maxed. Its the memory number on the left. you can watch your memory while a mission is going on. I use coop and sit in plane and hit GC every 5 min and watch if memory used is going up or remaining level.

[6S.Maraz]

[...]

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.

[...]

As far as I know, Rnzoli discovered the reason of the memory leak and found a solution (or a work-around) for that.

I cannot say anything else, you should contact him if you want to know something more.

Maraz

[Stanger]

[...]

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.

[...]

As far as I know, Rnzoli discovered the reason of the memory leak and found a solution (or a work-around) for that.

I cannot say anything else, you should contact him if you want to know something more.

Maraz

Yes he is a nice fellow. We were emailing back and forth on this issue.

[MrOblongo]

FIX NEW GUINEA!!
Remove the airbases not existing in 1942 and add Kokoda airstrip .

which are the wrong bases???

give me co-ords and I can delete them...any pix of Kokoda?

Sent u a PM...

[Shepherd]

Top shelf work on that MTB...and the rest of this map too for that matter. 8)

[rollnloop]

As far as I know, Rnzoli discovered the reason of the memory leak and found a solution (or a work-around) for that.

I cannot say anything else, you should contact him if you want to know something more.

Maraz

Where can i find this Rnzoli please, i am very intersted in a solution, having the same problem

[Stanger]

As far as I know, Rnzoli discovered the reason of the memory leak and found a solution (or a work-around) for that.

I cannot say anything else, you should contact him if you want to know something more.

Maraz

Where can i find this Rnzoli please, i am very intersted in a solution, having the same problem

A reason was not found what starts it, just a work around. P.M. me for a work around.

[Stanger]

This is great stuff. Love the detail you are putting in the maps. To take actual photos and make a copy is great. Thanks all for the hard work.