This allows for customizing OPFOR liveries, checking whether pilots are assigned, number of pilots available, and more stuff to get information & debug in an easier way...
* Implemented a new option in settings: Default start type for Player flights.
* Updated changelog.
* Removed unnecessary country parameter.
* Restore missing parameter
* on_pilot_changed should emit pilots_changed in its finally block, otherwise the start-type isn't updated if you have a single client pilot which you switch to a non-client pilot.
Also implemented other changes suggested by @Raffson, such as a more streamlined start_type QComboBox handling and moving the pilots_changed Signal to FlightRosterEditor.
* Decouple Signal from QFlighStartType
---------
Co-authored-by: Raffson <Raffson@users.noreply.github.com>
* Implemented support for the VSN Super Étendard v2.5.5
* Updated changelog and renamed the banner.
---------
Co-authored-by: Raffson <Raffson@users.noreply.github.com>
* Added F9F Panther mod support (version v2.8.7.101). Still missing loadouts and icon+banner.
* Added missing import in pydcs_extensions/__init__.py
* Added a banner and icon for the F9F Panther, credit for the banner to Jim over at the Century Series Discord. VSN Century Series logo used with permission. Also added loadouts for the F9F Panther and fixed the mod settings for it.
Mentioned by NoGoodNews as well as Starfire, once you open the logs an error would present itself as follows:
RuntimeError: The SignalInstance object was already deleted
* Updated Irondome support to IDF Assets Pack V1.1, which includes the David's Sling.
* Added an Israel 2017 faction with the David's Sling.
* IDF Assets Pack air defence presets and assets are now correctly removed from the faction when the mod is disabled.
* Removed the Iron Dome mod rocket launchers:
- "9M22U - 122mm Grad"
- "9M27F - 229mm Uragan"
- "9M55F - 300mm Smerch"
These were added to the Iron Dome Mod V1.2 in order for the radar to recognize them and be able to intercept them (these are limitations of DCS), so new rockets were added. However, they don't exist in the IDF Assets Pack.
* IronDome to IDF-Assets migration
---------
Co-authored-by: Raffson <Raffson@users.noreply.github.com>
* Rename pydcs_extensions/f4/__init__.py (from pydcs_extensions/f4b/__init__.py)
Rename pydcs_extensions/f4/f4b.py (from pydcs_extensions/f4b/f4b.py)
* Rename pydcs_extensions/f4/f4.py (from pydcs_extensions/f4/f4b.py)
* Support for the updated F-4B/C mod
Updated the F4.py pydcs extension to match the updated F-4B/C mod and
reworked the standard payloads to add "clean" to new F-4B pylons 11 and
12.
This includes a workaround to allow Liberation to use the new VSN F-4B
weapons with combined 2x Aim-9js on pylons 3 and 9 underslung with bombs
on ters on new pylons 11 and 12. In mission editor the combined weapons
are selected in pylons 3 and 9 and their under-slung counterparts are
forced onto 11 and 12 using "required" arguments in the mod's lua. All
other pylon 3 and 9 weapons use "required clean" arguments. Liberation
doesn't have a way to force these linkages onto pylons 11 and 12 and
without them, even without clean, no weapons will load on 3 and 9 or 11
and 12.
The workaround for normal weapons on the F-4B is to set the standard
load-outs to "clean" on pylons 11 and 12. This allows all normal weapons
to work on pylons 3 and 9 so long as pylons 11 and 12 are left as Clean.
It also allows Clean into the Liberation dropdown so it can be selected
later if necessary.
The workaround for the 4 new weapons that combines pylons 3 with 11 and
9 with 12 is that the user has to use the matching pair on each set of
pylons. For example - if F4B_LAU105_AIM9J_2_BRU42A_MK82_3 is selected
for pylon 3, BRU 42A MK823 LAU105 AIM9J2 must be selected for pylon 11.
Failure to do this correctly doesn't crash liberation or DCS, the result
will just be either no weapons at all on either pylon or the underslung
weapons on 11 and 12 floating without a pylon attaching it to the plane.
When updating f4.py in the future, note that running the pydcs database
export doesn't pull any data for Pylons 11 and 12. Those matching
weapons / classes have to be manually defined in those pylons for the
F-4B. This is noted in f4.py.
* F-4 mod support update to 2.8.7.201
* Updated QGeneratorSettings.py and the changelog.
* Updated F-4B and F-4C loadouts.
* Added the Phantom to some additional factions.
* Changelog updated: Updated support for F-4B/C Phantom mod to 2.8.7.204
The pydcs export for the latest patch was identical, which means it's also supported.
* Migrator change for renamed F-4B/C folder
---------
Co-authored-by: Nosajthedevil <78634843+Nosajthedevil@users.noreply.github.com>
Co-authored-by: Raffson <Raffson@users.noreply.github.com>
