mirror of
https://github.com/dcs-retribution/dcs-retribution.git
synced 2025-11-10 15:41:24 +00:00
4d4f4d1930
* 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>
36 lines
887 B
Python
36 lines
887 B
Python
from .SWPack import *
|
|
from .a4ec import *
|
|
from .a7e import *
|
|
from .a6a import *
|
|
from .f100 import *
|
|
from .f104 import *
|
|
from .f105 import *
|
|
from .f15d import *
|
|
from .f15i_idf import *
|
|
from .f16i_idf import *
|
|
from .f22a import *
|
|
from .f4 import *
|
|
from .f84g import *
|
|
from .fa18efg import *
|
|
from .fa18ef_tanker import *
|
|
from .frenchpack import *
|
|
from .hercules import *
|
|
from .highdigitsams import *
|
|
from .irondome import *
|
|
from .jas39 import *
|
|
from .ov10a import *
|
|
from .spanishnavypack import *
|
|
from .su30 import *
|
|
from .su57 import *
|
|
from .swedishmilitaryassetspack import *
|
|
from .uh60l import *
|
|
|
|
|
|
def load_mods() -> None:
|
|
"""Loads all mods.
|
|
|
|
Note that this function doesn't *do* anything. Its purpose is to prevent editors
|
|
from removing `import pydcs_extensions` when it is "unused", because mod imports
|
|
have side effects (unit types are registered with pydcs).
|
|
"""
|