Israel 1980s for BMS 4.35 - UOAF edition
-
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.
-
Version 1.3 released!
Easy identification of the currently installed version is now possible via the main menu background or theater selection list.
Does this replace original Add-On Israel1980s ? folder name ‘Israel1980s-main’ in zip file so how to install? Thanks
-
To your questions, dear zamcesarc:
- yes, it does (as its previous versions);
- in the zipped file downloaded I found no folder what that name you reported. I extracted the “Add-On Israel1980s” in the usual Data folder, and that was all.
Hope this may help you a bit. Please feel free to ask more, if in need.
With best regards.
-
Problem: In the campaign, the Ai would not generate SEAD or strike missions for the IAF F-4E. Just wanted to say that this problem has nothing specific to do with your mod. It is global across BMS, every F-4 is set to Fighter, except the F-4 G
Fix: 3 parts.
1. Change the Class subtype in database from 6, Fighter to 7, Fighter Bomber for all the airplane and flight entries
2. Edit the squadron entries, change subytype 8 fighter to type 9 fighter bomber
3. Update teplanes.lst to reflect DB changes.
// F-4E IAF Phantom Will Auto Frag Attack Missions 1 7 5 9 21837 617 10077 // F-4E Phantom EAF Will Only Frag Fighter Missions 1 6 44 8 21134 616 10077
-
thanks:birt:
-
Problem: In the campaign, the Ai would not generate SEAD or strike missions for the IAF F-4E. Just wanted to say that this problem has nothing specific to do with your mod. It is global across BMS, every F-4 is set to Fighter, except the F-4 G
Thanks for the feedback! Sadly it took me a bit to find some time to implement your fix, but here we go.
I followed your instructions, but oddly enough I’m still running into some issues.
I changed the SubType to “Fighter Bomber” for all F-4 IAF vehicle/flight/squadron CT entries and adjusted “teplanes.lst”, but when starting a campaign to test it, F-4 IAFs still only get fragged for AA work in Escort/CAP missions, it seems like only A-4s and F-16D-30s get assigned SEAD missions.How exactly did you verify the effects of your fix?
-
Thanks for the feedback! Sadly it took me a bit to find some time to implement your fix, but here we go.
I followed your instructions, but oddly enough I’m still running into some issues.
I changed the SubType to “Fighter Bomber” for all F-4 IAF vehicle/flight/squadron CT entries and adjusted “teplanes.lst”, but when starting a campaign to test it, F-4 IAFs still only get fragged for AA work in Escort/CAP missions, it seems like only A-4s and F-16D-30s get assigned SEAD missions.How exactly did you verify the effects of your fix?
Sorry, I forgot a step. In the Units tab of the editor, you also have to adjust the roll score for the aircraft. On the left the F-4E IAF is set to run a variety of missions. On the right the EAF will, likely, only frag CAP and escort missions.
-
On the right the EAF will, likely, only frag CAP and escort missions.
Ah, I see you increased the F-4E IAF squadron’s SEAD stat, default is 5, just like the F-4E EAF.
I checked that value, but I guess 5 just isn’t enough to auto-frag SEAD in a noticeable way, I’ll try out your values next.EDIT: increasing the SEAD stat for flight and squadron fixed it, I also had to increase the subtype values to last+1 after switching to the new “fighter bomber” category and update the category numbers in “VALIDAC.ACT” and “teplanes.lst”.
Again, thanks a lot for the feedback! -
Version 1.4 released!
New aircraft, the F-16C blk32 EAF Aggressor, which is identical to the stock EAF blk32, but shows up as “29” on RWRs.
Additional battalion unit composition fixes to improve realism in Serpent’s Sting.
Fixed F-4E IAF not being auto-fragged for SEAD, thanks Gastone.
-
v1.4 Hotfix-1
Deleted, fixes shipped with v1.5