Fixes an infinite loop in case a connection to the same CP is made in the template miz file of the campaign. It's basically wrong input, but suppose we'd have a use-case for it in the future, it would still make sense to have ground units retreat to a CP that's different from their origin...
* vietnamwarvessels first batch
* Ship YAMLs
* aircraft yamls initial version, need more work
* initial helicopter yamls
* update aircraft yamls
* Added DDs Fletcher and Sullivans
* ship icons
* aircraft banners and icons
* no huts
* update py files to VWV v0.9.0
* update aircraft yamls, add vigilante
* added 2 ships for VWV v0.9.0
* mig-21mf yaml
* icons and banners additional units v0.9.0
* added VWV units to USA_1970 and Vietnam_1970 JSONs
* Revert "added VWV units to USA_1970 and Vietnam_1970 JSONs"
This reverts commit ed0b28dc36c0d9c1a45a10689a3c419bd23ff258.
* A-1H yaml update
* mig-17 yaml update
* update helicopter yamls
* extension init
* weapon injections
* icon filenames _24 added
* removed tasks 0 from yamls
* hh2d yaml fix
* added VWV v0.9.0 to factions USA and Vietnam
* added max_range to aircraft yamls
* housekeeping
* Flyable to False - not available in mod version
* minor edits
* ignore test campaign
* deleted tasks
* weapon luas blue air
* added task numbers from task.py
* weapon luas red air
* task id numbers in comment
* switched weapon lua from aim-9J to aim-9D
* removed test campaigns
* update payload luas with payload names from flighttype.py
* Changed AIM-9D to 9B, 9D does not work
* removed air assault task for HH-2D
* Cva_31 added to runway_is_operational()
* CVA-31 added to naval_units in faction jsons
* add strike and cas tasks to ra-5c
* correct typo
* Added Armed Recon as task and payload to most a/c
* ignore pre-commit-config.yaml
* pre-commit-config
* black reformat controlpoint.py
* Added tasks to Vigilante (next to Recon) containing attack subtasks, which allow it to be scheduled for missions
* added ships to UNITS_WITH_RADAR
* remove pre-commit-config from gitignore
* added red aircraft to nva_1970 faction
* fixed black's complaint (two empty lines, should be one)
* fix airwing config not properly saving or loading
* add helper message to save function
* bugfixes
* remove unnecessary import used during testing
* yet another forgotten import
* change raise error to log warning
* fix conflict
* squash bugs and reuse patrol layout
* fix tanker tacan and formatting
* fix unlimited fuel option
* update pretense for tanker changes
* reuse refueling flight plan and bugfix for sunken carrier
changelog
* remove unitmap dependency
* formatting and more unit map removal
* more formatting
* typing and black
* keep tanker out of clouds
* fix if there are no clouds
* better cloud handling
* groundwork for recovery task
* remove changes to game/commander
* Finishing up recovery tankers
---------
Co-authored-by: Raffson <Raffson@users.noreply.github.com>
This is by no means complete. The bugs that this solves were already in
6.x, but we'd hidden the speed controls for the sim in that release, and
have always said that anything done after pressing "go" the first time
is undefined behavior. This is the first step on making those mid-sim
actions behave correctly.
UI actions such as creating a new package need to be executed between
ticks of the sim. We can either do this synchronously by blocking the UI
until the tick is done executing, acquiring a lock on the sim, executing
the action, then releasing the lock; or asynchronously by queueing
events and letting the sim execute them when it completes the current
tick (or instantly if the sim is paused).
Anything that comes from the new UI (currently just the map) must be
asynchronous because it goes through the REST API, but for the old UI
it's simpler (and because the lock will only be acquired as quickly as
the user can act, shouldn't slow anything down) to do this
synchronously, since it's difficult to use coroutines in Qt.
https://github.com/dcs-liberation/dcs_liberation/issues/1680
Some maps have inaccurate bounds for sea-zones, thus waypoints that end up being too close to the shore may keep using AGL which could still lead to trouble. Adding a condition to check whether a point is "not on land" will likely fix this issue for maps that have gaps between sea-zones and inclusion-zones around the shoreline...
