Hogeo Posted June 22 Posted June 22 (edited) In the current supercarrier, spawning into Street, i.e. launching 16 aircraft, is only possible at the start of a mission. However, this implementation is inconvenient when implementing cyclic ops, as only 12 aircraft can be launched from event 2 onwards. In CV-PROCEDURES, it is said that 12 to 20 aircraft will participate in cyclic ops. Since the purpose is to train the continuous launch and recovery of many aircraft in a short period of time, it is thought that training with a small number of aircraft will not be very effective. When assuming a multiplayer mission in which the carrier sails in a straight line and launches and recovers repeatedly, it may be troublesome to be spawned into Street, but that can be solved by simply making it possible to specify the location to spawn. In the end, the only difference in implementation is whether the placement location is assigned automatically or manually, and the decision on whether it should actually be placed is the same in both cases, right? If you want to avoid placing on Street, it might be nice to have an option such as "Do not place on Street". If you are concerned about the impact of doing so on existing code, an option such as "Make it possible to place on Street" might be fine. Edited June 23 by Hogeo Corrected mistakes
Recommended Posts