* Change indentation of register_special_waypoints (put out of loop)
* Added Strike Targets as F-15E Mission Target points (Set/Mission 1)
* Set up check for ASM : only if non-human flight lead. Add targets to the kneeboard.
* Generate multiple sets (i-e M2.1) for situations where the number of points is more than 8.
Added check condition to kneeboard (otherwise, may result in multiple writes).
* Change name of register_special_waypoints to register_special_strike_points
Add register_special_ingress_points method for special IPs and add to the appropriate classes
* Add changelog entry for Tomcat's IP wpt
* Avoid depending on client slots for special wpts injection
---------
Co-authored-by: tmz42 <thomas.monnzie@gmail.com>
Co-authored-by: Raffson <Raffson@users.noreply.github.com>
* Unlimited fuel for AI flights. For player flights, included at startup, for AI flights with join/split, applied at join/split.
* Unlimited fuel for AI flights. For player flights, included at startup, for AI flights with join/split, applied at join/split.
* Corrected default value of ai_unlimited_fuel to False in configure_behavior
* ai_unlimited_fuel : set argument based on setting and simplify activation section
* AI Unlimited Fuel : enable at start, disable at racetrack start/join, enable at racetrack end/split
* Correct typing : bool to Optional[bool]
---------
Co-authored-by: tmz42 <thomas.monnzie@gmail.com>
Putting the ingress point directly on one end of the FLOT means that AI
flights won't start searching and engaging targets until they reach that
point. If the front line has advanced toward the flight's departure
airfield, it might overfly targets on its way to the IP.
Instead, place an IP for CAS the same way we place any other IP. The AI
will fly to that and start searching from there.
This also:
* Removes the midpoint waypoint, since it didn't serve any real purpose
* Names the FLOT boundary waypoints for what they actually are
Fixes https://github.com/dcs-liberation/dcs_liberation/issues/2231.
This isn't a great fix for the reason I mention in the comment, but it's
quick and actually is accurate since it looks like we don't actually
handle formation speeds correctly in most cases...
This is probably as "fixed" as this is going to get for now since most
of the flight planning code is in the process of being rewritten.
https://github.com/dcs-liberation/dcs_liberation/issues/3113
We don't need explicit configuration of initial points. The plane
automatically configures any steerpoint immediately before a target
point as an initial point.
Target offset points and aim points have not been implemented because I
can't find any information the describes their intent.
Fixes https://github.com/dcs-liberation/dcs_liberation/issues/3088.
- Plan number of aircraft more accurately
- Fine-tuning ingress waypoint tasks
- Add lineup waypoint for STRIKE flights, 10NM in front of ingress on the same heading as the target
Restores handling of TheaterGroundObject targets in antishipingress.py
This is needed when anti-ship missions are planned against other ship groups than NavalControlPoints (carrier groups or LHA strike groups).
