docs/re: point the ship item at the end-to-end mission-path measurement
The entry said the crash blocks it; it now also says how far a run gets (past SELECT DATA, into a cinematic) and that the crash's firing point moves, so nobody goes looking for a menu route around it.
This commit is contained in:
@@ -607,4 +607,9 @@ throw, 537 stacked dumps, with `--mem_watch=false`. See
|
|||||||
[`title-crash-stl-tree.md`](title-crash-stl-tree.md).
|
[`title-crash-stl-tree.md`](title-crash-stl-tree.md).
|
||||||
|
|
||||||
So a second capital-ship capture needs that crash dealt with first. Everything up
|
So a second capital-ship capture needs that crash dealt with first. Everything up
|
||||||
to the save-slot screen is now scripted and works.
|
to the save-slot screen is now scripted and works, and one run got *past* it —
|
||||||
|
`SELECT DATA` reached with zero crashes, slot chosen, the game proceeding into a
|
||||||
|
cinematic — before crashing at the same `0x82307128`. The crash is intermittent
|
||||||
|
in **where** it fires, not whether, so there is no menu route around it. See
|
||||||
|
[`title-crash-stl-tree.md`](title-crash-stl-tree.md) for the end-to-end
|
||||||
|
measurement and for what has been ruled out (`--mem_watch=false`, twice).
|
||||||
|
|||||||
Reference in New Issue
Block a user