T1M6: TRN Epsilon hypers out instead of disabling

[J. King]

In X-Wing during Operation 6 of Tour 1 (MAX13), TRN group Epsilon moves to disable FRT Ars Opus as soon as it is captured by Alliance forces; in XWVM Epsilon continues off into hyperspace even after Ars Opus is captured, thus the player only needs to contend with one wave of transports, making the mission much easier.

[Ras Talon]

Tested the mission, did not observe this behavior. I believe the issue has since been resolved.

[J. King]

Confirmed it still occurs. See video:

https://youtu.be/zgt8UaRTseI

[Ras Talon]

I figured out what's going on.

The TRNs arrive in two waves. When the first wave arrives, the FRT isn't captured yet, so it's neutral, so they disengage.

By the time the second wave arrives, the FRT is captured, so it's friendly, so the TRNs engage it. That's what I was seeing when I thought the issue was resolved.

Should be easy to test if the issue is indeed that a DISABLE order by neutrals doesn't work on another neutral.

[J. King]

I doubt it's related to IFF: the FRT is already disabled when the first wave arrives, so they unfurl the MISSION ACCOMPLISHED banner, and head for hyperspace. The difference may be one of timing, or that hyperspace is cancellable in X-Wing but not XWVM.

[Ras Talon]

Flew the mission in X-wing 94. It's the second thing.

The TRNs hyper in, fly off to the side, I'm assuming to hyper out (no way for me to check), and then the FRT gets captured, and they engage to disable the FRT.

[J. King]

It looks like in Original X-Wing Epsilon 1 does in fact hyper out, but Epsilon 2, 3, and 4 remain. Evidently Epsilon 1 is ever so slightly closer to its hyperspace point thanks to it being the lead of a Vic formation. Video:

https://youtu.be/055CcxHqhEA

We can therefore conclude that it is largely a timing problem, but it could be any of the following:

1. Capturing takes too long
2. Hyperspace starts too soon
3. Craft aren't quite flying at the right speeds
4. The Vic formation is too tight.

Given the two videos, it does look like possibility 4 is a strong one.

[J. King]

Modifying the mission to increase the distance the transports travel makes no difference to the outcome in XWVM, so it's apparently a logic bug: craft should be able to re-evaluate their decision to hyper out until the jump is actually triggered.

[David Esparza Guerrero]

Fixed: Issue #342 "T1M6: TRN Epsilon hypers out instead of disabling"

→ <<cset bd24dd715b6f>>