loading time

[GOPHUR]

Steady I think this is a memory leak. Martini is looking at it.

Can you check the program usage before you spawn each time and see if it is going up?

[clone9cz]

After multiple long load times:

First the Loading screen turn black then.

No more background screen after despawn.

After trying to spawn on another mission the game crashed.

Workaround

Use system performance monitoring to count ww2.exe Virtual Memory and restart WWIIOL at treshold 1.7-1.8GB VM.

100% reduced clinet CTD on my system since 2005-6.

[imded]

Well, lets see.

1. getting into the 1st page of game (side lock delay)
   
2. enter the world delay (spawn delay) and sometimes you have to hit this button several times before getting to next page at a lost of 10-15+ seconds each time you hit button.
   
3. 'Did you know' page delay from 10 seconds to 75 seconds with a 30%+ chance of CTD.
   

Sounds like a lot of built in time delay here.

If #3 is allways here, then why do we have a SD due to overpop. I sure

hope that #3 is taken into account for overpop before adding additional time to it.

So lets add up the possible times with only using #2 and #3.

Max hitting enter world button (x3) of about 45 seconds and then having to wait (without CTD) for the DID YOU KNOW page of 75 seconds. we have 120 seconds.

Now, taking this into account during an overpop situation, we should take the average of the 120 seconds and say typically takes 60-75 seconds. Hope this is adjusted to the overpop time as it is built in default time.

Thanks guys for you great work @ CRS.

[petie]

Well' date=' lets see.

1. getting into the 1st page of game (side lock delay)

2. enter the world delay (spawn delay) and sometimes you have to hit this button several times before getting to next page at a lost of 10-15+ seconds each time you hit button.

3. 'Did you know' page delay from 10 seconds to 75 seconds with a 30%+ chance of CTD.

Sounds like a lot of built in time delay here.

If #3 is allways here, then why do we have a SD due to overpop. I sure

hope that #3 is taken into account for overpop before adding additional time to it.

So lets add up the possible times with only using #2 and #3.

Max hitting enter world button (x3) of about 45 seconds and then having to wait (without CTD) for the DID YOU KNOW page of 75 seconds. we have 120 seconds.

Now, taking this into account during an overpop situation, we should take the average of the 120 seconds and say typically takes 60-75 seconds. Hope this is adjusted to the overpop time as it is built in default time.

Thanks guys for you great work @ CRS.

This shouldnt count towards spawn delay

Because both sides suffer it

So say side A has 60 sec SD

And ot is removed because of 60 sec load screen

Then underpop side also has this 60 sec losd screen so means there is NO Spawn delay

[elegance]

1.35 still suffering from this? Cause getting a CTD (after a 20sec+ loading time) when changing towns (on 4th or 5th change) is getting really old really quick. Respawning in the same town is without problems. No delay and no CTDs.

[petie]

Im gonna do some testing

A - Log in game - spawn North side of map (measure time taken)

B - Spawn down south if map ( measure time taken)

C - Reboot game - spawn south ( measure time taken)

I think C maybe quicker B

[ohanselo]

every one of my squad members can link the spawn in to atleast 1 or 2 CTD's

[dotsie]

3 to 4 CTDs a session. The further away from a battle you change the longer it takes. The longer you are logged the more likely a CTD seems. Especially common when spawning air because you respawn far from where you died.

Old already.