[Kie99]

When trying to play the second to last mission (the one where you scan the Hades) I get a couple of parsing errors at the start relating to the Hades engines

Invalid subsystem name.

In sexpression: ( when
   ( or
      ( cap-subsys-cargo-known-delay
         0
         "Hades"
         "enginesdownleft"
      )
      ( cap-subsys-cargo-known-delay
         0
         "Hades"
         "enginesdownright"
      )
      ( cap-subsys-cargo-known-delay
         0
         "Hades"
         "engines"
      )
      ( cap-subsys-cargo-known-delay
         0
         "Hades"
         "enginesupleft"
      )
      ( cap-subsys-cargo-known-delay
         0
         "Hades"
         "enginesupright"
      )
   )
   ( do-nothing )
)
(Error appears to be: engines)
ntdll.dll! NtWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_13r_INF_SSE2-20110311_r7052.exe! <no symbol>
fs2_open_3_6_13r_INF_SSE2-20110311_r7052.exe! <no symbol>
fs2_open_3_6_13r_INF_SSE2-20110311_r7052.exe! <no symbol>

I OKd those errors and proceeded to the mission, but it crashed half way through.  I tried editing the mission to 'Engines' would refer instead to 'Engines Main' and the mission loaded correctly, but I still got the same crash midway through the mission, after being ordered to go and protect the science cruiser.  I get the same parsing error on the last mission, but I haven't tried to play through it.

Tried it with a couple of different builds.  Other missions involving the Hades work just fine though.

[CommanderDJ]

It might not be needed, but just in case, generate an fs2_open.log as detailed here. 9 times out of 10 it's usually all that's needed for people to help you fix the issue.

[mjn.mixael]

The engines issue I know about (and have no idea how it snuck through my debug runs).

The crash is probably related to the Typhon model (just a guess).