1.34.8.7 - Long Flight Test

[coda]

On the beta server.

P38 lifted Seclin, flew to Monchen, flew into aaa and let myself get shot down. Respawning took [much] longer than normal, but didn't crash. Same mission, took off again, flew to Lille (or closest Axis AF) and let aaa shot me down. Respawn was instant. No CTD.

Lifted 110 Gilze, flew to Antwerp, let myself get shot down, very long load time. Lifted Gilze 110 again, flew past Antwerp and back, respawn instantly. No CTD's.

During all flights had resource monitor up. Game was loading/unloading memory and using a consistent 1.39 to 1.41 Gb. However, when re-spawning after crashing a long way away from origin, re-spawning peaked to 1.7 then dropped back down to 1.4 after loading.

After paying attention to this for a while, my best guess. If you are at your spawn point location and respawn, you're terrain is already loaded, so you respawn right away.

When you change your area, you unload the terrain where you are and reload the new area. That would explain the extra time.

I didn't CTD on the beta server, difference is I usually only CTD when spawning into a heavily populated area, ground or air. So I'm guessing the loading/unloading/reloading of new terrain combined with rendering the people/units/positions etc. in the heavily populated areas are causing CTD's? AT least that's what happens for me.

Also noted that when flying with squaddies, when many of them report CTD's while flying along, it's usually when they enter a heavily populated area.

No way to test this on the beta server, I think i was the only one on it.

Edited January 31, 2012 by coda

[GOPHUR]

"After paying attention to this for a while, my best guess. If you are at your spawn point location and respawn, you're terrain is already loaded, so you respawn right away.

When you change your area, you unload the terrain where you are and reload the new area. That would explain the extra time."

Correct.