Resolves#313
* Initial commit of OH-6 Modpack v1.2 + Vietnam Asset Pack v1 support.
* Added OH-6 Mod loadouts by @Starfire13
* Modified pydcs_extensions/oh6_vietnamassetpack/oh6_vietnamassetpack.py
Added resources/units/ground_units/vap_m35_truck.yaml
Added resources/units/ground_units/vap_mule.yaml
Added resources/units/ground_units/vap_mutt.yaml
Added resources/units/ground_units/vap_mutt_gun.yaml
Added resources/units/ground_units/vap_type63_mlrs.yaml
Added resources/units/ground_units/vap_vc_bicycle_ak.yaml
Added resources/units/ground_units/vap_vc_zis.yaml
* Modified changelog.md
Modified resources/factions/USA 1970 Vietnam War.json
Modified resources/factions/USA 1971 Vietnam War.json
Modified resources/units/ground_units/vap_mule.yaml
Added resources/units/aircraft/OH-6A.yaml
* Added the OH-6 to factions and implemented the mod selection in the new game wizard. Added an icon an a banner.
* Modified resources/units/aircraft/OH-6A.yaml
* Added icons for the Vietnam Asset Pack ground units. Also added an icon for the PT-76 since it was missing. Added a Viet Cong 1970s faction.
* Added resources/units/ships/vap_us_seafloat.yaml
* Adjust tasking for OH-6A
OH-6A is only capable of Transport & Reconnaissance, but we can ignore this if the lead slot is a client. AI however will most likely not support this, but we can add Transport & Air Assault instead...
* Fix bug in configure task + client override fallback
---------
Co-authored-by: Raffson <Raffson@users.noreply.github.com>
AI got a little better, at least that's what tests in AFG showed. The main issue is that helicopters tended to attack static objects, which we obviously don't want...
* Large aircraft ground spawns
Added the ability to add separate ground spawns for C-130 and other large aircraft to campaigns. Implemented on @holyorangejuice 's request.
Large aircraft ground spawns are added to the campaign by placing a C-130 on the ramp, just like an A-10 or AJS37 previously. Note: use the stock DCS C-130, so the campaign miz can be safely opened without the C-130 mod (or any other mod) installed. Not the C-130J player-flyable transport, not the KC-130J tanker included in the UH-60L mod etc.
Large planes (wingspan more than 40 meters, such as the C-130):
- First try spawning on large ground spawns
- Then try the regular airfield ramp spawns
Below 40 meter wingspan aircraft:
- First try spawning on regular or roadbase ground spawns
- Then try the regular airfield ramp spawns
- Then, if both of the above fail, use the large ground spawns
* Specify explicit black version 23.9.1 to fix lint error.
* Update lint.yml
---------
Co-authored-by: Raffson <Raffson@users.noreply.github.com>
As a result of using fast-forward, AI flights are already oriented towards SPLIT, which slows things down during mission start. The escorts tend to go all over the place because of this...
Randomly chooses one of the liveries defined if present in the squadron's yaml, overrides entry for "livery" or whatever is chosen in the UI except liveries on flight-member level
* 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>
This doesn't need to be a part of FlightPlan, and it's easier to test if
it isn't. Move it out and add the tests.
It's pretty misleading to allow this in the core of the flight plan code
anything. This is an extremely unreliable estimate for most aircraft so
it should be more clearly just for briefing purposes.
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 property affects safe compat because the ID is what gets preserved
in the save, but it's unfortunately also used as the display name, which
means changing the display name breaks save compat. It also prevents us
from changing display names without breaking faction definitions.
This is the first step in fixing that. The next is adding a separate
display_name property that can be updated without breaking either of
those.
