Israel 1980s for BMS 4.35 - UOAF edition
-
New version “Beta 0.4” released.
-
New version “Beta 0.5” released.
This will probably be the last beta version, depending on stability feedback.
-
Miss ITO1980s , great campaigns to boost our skills!
Thanks! UOAF ITO1980s dev team !
-
Version 1.0 released!
Integration of the changes brought by ITO v1.05 + multiple other fixes and reworks.
Battalion layouts were overhauled once more in an effort to make them more realistic, campaigns started and saved by users might need to be patched up with Mission Commander and adapted to the new DB changes.
-
The “Composite Download”, which shipped both ITO and ITO80s in a single .7z file for quicker installation, turned out to be causing CTDs.
Therefore, first installing stock ITO through its installer and then unzipping ITO80s into Data remains the official way of getting ITO80s to run properly.
-
This theater is epic! We went for a low low level bomb run on a Syrian radar station and then had some serious knife fights with Floggers and Fitters.
-
Glad for you, dear Stevie, that you have had some fun, out there.
On my little own, hhmmm… let me se what good have here and could be done with
We can talk about in a few days, I guess.
With best regards to all.
-
Version 1.1 released!
New Tacview add-on .xml file that fixes most objects’ labels, models and threat ranges. Installation instructions are in the shipped README.
The current campaigns had EAF Mig-21s in place of SAAF Mig-21s (and vice versa), this has now been fixed.
Campaigns started and saved by the user require a manual fix (if you’re bothered by the issue) i.e: via “Mission Commander>Units>Advanced Options>Change all Squadrons to”. -
Israel1980s v1.1 Training Missions Hotfix:
Deleted since the hotfix was implemented into v1.2
-
I could not get the IAF F-4e to frag a SEAD mission. However, DEAD missions will frag though . So I started poking around the DB and the aircraft data. Long story short I noticed a few issues with the IAF F-4e.
1. In the database, the aircraft dat associated to the IAF F-4e is the f4erok.dat, which is the Republic of Korea F4, not the f4eiaf.dat. Since the aircraft is mismatched to it’s .dat in the DB, editing the misTypeCapability in the f4eiaf.dat won’t change the missions type available. Not sure if this was intentional or not, but I changed in the DB to the f4eiaf.dat and was able to frag SEAD missions for the F-4.
2. Some of the entries in the f4eiaf.dat seem like they are accidentally missing a zero or two on the end.
For example.A2GHarmAlt 200 A2GHarmMinAlt 1000
probably should be
A2GHarmAlt 20000 A2GHarmMinAlt 10000
There’s a few more like this for bombs too. Those are important because they define the AI attack profile for the various weapons. I don’t think you want the F4 dropping to 200 feet to fire AGM 78’s or 45’s
3. In the f4eiaf.dat the max number of Anti radiation missiles is set to 0. For the A-4 it’ set to 4.
maxNumARMs 0
Not sure if this means no limits on ARMS carried or none are carried. However it would probably be a good idea to limit it to 2 on F4e IAF. As the AGM 78 is a big boi and it can cause takeoff issues given some of the shorter runways.
Thanks for all the work on this. Love the mod. If you need testers or trouble shooters let me know, happy to help.
mandatory pic of sexy as SEAD work.
-
Hello - for us non-techy dummies, could someone dumb this down and provide “clear” step by step instructions on how to install.
For example1.) If you don’t already have ITO, do ABC.
2.) IF you already have ITO and just need to install update (i.e v1.1), do XYZ.Please list where to download to, what folder, do we delete anything, etc……
Thank you -
Hello - for us non-techy dummies, could someone dumb this down and provide “clear” step by step instructions on how to install.
For example1.) If you don’t already have ITO, do ABC.
2.) IF you already have ITO and just need to install update (i.e v1.1), do XYZ.Please list where to download to, what folder, do we delete anything, etc……
Thank youThe “How to install:” section literally does all of that, you need stock-ITO to run ITO80s. What about it isn’t clear?
If you’re asking about updating ITO80s, simply:
- back up the TEs that you want to keep
- delete “Add-On Israel1980s”
- extract the new Israel1980s version from the latest download into Data
Alternatively, a lesser “safe” method of updating is to just extract Israel1980s into Data and overwrite its existing files.
-
I could not get the IAF F-4e to frag a SEAD mission. However, DEAD missions will frag though . So I started poking around the DB and the aircraft data. Long story short I noticed a few issues with the IAF F-4e.
…
Thanks for the feedback. I didn’t reply yet because I was working on other stuff, let me catch up:
I did indeed neglect to add the SEAD mission type to the F-4 IAF’s misTypeCapability string, it will be fixed.
- Turns out this is an ITO issue, the file has been present since before Israel1980s was created, but never properly integrated as you point out.
I will integrate that change into the next ITO80s version, while encouraging you to also point this issue out to vAiCon in the main ITO thread. - I agree on the “A2GHarmAlt” value but not on “A2GHarmMinAlt” (by referencing the KTO values for F-4s), I’m pretty sure “A2GHarmMinAlt” defines the minimum required height AGL to release an ARM, similar to how you need to climb to 1000ft to release the AGM-84 Harpoon.
I’ll increase the first to 20000, but leave the second value at 1000 like it is by default. - That issue was carried over from ITO as well, I presume it was missed when “f4erok.dat” was copied into “f4eiaf.dat”. I’ll set it to 2 like you suggested.
Thanks again! Testing and troubleshooting is always encouraged. If you want to contribute more, feel free to fork the GitHub repository, implement fixes and create a pull request.
Cheers!
- Turns out this is an ITO issue, the file has been present since before Israel1980s was created, but never properly integrated as you point out.
-
Thanks for the feedback. I didn’t reply yet because I was working on other stuff, let me catch up:
I did indeed neglect to add the SEAD mission type to the F-4 IAF’s misTypeCapability string, it will be fixed.
Cheers!
You may just want edit the misTypeCapability in F4EROK.dat, Instead of replacing F4EROK with F4EIAF in the DB. I had some texture issues with the F-4 after I changed it to f4eiaf.dat, The landing gear went missing on the ground. I think the ROK F-4 is better integrated into 4.35 so you’ll probably save a lot of time and headache by just keeping the IAF F4 tied to the ROK.
I spent the better part of the evening trying to fix the texture issue, I don’t think there is a way to do it without either altering the base Israel theater or adding another big DB file to your mod. I know the goal was to keep this mod as light as possible, so I just reverted to base with an edited ROK-F4 with expanded mission capabilities. The evening wasn’t a total loss though. I managed to implement this loadout
in game.
-
You may just want edit the misTypeCapability in F4EROK.dat, Instead of replacing F4EROK with F4EIAF in the DB. I had some texture issues with the F-4 after I changed it to f4eiaf.dat, The landing gear went missing on the ground. I think the ROK F-4 is better integrated into 4.35 so you’ll probably save a lot of time and headache by just keeping the IAF F4 tied to the ROK.
After a bunch of trial and error I found which exact part of the F-4E IAF ACData file causes the landing gear issue, fixed it by replacing it with this part of the F-4E EAF ACData (formerly F-4E ROK):
#----------------------------------------------------- # Aircraft #----------------------------------------------------- typeAC 11 isComplex 1 irSignature 1.5 visSignature 1.5 #-----------------------------------------------------
Thanks for the A-4 pic, I’ll update the loadout options based on that evidence.
-
After a bunch of trial and error I found which exact part of the F-4E IAF ACData file causes the landing gear issue, fixed it by replacing it with this part of the F-4E EAF ACData (formerly F-4E ROK):
#----------------------------------------------------- # Aircraft #----------------------------------------------------- typeAC 11 isComplex 1 irSignature 1.5 visSignature 1.5 #-----------------------------------------------------
Thanks for the A-4 pic, I’ll update the loadout options based on that evidence.
Just an FYI I had to add the LAU 88 in the racks to get the mavs look right.
-
Just an FYI I had to add the LAU 88 in the racks to get the mavs look right.
Yup, noticed. Already added both the LAU-117 and LAU-88, thanks for the heads up anyway.
-
Version 1.2 released!
Integrated the changes brought by ITO v1.05.2 + some minor fixes.
-
Version 1.3 released!
Easy identification of the currently installed version is now possible via the main menu background or theater selection list.
-
I appreciated particularly those specific TacView folder and detailed instructions very much.
That’s the way to do things. Bravo, dear Rusher, always accurate and so careful for all details!
With best compliments and regards.