e85f6ac955
This page's own reproduction - move the cache aside, get a throw; restore it, get none - made "the cache is incomplete" the obvious explanation for the mission crash. Three tutorial runs say otherwise. tut2 subdir 6 MISSING 641 crashes by t+24s 13243 total tut3 missing -> gained 6 in-run 2 crashes to t+80s 11898 total tut4 6 present from the start 2 crashes to t+56s 11497 total The missing entry was real: \aab216c3\6 was requested and absent, and the game wrote it during tut3 (11 -> 12 files). tut4 then ran with a complete cache and stormed anyway. Every dump across all three runs is PC 0x82307128, one address, no others. So the cache may gate the boot-time throw this page documents; it does not gate the mission one. What the runs did give is an opening. Both post-cache runs show the same shape - exactly 2 crashes, then nothing, for 56-80 seconds of rendering, advancing mission - where the first run was already at 641 by t+24s. That is where the second capital-ship capture has to happen: F10 armed INSIDE the window. Not a guarantee, since the storm began at t+24s, ~t+96s and ~t+56s across the three runs, but two of three offered most of a minute.