[Stanger]

Sorry to say, but things arent that simple

You need to take in account the:

- hardware (processor, vidcard, ram)
- software (windows version, service packs, drivers, hd fragmentation)
- graphical settings of the game
- the specific mission which was used to test

In my opinion with fast hardware (core2duo, geforce 8000 series card) you wont have any "memory leaks" at all, so we should rather use the term "optimizing for slower hardware"

I hear what you are saying. I have a core2duo with vidcard 7950 and 4 megs of ram. Others in my squad have better machines and everybody is locking up. There are maps that definate and consistently perform well. I am trying to figure out why.

[Vpmedia]

Ok, this changes things a bit.
I dont have experience with core2duo machines and Il-2 but you shouldnt have problems on any map.
Then we shouldnt use the term "optimizing for slower pc"

If you could pls take a look at the Burma/Imphal and Norway/Banf bases and tell me if there's the same problem then I can probably improve the fps on the Midway map too, as I did with the two above mentioned maps.

[Stanger]

Vpmedia thanks. Lets keep in touch and I will keep you inform. Due to work schedule I will be able to go hard at this all day Wednesday. Thanks for the info. I am talking about the campaigns that SEOW uses so we are talking about a lot of flyers and objects in campaigns. So optimising for FPS would be great.

[Stanger]

Ok have a update. It seems it is the docks that are causing the problem. Even if one piece is left it still errors out. I had to remove all of them and Midway has two sets of docks. So it seems it is not a collision problem. Now next step is to test and see if the memory performs better.

[spud]

Yeah, I found the same thing. A single object makes the error, and they make the console error if they are on the map but not touching. It's the objects themselves.

[lowfighter]

Hey, could you please tell me how this memory leak manifests? What is the memory leak? :?

[spud]

Apparently some maps lock everyone up online after some time period. All the maps that do so exhibit errors in the console when you first load the map.

Load a map, pull up console, and if you see those errors that look like this in the console:
##### House without collision (3do/Buildings/Port/BaseSegment/live.sim
##### House without collision (3do/Buildings/Port/Floor/live.sim
##### House without collision (3do/Buildings/Port/BaseSmallSegment/live.sim

the map will eventually lock up.

I've never seen it, but these guys fly in groups all the time and see it a lot.

[Stanger]

Yes small missions will not lockup. Gonna do different missions to see if can pin down. Doing more testing. After 40 minutes last Saturday our campaign mission locked up for everybody. About 20 players were in there. Some got this message.

[fabianfred]

I get that message and lock-up sometimes...when I try to take a screenshot during a very big and complicated mission....never thought if it was map related or not....?

[lowfighter]

Thanks for explanation. It's a very long time since I quit online, but I do remember seeing those error messages on console, didn't pay attention to them.
Stanger, you say if it's a small mission, the map will not lock up. Just remembered that I got sometimes the same memory error offline. It always happened when the mission was EXTREMELY heavy. I remember having one involving maybe 100 tanks, about same number of vehicles, a lot of artillery, flak, maybe 20-30 aircraft. It would lock whenever I run it and about the same time during the mission maybe about 10 minutes after start. Not sure, how heavy are those missions you get lock up?

Edit: I see Fred has seen it same way as me...

[spud]

Someone who plays with perfect maps (no console errors) with a bunch of people should drop some quay objects on the map (in map edit mode) and then see if they lock up.

[Stanger]

Yes and do not forget the GC command in console to get the memory that is left in game.

If you use Shift tab then you us capital GC. I you use the chat you use >GC.

[Stanger]

Here is a snippet from the SEOW forum.

BS8th_Bulau wrote:
I entered >GC into chat at 2 minute and 1 minute intervals. Memory total reported as follows:
...
0:13 94.5mb
0:14 94.1mb

A few seconds later, the game locked up.

A tell-tale sign of the stupid memory bug in IL-2. The limit is at 96 MB (even if your PC has 4 GB). Over 90MB, you may already experience strange lagging, pulsed warping, as the underlying JVM is desperately trying to free any garbage memory, anticipating a total congestion coming on.

Normally maps use 25-50, or with heavy object population 60-70MB. But larger and more detailed maps definitely use more memory, event with same number of objects, than small ones.

There is a temporary workaround for 4.08, but I reported this bug to the dev team, so may I kindly ask you to test the same with 4.09 beta patch? The result would be interesting for many of us.

or this:

I've had a chance to do a little testing of this. I've copied our big mission onto the Prokhorovka, Smolensk, and Moscow1 maps. The only editing I did was to make sure all the aircraft takeoff and landing waypoints were at an airbase.

Prokhorovka easily ran for an hour, starting out at 41.5 megs, and never rising higher than 47.2 megs total memory. At one hour, this mission is essentially winding down, and I saw no reason to continue any longer test.

Smolensk also ran for an hour without even working up a sweat, starting at 39.4 megs, and reaching a high of 40.8 megs, finishing the hour at 39.0 megs.

Moscow1 has not been run for the hour duration at this time. I started it, and checked memory use immediately, finding it to be using 40.2 megs. I expect that it would play out similarly to the foregoing two maps, and last the hour without incident.

As per the request from Zoli, I tested the original mission on the Ostfriesland map, using the latest 4.09 beta patch. In two attempts, it seemed to fare even worse than 4.08, starting at 73 megs, and lasting only 10 minutes before locking up, using a little over 88 megs at that point.

[fabianfred]

I have never looked at any console....but even with my old computer i always liked to run HUGE missions...and have never had the game crash or lock up...apart from as I posted above...trying to take a screen shot...... and years ago too....when trying to save a track file...before they bought out that fix patch which cause the saving of Tracks to be much quicker....that was before the NTRK came out

my HUGE missions are Pearl harbor on the Hawaii map...with more than 180 planes

a huge tank battle on the Smolensk map

and a huge ground attack on the Berlin map...... Bridgehead....see downloads

[letku]

I've got this memory leak problem in DCG several times when it spawns more aircraft on some maps.

Murmansk is one and was it NE Europe (online2?? don't remember the right name for it :?: ) it had a long straight canal in it.
You could fly about 10-15min and then they would lock up in online of offline.

Lowering the amount of planes helps just for a bit longer flying time and then it locks up again.
In DCG i had about 32-40 planes per side at start +some spawning planes later (4 to 12) and maybe about 100 vehicles on ground.

There's a lot of error messages in console when it happens.Doesn't il2 record those lines in some error.logfile or am i wrong? Can't check it myself as i'm at work now.


Also seen this in SEOW too a couple times happen in Murmansk,Normandy and on a Pacific map.