Implementing Departure procedures(Case I/Case II)

[Hogeo]

Departure procedures have been a long-standing request.

It seems that Case III (though there is no voice report) has been implemented.

But the others are not yet.

In Case I, after taking off from the carrier, you just fly from the carrier to 7DME at an altitude of 500ft at 300 knots, and then you can navigate freely.

This does not seem difficult to implement, since there are only altitude and speed restrictions up to 7DME.

One example of how to implement this is to aim for a waypoint at alt=500ft, speed=300kts a few nm ahead at 1 second intervals until 7DME, and when the AI aircraft leaves 7DME from the carrier, fly to the waypoint originally set for the AI aircraft group.

When I implement it like that, it climbs to about 1000ft immediately after taking off. After that, it tries to fly down to 500ft. I would like to eliminate this first climb up to about 1000ft.

Case || is a bit special, and you must avoid flying through the clouds.

1) Fly at 300 knots at an altitude of 500ft from the carrier to 7DME.

2) If you find a gap in the clouds 7DME from the carrier, the 500ft altitude restriction is lifted, and you can climb through the gap (i.e., it is the same as case I).

3) If there is no gap in the clouds that you can climb through, keep your altitude at 500ft, pass over the 10DME Arc as in case III, leave the 10DME Arc on the departure radial, and fly in search of a gap in the clouds.

4) If you find a gap in the clouds, the 500ft altitude restriction is lifted, and you can start climbing.

The question here is how to find a gap in the clouds, but I think you can determine this by flying some kind of target in the sky that is invisible to the player, and using the Controller.isTargetDetected() function to determine whether the target is detectable with DetectionType=visible.

If I were to implement this, the player would see the target (i.e. an aircraft not on the plan flying), which would raise the question of why such an aircraft is flying.

So I would like to see this implemented in Supercarrier.

[Hogeo]

I tried to implement the Case II departure procedure.

When the aircraft is more than 7 DME away from the carrier, several Russian helicopters are spawned in the sky, and the Controller.isTargetDetected function is used to detect them and find the next direction to head.

However, when the cloud density is 8 or less, visible=true is returned even if the helicopter is not visible due to the clouds, and conversely, when the cloud density is 9 or more, visible=false is returned for helicopters at altitudes above the cloud base, even if they are visible.

If visibility can be judged not by a simple cloud base or thickness setting, but by judging whether an object is visible as seen by the human eye, it should be possible to ascend through gaps in the clouds.

Also, in my implementation, I cannot set the altitude from launch to 7 DME to 500ft, or fly at a constant 300KIAS throughout the entire departure procedures.

The implementation of Case I/II Departure procedures and the rough implementation of Case III report call are implemented in a series of processes called by the flib_CV_departure_ops:go_case_departure() function contained in flib_CV_departure_ops.lua.

The contents of the lua files included in the two mission files are identical, and their licenses can be considered public domain, so please feel free to use them if necessary.

I hope this will help you fully implement Case Departure Procedures in Supercarrier.

test_CASE II deperture_cloud_density=8.miz

est_CASE II deperture_cloud_density=9.miz