Version v1.7 released!
Integrated the new changes brought by ITO v1.05.4 (for 4.35 U3).
Removed the PPT.ini fix “SKY”, since its shortname conflicted with the Skyguard threat ring.
Revised AGM-45 Shrike FM and Seeker, to make it more realistic.
A new Shrike definition was also added to the Tacview Add-On .xml, thereby requiring a reinstall of that file as per the instructions in “README.txt”.
UOAF presents: Israel 1980s for BMS 4.35!
Thanks to vAiCon for providing the official Israel Theater for BMS 4.35, which serves as the foundation for this theater.
The goal of this project is to provide an Israeli theater optimized for 1980s-style operations, with very limited aircraft, avionics and loadout options.
GitHub Repository:
https://github.com/UOAF/Israel1980s
Primary download:
https://github.com/UOAF/Israel1980s/releases
Secondary download (latest version - v1.7):
https://drive.google.com/drive/folders/13hwgD6Bi-5jlQri62TvDkNLJBRFLX5lA?usp=sharing
How to install:
Version History:
Version 1.7 - 31.10.2021
-Integrated the new changes brought by ITO v1.05.4 (for 4.35 U3);
-Adjusted AGM-45 Shrike missile FM and Seeker properties to better simulate real life performance;
-Added new AGM-45 Shrike definition in the Tacview Add-On .xml, requiring each user to repeat the install process as per "README.txt" instructions;
-Fixed a conflict of two definitions in the PPT.ini file;
-Made the M163 radar visible on RWRs, just like the ZSU-23-4 Shilka;
Version 1.6 - 18.07.2021
-Integrated the new changes brought by ITO v1.05.3 (for 4.35 U2);
-Revised Tacview Add-on .xml setup instructions, to avoid issues from incorrect backslash placement in the paths added to "Data-Falcon4Theaters.xml";
Version 1.5 - 25.06.2021
-Updated Visual Aircraft Recognition Documentation by Stevie;
-Fixed F-16C-32 EAF Aggressor using the USAF blk50 cockpit and wings model;
-Fixed a CTD that occurred when adding the F-4E IAF to a Dogfight match, also added the F-4E EAF to available Dogfight airframes;
-Fixed the IAF Museum being on top of Hatzerim AB's Runway 10R, moved it 1km north-east where it belongs;
Version 1.4 - 23.06.2021
-Introduced new "F-16C blk32 EAF Aggressor" aircraft, identical to the default EAF blk32 in every way except for its radar, which shows up as "29" on RWRs;
-Additional battalion unit composition fixes to improve the realism of Serpent's Sting;
-Fixed F-4E IAF not being auto-fragged for SEAD, thanks to Gastone for identifying the bug and providing fix-instructions;
Version 1.3 - 14.06.2021
-Reworked some battalion unit compositions to improve realism, mainly in Egyptian units for Serpent's Sting;
-Added version number to the 2D main menu background and theater selection list;
-Replaced the default Court Martial debrief sound with something fresh;
-Minor UI texture fixes;
Version 1.2 - 30.05.2021
-Integrated the new changes brought by ITO v1.05.2 (for 4.35 U1), including the adjusted CkptArt, ACData and Objective features;
-Properly integrated F-4E EAF/IAF ACData and fixed their AI weapon employment altitudes;
-Fixed the 2 training missions from the previous release that weren't usable;
Version 1.1 - 23.05.2021
-New GBU-15 and ACM (4v12) training TEs;
-New F-16A-blk15 EAF (same AA loadout as IAF blk15), mainly intended as a heaters-only REDFOR Viper for mission designers;
-More realistic Mig-23 and AA-7A/B capabilities and flight models, provided by NHawk;
-Addition of an add-on .xml file for Tacview, which fixes the labels, models and threat ranges of many objects;
-Fixed F-16A/B-15 IAF not being SEAD/DEAD fraggable and EAF using SAAF Mig-21s in the campaigns (and viceversa);
-Minor UI texture improvements, semi-transparent "help" and "commit" buttons and updated IA/DGFT/TE/CAM preview maps to the v1.05 standard;
Version 1.0 - 12.05.2021
-Integrated the new changes brought by ITO v1.05 (for 4.35 U1), including new aircraft, airbase frequencies and objective data;
-New "Visual Aircraft Recognition Charts+Guide" documentation provided by Stevie;
-More realistic AIM-9L and AIM-7-E2/F/M flight models provided by NHawk;
-Fixed unrealistic aircraft loadouts and battalion unit compositions;
Beta 0.5 - 24.04.2021
-New UI background music and "Peace for Galilee" intro video taken from ITO80s 4.33;
-Added the EC-707 Re'em (Oryx), an IAF EW aircraft that can now be used for ELINT and EWS/ESJ (SAM Jamming) missions;
-Reworked "Peace for Galilee" and "Serpent's Sting": moved E-2C squadrons to resolve AI not fragging it and replaced RC-135W squadrons with the new EC-707, added many more IDF Hawks;
-Fixed crashes in "Peace for Galilee" caused by oversized Brigade units;
-Fixed the KFIR being rendered as F-CK1 (with the help of ccc1tw);
Beta 0.4 - 18.04.2021
-New Realistic Campaigns: "Peace for Galilee" and "Serpent's Sting";
-Further adjustments to the DB, overhauled battalion layouts to improve realism, created the M163 vehicle to serve as AAA for blue forces, transformed the Stinger into the older Redeye MANPAD;
-Made static SAM sites not always visible;
-Fixed A-4 avionics/IFF, flyable missions, loadout and squadron stores;
Beta 0.3 - 08.04.2021
-Updated "ppt.ini" with a fresh layout and additional markpoints (thanks to Jackal for contributing the base for the new PPT file!);
-Complete background Art overhaul, 80-fied all background imagery and meme-ified some others...;
-Rearranged campaigns according to future plans, renamed the gameplay-oriented custom editions of "1982 Peace for Galilee" to "Operation Lox" and "1988 Serpent's Sting" to "Spitting Cobra", moved them from respective slots 4 and 1 to slots 4 and 5;
Beta 0.2 - 28.03.2021
-Reworked "1988 Serpent Sting" and "1982 Peace for Galilee" Campaigns;
-New missile, AIM-9L (replaced 9M): higher flare chance and ground clutter factor than AIM-9M;
-Adjusted AA-2D (IR) missile: lowered flare chance and ground clutter factor towards AIM-9P values;
-Added SA-7 to "OSA II" missile boats;
Beta 0.1 - 20.03.2021
-First pre-release of Israel 1980s;
How to apply the solution to your theater:
As explained previously, to write the coordinates in the .acmi correctly, BMS code needs to know the N/S lat and W/E lon of the 4 theater “sides”.
It was decided to let BMS read those values out of an Add-On [theatername]\Terrdata[theatername]\terrain\Theater.map file, since it’s a binary file, you will need a hex editor (I used HxD) to add the values.
C:\Programs\Tacview\Data\Xml\Data-Falcon4Theaters.xml, this will provide a quick reference for theater border coordinates that should already provide a proper alignment in Tacview (for most 64 tile theaters), for this example we’ll use the ITO values;<West>30</West>
<East>40</East>
<South>25</South>
<North>35</North>
open your Theater.map with a hex editor like HxD (might be better to make a backup of the file first), make sure you select “little endian” as Byte Order below the Data Inspector;
In HxD, “Edit>Insert Bytes”, set bytecount to 4 to insert 32 new bits, they will be highlighted in red. Mark them and use the Data Inspector to overwrite them with a new float (32 bit) value “20000”, this is some “max altitude” metadata that needs to be present;
Insert 8 new bytes (64 bits) like in step 3, select them and use the Data Inspector to overwrite them with a new 64 bit float, repeat this step a total of 4 times to write the WEST, EAST, SOUTH, NORTH border coordinates in order;
In total you should have added: “20000” as a 32bit (4 hex-value pairs or bytes) float and the WEST, EAST, SOUTH, NORTH border coordinates as 4 consecutive 64bit (8 hex-value pairs or bytes) floats, all totaling to 36 new bytes written since you started editing. Save the file and check alignment by creating an acmi using the new native export;
@gundam the AB>Mil click is much louder than the Mil>AB click by default, are you sure you’re not hearing the latter at all?
As long as you see both “burner-on.ogg” and “burner-off.ogg” files in the BMS-Burner folder, the program should have no issue playing both.
Also check your “bms-burner-log.txt” file, it should have logged both Mil>AB and AB>Mil changes.
Version v1.6 released!
Integrated the new changes brought by ITO v1.05.3 (for 4.35 U2).
Revised Tacview Add-on .xml setup instructions in the zipped README.txt, I encourage everyone to re-read them.
The revisions were made because some issues stemming from incorrect backslash placement in the ITO80s DB paths in “Data-Falcon4Theaters.xml” have been found:
make sure you only use backslashes “” in those paths and put an single backslash at the end of each path, after “\terrain” and “\objects”.
@lorikeolmin My bad, apparently the forum formats a double “-” as “–”, instead of just “- -” that are closer together.
@cag Which version of Windows are you running? From what I’m reading that specific DLL was first included in windows 8.
You could try out fix suggestions like this one from the microsoft helpdesk.
Alternatively, install the Python interpreter and execute my source code directly, instead of using the compiled .exe.
@nitaihatr2 Just like with the recent ITO v1.05.4 update, the only v1.7 changes which affect saves are those to the DB’s flight units.
While I’m not entirely sure what those changes do to already fragged flights, I doubt they’d break saves, otherwise we’d have seen appropriate warnings when updating ITO.
ACData MissionType Selector has been updated to handle 4.36’s additional mission types.
@khronik The issue is that it’s not just a single xml file, it’s one for every theater you installed or plan to install (if it hasn’t been updated yet).
FYI, it’s also not reverse engineering, I simply shared the source code that I compiled the auto-patcher from. If you can’t execute the .exe, installing the python interpreter and executing the source code will likely still take less time and annoying repetitive labor than manually editing everything.
How to apply the solution to your theater:
As explained previously, to write the coordinates in the .acmi correctly, BMS code needs to know the N/S lat and W/E lon of the 4 theater “sides”.
It was decided to let BMS read those values out of an Add-On [theatername]\Terrdata[theatername]\terrain\Theater.map file, since it’s a binary file, you will need a hex editor (I used HxD) to add the values.
C:\Programs\Tacview\Data\Xml\Data-Falcon4Theaters.xml, this will provide a quick reference for theater border coordinates that should already provide a proper alignment in Tacview (for most 64 tile theaters), for this example we’ll use the ITO values;<West>30</West>
<East>40</East>
<South>25</South>
<North>35</North>
open your Theater.map with a hex editor like HxD (might be better to make a backup of the file first), make sure you select “little endian” as Byte Order below the Data Inspector;
In HxD, “Edit>Insert Bytes”, set bytecount to 4 to insert 32 new bits, they will be highlighted in red. Mark them and use the Data Inspector to overwrite them with a new float (32 bit) value “20000”, this is some “max altitude” metadata that needs to be present;
Insert 8 new bytes (64 bits) like in step 3, select them and use the Data Inspector to overwrite them with a new 64 bit float, repeat this step a total of 4 times to write the WEST, EAST, SOUTH, NORTH border coordinates in order;
In total you should have added: “20000” as a 32bit (4 hex-value pairs or bytes) float and the WEST, EAST, SOUTH, NORTH border coordinates as 4 consecutive 64bit (8 hex-value pairs or bytes) floats, all totaling to 36 new bytes written since you started editing. Save the file and check alignment by creating an acmi using the new native export;
@df1979 most browsers seem to have issues opening that web-page, might have to do with the server’s .htaccess file.
Right clicking the link and selecting “save link as file” works though.
@ccc1tw thanks for pointing that out, I completely forgot to add that important step to the README 
The shared .7z has now been updated to include a revised README.txt (the download link is unchanged).
@ccc1tw I’m guessing that they are “empty” slots that will hold future mission types, though I’m not sure why they had to be defined at all in that case 
ACData MissionType Selector has been updated to handle 4.36’s additional mission types.
<p>@airtex2019 Unfortunately this wasn’t made clear enough. I’m the author and first shared the source code on the UOAF discord (<a href=“https://discord.gg/U7UykYX” target=“_blank”>invite</a> and <a href=“https://discord.com/channels/582602200619024406/615631373968998435/908706086377357352” target=“_blank”>specific message</a> link), where I first noticed discussion around the issue. Later I compiled the same code into the .exe that was distributed to everyone. I also attached the source code in <a href=“https://forum.falcon-bms.com/post/334192” target=“_blank”>this reply</a> of mine in this very thread, though I admit I probably should have asked depapier to link it in his first post for best visibility.<br />In any case, as @airtex2019 correctly pointed out, my code just grabs the BMS path from the registry, finds the FALCON4_RCD.XML within every theater and only edits the 3 seeker entries mentioned by the hotfix notice. I didn’t make the script pause because it is usually bad practice when coding CLI applications, but if you open a CMD shell and run the .exe or .py from there you’ll see how it lists every file that it modified.<br />Python is one of the best languages available to quickly write short but powerful code like this, batch files are pretty limited when more complex logic is required. The python interpreter is also trivial to install and only going to become more useful in the future, even on non-coder PCs. For those who trust my word, there’s always the .exe.<br />Next time I’ll make sure to publish both exe and source code together in a more comprehensive way, along with an exe hash for good measure, cheers!</p>
@khronik The issue is that it’s not just a single xml file, it’s one for every theater you installed or plan to install (if it hasn’t been updated yet).
FYI, it’s also not reverse engineering, I simply shared the source code that I compiled the auto-patcher from. If you can’t execute the .exe, installing the python interpreter and executing the source code will likely still take less time and annoying repetitive labor than manually editing everything.
@cag Which version of Windows are you running? From what I’m reading that specific DLL was first included in windows 8.
You could try out fix suggestions like this one from the microsoft helpdesk.
Alternatively, install the Python interpreter and execute my source code directly, instead of using the compiled .exe.
@lorikeolmin My bad, apparently the forum formats a double “-” as “–”, instead of just “- -” that are closer together.