Brigade shift = Ctd

[bobstav]

Enough.

For 2 months now, every single time i shift brigade, i have an extremely long spawning period, we are talking 3-5 minutes. And usually, like 60 % of the time, i ctd after having sat there looking at my screen waiting to spawn. If you care, send me an e-mail once this is fixed. If not, oh well.

[Nick]

I think this is the number 1 most annoying bug for me right now, it's quicker to shut the game down and reload it!

[dotsie]

10 CTDs a night with this maybe. Its seriously starting to get on my nerves. I mean SERIOUSLY.

[jackalx]

I have the exact same thing, since the last month its really annoying .

[wiffy]

Same here. Not 10 per night, but enough to cause me to just log off after a few times. I've talked 2 previous players and 1 new player into subbing and playing with me after being away for awhile. All of us experience CTD's often when spawning in... after a long delay. Very frustrating.

[GOPHUR]

I don't think i8t has anything to do with changing brigades. I'm going to bet you are a pilot and after a long flight your virtual memory is full.

To test this, before you spawn, alt-tab to the desktop and bring up the task manager. If ww2.exe is getting close to 1.7GB of memory it is going to crash next time you load new terrain.

Martini never could find the culprit here and it doesn't seem to happen on all of our test machines. The only cure for now is to restart the game if you've been flying a lot and are planning a change in location that will load new map areas.

[bigrow]

I don't think i8t has anything to do with changing brigades. I'm going to bet you are a pilot and after a long flight your virtual memory is full.

To test this, before you spawn, alt-tab to the desktop and bring up the task manager. If ww2.exe is getting close to 1.7GB of memory it is going to crash next time you load new terrain.

Martini never could find the culprit here and it doesn't seem to happen on all of our test machines. The only cure for now is to restart the game if you've been flying a lot and are planning a change in location that will load new map areas.

I don't fly but it happens to me and alot of my squad.

I find this a bit odd though;

1. First spawn is north edge of map 3-5 secs spawn in time.

2. Second spawn in same location 1-2 secs spawn in time.

3. Third spawn is south 10+ secs spawn in time.

4. Fourth spawn is south again 1-2 secs.

5. Fifth spawn is back to original north location, spawn time is 20+ secs.

So, if the original location info is being stored when it shouldn't, hence slowing subsequent spawns at different locations, why does it take so long to go back to the original location again? I ask the question because i am interested in the answer, but also i have read very little rat feedback on this issue, and although you say martini was unable to find the problem, a couple of your posts(since 1.34) suggest to me that the problem, and the the way it often shows itself, isn't fully appreciated. Forgive me if i'm wrong, but when i take my car to be fixed, even though he knows more about cars than i do, i like to make sure the mechanic has full knowledge of any issues to save his time/help him find the cause.

[bobstav]

actually I dont fly at all, tried that, found the ground from above too fast , too often

I spend my time ingame playing infantry only. Usually i am one on the allied side that reacts to new ews instantly, which as you can guess, my ctd's taken into consideration, is not going very well at the moment. Most of the time nowadays, the axis will get a 4-10 minutes headstart on me, depending on spawn wait upon bdeshift, eventual ctd, and if so, another gamereload/choose side/Choose bde/ make new mission/ spawn in/ try to locate that engine i wanted to locate 10 minutes ago, but unfortunately now, while i was going through all my procedures (which by the way never happened to me until last 2 months)the axis now have setup already and are inbound and im suddenly not locating anything but some bullets flying toward me. This ctd cr.p is giving the attackers yet another advantage in their setups, and tbh, im not playing anymore until it is fixed. I love your game, but this is affecting my gameplay to the point, where i dont really care much anymore.

[dotsie]

I don't think i8t has anything to do with changing brigades. I'm going to bet you are a pilot and after a long flight your virtual memory is full.

To test this, before you spawn, alt-tab to the desktop and bring up the task manager. If ww2.exe is getting close to 1.7GB of memory it is going to crash next time you load new terrain.

Martini never could find the culprit here and it doesn't seem to happen on all of our test machines. The only cure for now is to restart the game if you've been flying a lot and are planning a change in location that will load new map areas.

This is not a solution Gophur. Every time you die while flying you have to move a long distance back to spawn AF and reload terrain. If you RTB its not a problem but who RTBs every flight. Everyone is complaining about this. Its badly affecting flying.

Also why has this become such a problem since last update? I cant remember 2 minute waits and CTDs before.

Edited September 12, 2012 by dotsie