norman99 Posted May 23, 2020 Posted May 23, 2020 Obviously there has been lots of requests for cyclic ops, and more control of the launch/recovery cycle in general. One possible implementation, that could be done relatively easy would be the addition of two parameters in the mission editor, Launch Window & Recovery Window, along with open & closed flags for each. When either is closed, that operation is suspended, either delaying launches, or holding aircraft in the stack overhead, until they open again. This would allow mission designers complete freedom to create a variety of scenarios using any trigger available, such as times, aircraft proximity, fuel states, basically anything one can think of. Defaulting both to open would ensure those not interested in this additional control aren’t unduly affected either.
ScopeDope Posted May 27, 2020 Posted May 27, 2020 Obviously there has been lots of requests for cyclic ops, and more control of the launch/recovery cycle in general. One possible implementation, that could be done relatively easy would be the addition of two parameters in the mission editor, Launch Window & Recovery Window, along with open & closed flags for each. When either is closed, that operation is suspended, either delaying launches, or holding aircraft in the stack overhead, until they open again. This would allow mission designers complete freedom to create a variety of scenarios using any trigger available, such as times, aircraft proximity, fuel states, basically anything one can think of. Defaulting both to open would ensure those not interested in this additional control aren’t unduly affected either. Yes to this! Another idea I had was special options for each catapult. That way you could switch off 1 and 2, have aircraft park on the bow, etc. When all 4 cats are switched off, you're in pure recovery mode.
Recommended Posts