Israel 1980s for BMS 4.35 - UOAF edition
-
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
-
Version v1.5 released!
Fixed the F-16C-32 EAF Aggressor using the USAF blk50 cockpit and wings model and F-4E IAF causing a CTD when added to a dogfight match.
Also fixed the IAF Museum being on top of Hatzerim AB’s Runway 10R… moved it 1km north-east where it belongs.
-
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”. -
-
-
-
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”. -
AWESOME!! is it save-game compatible with 1.6?
-
@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. -
-
-
-
117th squadron at Operation Lox has unchecked by default “Set by HQ”. That’s the reason, if someone is wondering why packages are not created at the start of the campaign.
Loving this new campaign with only rear aspect missiles
-
Has this been ported over to 4.36?
-