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>
(Github Readme Banner and Splash screen Artwork by Andriy Dankovych, CC BY-SA 4.0)
About DCS Retribution
(Last update: 2023-05-20)
DCS Retribution was forked from DCS Liberation, which is a DCS World turn based single-player or co-op dynamic campaign. It is an external program that generates full and complex DCS missions and manage a persistent combat environment.
DCS Retribution is still relying on Liberation for certain updates, and will possibly stay that way in a more distant future. Therefore, the patreon link will keep pointing to Khopa's account until further notice. However, we are no longer backwards compatible with Liberation, and will no longer attempt to do so.
Instead, we are focussing on keeping our campaigns forward compatible so that you as a user can continue on whatever campaign you had going on. Please keep in mind that once you save a campaign that was started in a previous (save-compatibility breaking) build, your save file will have been migrated and thus no longer compatible with the previous build. Therefore, we recommend backing up your saves and perhaps organizing them by version/build number.
For a more complete overview of our features, check the changelog.
Downloads
Latest release is available here : https://github.com/dcs-retribution/dcs-retribution/releases
To download preview builds of the next version of DCS Retribution, see https://github.com/dcs-retribution/dcs-retribution/wiki/Betas.
DCS bugs
These DCS bugs prevent us from improving AI behavior. Please upvote them! (But please
don't spam them with comments):
While DCS bugs are still a thing, we don't quite agree with the ones stated above. We believe to have addressed these, although some quirks still exist. For example, SEAD Escorts tend to be a little picky with what they engage, especially with older SAM systems.
Bugs and feature requests
If you need to report a bug or want to suggest a new feature, you can do this on our bug tracker. In either case, please use the search bar at the top of the page to see if it has already been reported. Note that you may need to remove the filter for open bugs if it's something we've recently fixed.
Roadmap
Our plans for future releases can be found on our Projects page. Each planned release has a Project, and the page for that project has columns for to do, in progress, and done. Items in the Done column are in the preview build for that release. Items in the To do column are planned to be added to that release.
Resources
Tutorials, contributors and developer's guides are available in the project's Wiki
(Some historical information is also availabe on Liberation's Wiki)
Special Thanks
First, a big thanks to shdwp, for starting the original DCS Liberation project.
Then, DCS Liberation/Retribution uses pydcs for mission generation, and nothing would be possible without this. It also uses the popular Mist lua framework for mission scripting.
Excellent lua scripts DCS Liberation/Retribution uses as plugins:
- For the JTAC feature, DCS Retribution embeds Ciribob's JTAC Autolase script.
- Walder's Skynet-IADS is used for Integrated Air Defense System.
Please also show some support to these projects !