M10 issue in the beginning

[OLD CROW]

Modules in conflict: F-14B , Supercarrier module

Map: Syria

DCS version: 2.9.19.13478 MT

Reproduction Steps:

1- Start a mission with the F-14B CAG positioned to taxi toward CAT 3 while an E-2 is already spotted on CAT 3.

2- E-2 on CAT 3 spools up engines.

3- F-14B CAG begins taxi to CAT 3.

4- The first marshaler transfers control to the marshaler positioned behind the jet blast deflectors of CAT 3.

5- F-14 begins its 90-degree turn toward CAT 3 while the jet blast deflectors are still lowering.

6- The marshaler signals “hold” (closed fists).

7- The F-14 hesitates briefly, then continues attempting the turn despite the “hold” signal.

Expected Result:

- F-14 should hold position until the jet blast deflectors are fully lowered and the marshaler gives the appropriate “taxi forward” signal.

- After proper signaling, the F-14 should complete its 90-degree turn smoothly and line up with CAT 3.

Actual Result:

- F-14 continues to attempt the 90-degree turn toward CAT 3 while the marshaler keeps signaling “hold.”

- The aircraft stutters through the motion and ends up stuck in a perpendicular position relative to the CAT 3 axis.

- F-14 remains locked in place indefinitely, preventing normal carrier operations.

Additional Notes:

This seems to be caused by a conflict between the F-14 module, the scripted takeoff trigger chain and the Supercarrier’s marshaler logic.

Issue blocks mission progress since the F-14 never clears the taxi path or launches.

 

Is there any possible interim solution until you add the definitive solution to any next update, like editing any launching position of any aircraft (E-2 or F-14 CAG) in the mission editor, just to let me progress in the mission? I'm not worried about campaign statics, I'm only interested in flying the mission. Thanks for advance.