Jump to content
Sign in to follow this  

Recommended Posts

Hello everyone,


I have a question about the location of weapons .ini files.  I have been looking for it using CAT extractor.  I am unable to find the .ini files for the weapons in SF2.  May I ask if anyone know where I can find it?

If someone knows which weapons pack is up-to-date and is released for SF2, please let me know too.  I will contact author about tweaking their .ini for weapons, respectfully.  If the permission is approved, I will start .ini dancing through a long list of weapons.

The information and advice are much appreciated, as always.  I am still looking for files again in SF2. 

I am working on the project that sorts the weapon list like I did with the aircraft list.

Cheers!

Edited by Eagle114th

Share this post


Link to post
Share on other sites

6 hours ago, ravenclaw_007 said:

Folder ObjectData001 , WEAPONDATA.ini

Sir, thank you very much!  I am going to roll my sleeves again and start working on this project. 

By the way, I am a fan of your weapon pack series work.  I found it recently on this forum.  It looks great!

Share this post


Link to post
Share on other sites

I have a problem with the updated Weapondata.ini.  After finishing editing and renaming all weapons in weapondata.ini, I moved both weaponsdata.ini / DAT files to SF2 -> Objects -> Weapons -> Weapondata and started SF2.  It appears that not all ordinance name is updated in SF2 yet, only a few.  Here is screenshot
 

img00002

 

Notice that only a few weapons with new names show up while the rest still show an original name. 

For example, for AIM-7E Sparrow, I renamed it as:

(AAM) AIM-7E Sparrow (SARH) and it still shows up as AIM-7E Sparrow.  Am I doing something else wrong? 
 

[WeaponData028]
TypeName=AIM-7E-4
FullName=(AAM) AIM-7E-4 Sparrow (SARH)
ModelName=aim-7e
Mass=193.690002
Diameter=0.200000
Length=3.670300
SubsonicDragCoeff=0.440000
SupersonicDragCoeff=0.615000
AttachmentType=USN
SpecificStationCode=
NationName=USN
StartYear=1974
EndYear=1980
Availability=2
BaseQuantity=6
Exported=TRUE
ExportStartYear=1974
ExportEndYear=0
ExportAvailability=2
WeaponDataType=1
RailLaunched=FALSE
RocketPod=FALSE
Retarded=FALSE
FinStabilized=TRUE
SpinStabilized=FALSE
HasGrowl=FALSE
EffectClassName=MediumMissileEffects
ReleaseDelay=0.200000
WarheadType=0
Explosives=30.000000
FusingDistance=2.000000
ClusterBomblets=0
ClusterDispersion=0.000000
GuidanceType=12
Accuracy=60
MaxTurnRate=15.000000
MaxLaunchG=5.000000
LockonChance=80
LaunchReliability=75
ArmingTime=1.000000
SeekerFOV=5.000000
SeekerGimbleLimit=46.000000
SeekerTrackRate=16.000000
SeekerRange=28000.000000
CLmax=14.000000
MinFreq=0.000000
MaxFreq=0.000000
MinLaunchRange=500.000000
MaxLaunchRange=28000.000000
Duration=70.000000
CounterCountermeasure=70.000000
NoiseRejection=30.000000
CapabilityFlags=0x00000008
LoftAngle=0.000000
DescentAngle=0.000000
MaxLoftAltitude=0.000000
BoosterStart=0.500000
BoosterDuration=2.800000
BoosterAccel=21.600000
BoosterEffectName=MissileFireEffect
BoosterSoundName=Missile
BoosterNodeName=
BoosterPosition=0.000000,-1.835150,0.000000
SustainerDuration=0.000000
SustainerAccel=0.000000
SustainerEffectName=
SustainerSoundName=
SustainerPosition=0.000000,-1.835150,0.000000
InFlightEffectName=MissileInFlightEffect
InFlightSoundName=
ReleaseAnimationID=-1
EODisplayFlags=0
CEP=0.000000

 

Edited by Eagle114th

Share this post


Link to post
Share on other sites

This "new" system may not work due to how the cat file system works. 

You'll probably have to make a folder for every single weapons listed. Inside that, you'll need all new inis and data inis for every single weapon (including stock ones) with this "new" naming system.

Typename= would probably stay the same, as that's what's being read by the loadout ini (of each and every single aircraft -- pray that you don't have to edit them, as well). The FullName=, as you know, and have editied, is what's seen on the loadout screen. It should work as you wish

BTW, editing the weaponsdata ini hasn't been needed since SF2 came out. You folderize all the new weapons and place them in the /Objects/Weapons folder. It's been a 'drag and drop' since day1. Hence, what I'm thinking that you have to do the whole thing from scratch, individually folderized.

  • Thanks 1

Share this post


Link to post
Share on other sites
5 minutes ago, Wrench said:

This "new" system may not work due to how the cat file system works. 

You'll probably have to make a folder for every single weapons listed. Inside that, you'll need all new inis and data inis for every single weapon (including stock ones) with this "new" naming system.

Typename= would probably stay the same, as that's what's being read by the loadout ini (of each and every single aircraft -- pray that you don't have to edit them, as well). The FullName=, as you know, and have editied, is what's seen on the loadout screen. It should work as you wish

BTW, editing the weaponsdata ini hasn't been needed since SF2 came out. You folderize all the new weapons and place them in the /Objects/Weapons folder. It's been a 'drag and drop' since day1. Hence, what I'm thinking that you have to do the whole thing from scratch, individually folderized.

Understood, your advice is much appreciated. 

I will do this way.  I will do a few experiments with the AIM-9s and AIM-7s family first.  Then see how it goes. If it all works out very well, then I will go this way.

Cheers!

  • Like 1

Share this post


Link to post
Share on other sites

GOOD NEWS!  Looks like it is working! I was renaming all AIM-9s family in SF2 in a method as Wrench explained.  I am able to display all AIM-9s updated names!

img00004

  • Like 1

Share this post


Link to post
Share on other sites

It appears that there is probably a bug with Mk.20 Rockeye II.  I renamed Mk.20 Rockeye II, it made two names with and without new names at the same time.  I did double-checked everything and still is confused by this.  Another ordinance works successfully though.  Can anyone test and see if anyone experiences the same problem with Rockeye II?

I placed the following three files into MK20_ROCKEYE_II folder in Weapons folder (SF2):

MK20_ROCKEYE_II.INI
MK20_ROCKEYE_II_DATA.INI
ROCKEYE.BMP

MK20_ROCKEYE_II.INI CODES:

[WeaponData]
ObjectDataFile=MK20_ROCKEYE_II_DATA.INI

[LOD001]
Filename=rockeye.lod
Distance=100

[LOD002]
Filename=rockeye_LOD2.lod
Distance=250

[LOD003]
Filename=rockeye_LOD3.lod
Distance=1000

[Shadow]
CastShadow=TRUE
ShadowCastDist=10000
MaxVisibleDistance=100


MK20_ROCKEYE_II_DATA.INI codes:
 

[WeaponData001]
TypeName=Rockeye
FullName=(CBU) Mk.20 Rockeye II
ModelName=rockeye
Mass=216.000000
Diameter=0.332000
Length=2.337000
SubsonicDragCoeff=0.224000
SupersonicDragCoeff=0.788000
AttachmentType=NATO
SpecificStationCode=
NationName=USAF
StartYear=1968
EndYear=1996
Availability=2
BaseQuantity=12
Exported=TRUE
ExportStartYear=1968
ExportEndYear=1996
ExportAvailability=2
WeaponDataType=0
RailLaunched=FALSE
Retarded=FALSE
FinStabilized=TRUE
SpinStabilized=FALSE
EffectClassName=ClusterBombEffects
DragAreaMultiplier=1.000000
WarheadType=9
Explosives=100.000000
FusingDistance=100.000000
ClusterBomblets=50
ClusterDispersion=0.500000
GuidanceType=0
Accuracy=0
MaxTurnRate=0.000000
MaxLaunchG=0.000000
LockonChance=0
LaunchReliability=0
ArmingTime=0.000000
SeekerFOV=0.000000
SeekerGimbleLimit=0.000000
SeekerTrackRate=0.000000
SeekerRange=0.000000
LiftDragRatio=4.000000
ReleaseAnimationID=1
ReleaseAnimationTime=0.200000
ReleaseAnimationDelay=0.100000
EODisplayFlags=0
CEP=20.000000


Here is a screenshot with the strange bugs with Mk.20 Rockeye II:

img00003

Share this post


Link to post
Share on other sites
1 hour ago, Eagle114th said:

I placed the following three files into MK20_ROCKEYE_II folder in Weapons folder (SF2):

Why? The Rockeye is a stock weapon. By doing what you did, you actually created another copy of the weapon, and you modified this copy, not the original weapon.

If your plan is to rename all stock weapons, your Weapons folder must be clean, you must edit only the WeaponData.ini file. Any other weapon subfolders you add may create additional, unwanted copies of stock weapons

  • Thanks 1

Share this post


Link to post
Share on other sites
8 hours ago, Menrva said:

Why? The Rockeye is a stock weapon. By doing what you did, you actually created another copy of the weapon, and you modified this copy, not the original weapon.

If your plan is to rename all stock weapons, your Weapons folder must be clean, you must edit only the WeaponData.ini file. Any other weapon subfolders you add may create additional, unwanted copies of stock weapons

I see, your advice is appreciated too.  Just for clarifying, weapondata.ini and .dat goes to this directory:

SF2 folder -> Objects -> Weapons -> Weapondata

Right? 

This is opportunities for me to learn more about how SF2 works, that way I can edit both weapondata.ini and making new folders for the proper situations. 

Edited by Eagle114th

Share this post


Link to post
Share on other sites

the .dat file is also no longer used

your pathway should be:

Objects --> Weapons --> Folder-name-of-weapon --> name-of-weapon.ini, name-of-weapon_data.ini. Also including any skins or lods, if aftermarket units. (exempt are cloned stock weapons, that reference 3W lods)

Do you know the format for the folderized _data ini???

example:

Quote

[WeaponData001]                      <-----THIS IS REQUIRED!!!
TypeName=B25RocketRack
FullName=B-25/PBJ Rocket Stubs
ModelName=P-51Rkt_Rack
Mass=20.000000
Diameter=0.000000
Length=0.866000
SubsonicDragCoeff=0.200000
SupersonicDragCoeff=0.770000
AttachmentType=USAF
SpecificStationCode=
NationName=USN,USMC,USAF
StartYear=1943
EndYear=1959
Availability=2
BaseQuantity=10
Exported=TRUE
ExportStartYear=1943
ExportEndYear=1960
ExportAvailability=1
WeaponDataType=2
RailLaunched=FALSE
RocketTypeName=HVAR5
NumRockets=1
ROF=0.000000
FireEffectName=RocketPodEffect
FireEffectTime=0.150000
FrontCoverNodeName=
RearCoverNodeName=
ShowRockets=TRUE
Rocket01Position=0.000000,0.000000,-0.150000

just making sure :)

  • Thanks 1

Share this post


Link to post
Share on other sites
1 hour ago, Wrench said:

the .dat file is also no longer used

your pathway should be:

Objects --> Weapons --> Folder-name-of-weapon --> name-of-weapon.ini, name-of-weapon_data.ini. Also including any skins or lods, if aftermarket units. (exempt are cloned stock weapons, that reference 3W lods)

Do you know the format for the folderized _data ini???

example:

just making sure :)

Roger that, added it to my notes.

Cheers!

Share this post


Link to post
Share on other sites
7 hours ago, Eagle114th said:

SF2 folder -> Objects -> Weapons -> Weapondata

Right? 

No. WeaponData.ini must be put simply inside the Weapons folder. That should be the only file in your Weapons folder, if you only want stock weapons with new names.

  • Confused 1

Share this post


Link to post
Share on other sites
1 hour ago, Menrva said:

No. WeaponData.ini must be put simply inside the Weapons folder. That should be the only file in your Weapons folder, if you only want stock weapons with new names.

I tried that with updated Weapondata.ini (All names are changed) and there are no changes occurring in SF2 yet.  Perhaps I should fly a mission and let SF2 'update' the text with new names from Weapondata.ini? I will run the further test again.

UPDATE:  This is strange.  If I put the folderized files in Weapons folder, it shows the changes in SF2 (With that buggy Mk.20 Rockeye II as mentioned above).  If I put only Weapondata.ini in, there are no changes occurring in SF2 yet. I must have been missing something.  I ran the tests with Weapondata.ini only by doing a quick mission and end it, no changes show up in loadout screen yet.

1

2

 

Edited by Eagle114th

Share this post


Link to post
Share on other sites

That is happening because you only edited the .ini file, while the .dat file is still that of the original game, hence you get the original names. You must re-save the .dat file with TW's Weapon Editor.

The .ini file is just an interface for the Weapon Editor, the stock weapon data that is truly read by the game is held in the .dat file.

Edited by Menrva

Share this post


Link to post
Share on other sites
1 hour ago, Menrva said:

That is happening because you only edited the .ini file, while the .dat file is still that of the original game, hence you get the original names. You must re-save the .dat file with TW's Weapon Editor.

The .ini file is just an interface for the Weapon Editor, the stock weapon data that is truly read by the game is held in the .dat file.

Menrva and Wrench,

I FINALLY DID IT.  I actually used TK weapon editor... OH BOY, I SHOULD HAVE used it earlier! (smacks my head on the desk).  THANK to you (Menrva) and Wrench for explaining how the system works in SF2.  The beauty of TK's Weapon Editor is that it automatically take care of everything I needed for it to do for me.  All I have to do is to edit all names from 'FULLNAME=" and use weapon editor to take care of the rest for me.  I will make sure to remember to use all tools available out there.

It is working beautifully in SF2 now!  Here are screenshot:

img00006

img00005

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Similar Content

    • By Eagle114th


      View File Screen Overhaul - (1920 x 1080)
      Strike Fighter Project 2 – Screen Overhaul v1.2 Customizable Edition
       
      The new version of SF2 Screen Overhaul 1.2 is now released.  Here is the following screen this mod completely overhaul:
       
      -          Main screen
      -          Single mission screen
      -          Mission editor screen
      -          Hangar (Default) screen
      -          Loadout screen
      -          Planning screen
      -          Roster screen
      -          Campaign screen
      -          Campaign editor screen
      -          Pilot records screen
      -          Options screen
       
      It does not yet cover another screen.  It is work in progress (WIP) for now.  What I am seeking for is feedback that will help me improving the mod further. It is one of my biggest projects I ever worked on for SF2. It gave me opportunity to grow a new skill I enjoy doing. 

      NOTE:  Now that SF2 Screen Overhaul is becoming a customizable version. If you make any mods that adds or change anything to this mod, please add my name and mod name to your credit part.
       
      You can contact me by PM in CombatAce (I am known as Eagle114th there) or Strike fighter series Discord chat (My username is Magic Dragon, so you can find me there too.)

      Version 1.2 NOTES:
       
      Buttons customization instruction:
      In Menu folder (SF2 mod folder), you will see various SF2 screen named as “BUTTONS_HANGAR, MAIN, OPTIONS, etc...), there are folders for each button.  In order, to change the color of buttons, go to one of button folder, you will see different folders for various color.  Copy the file from there and overwrite the files in any BUTTONS_(SCREEN) folder.

      For example, in BUTTONS_HANGAR, if I want to change the color of “LOADOUT” square button to blue; I go to the folder “LOADOUT”, then “Blue” folder, copy the files: LOADOUT0.bmp, LOADOUT1.bmp, and LOADOUT2.bmp.  Then I paste (Overwrite) the files in BUTTONS_HANGAR.
       
      Screens and Buttons customization Templates
      In different “BUTTONS_(different screen names)”, there are folder “_Templates’.  You can use it to change the designs, colors, or anything you want to do with the screen background or buttons. 
       
       


      This mod uses a font known as Orbitron.  I included it in _Fonts folder.

      I want to express my sincerely big THANKS to Menrva, Wrench, UllyB, Daddyairplanes, Wilches, JosefK, FalonCAF, and everyone else in CombatAce community for making this possible.  You all have been a huge help. 

      Because of Operation Desert Storm 30 years anniversary great mod, I was able to study the codes on how SF2 menu work, which led me into developing new menu for SF2.  This mod is truly fun to fly in SF2.  If anyone hasn’t tried it yet, I highly recommend it.


      There are detailed instruction that explains how to install in the proper ways in README file.  LEASE READ IT BEFORE INSTALLING! 

      I included the plans for the next version in the readme too.  

      The feedback are always welcomed!
       
       
       
      Submitter Eagle114th Submitted 05/18/2021 Category Menus  
    • By Eagle114th
      Strike Fighter Project 2 – Screen Overhaul v1.2 Customizable Edition
       
      The new version of SF2 Screen Overhaul 1.2 is now released.  Here is the following screen this mod completely overhaul:
       
      -          Main screen
      -          Single mission screen
      -          Mission editor screen
      -          Hangar (Default) screen
      -          Loadout screen
      -          Planning screen
      -          Roster screen
      -          Campaign screen
      -          Campaign editor screen
      -          Pilot records screen
      -          Options screen
       
      It does not yet cover another screen.  It is work in progress (WIP) for now.  What I am seeking for is feedback that will help me improving the mod further. It is one of my biggest projects I ever worked on for SF2. It gave me opportunity to grow a new skill I enjoy doing. 

      NOTE:  Now that SF2 Screen Overhaul is becoming a customizable version. If you make any mods that adds or change anything to this mod, please add my name and mod name to your credit part.
       
      You can contact me by PM in CombatAce (I am known as Eagle114th there) or Strike fighter series Discord chat (My username is Magic Dragon, so you can find me there too.)

      Version 1.2 NOTES:
       
      Buttons customization instruction:
      In Menu folder (SF2 mod folder), you will see various SF2 screen named as “BUTTONS_HANGAR, MAIN, OPTIONS, etc...), there are folders for each button.  In order, to change the color of buttons, go to one of button folder, you will see different folders for various color.  Copy the file from there and overwrite the files in any BUTTONS_(SCREEN) folder.

      For example, in BUTTONS_HANGAR, if I want to change the color of “LOADOUT” square button to blue; I go to the folder “LOADOUT”, then “Blue” folder, copy the files: LOADOUT0.bmp, LOADOUT1.bmp, and LOADOUT2.bmp.  Then I paste (Overwrite) the files in BUTTONS_HANGAR.
       
      Screens and Buttons customization Templates
      In different “BUTTONS_(different screen names)”, there are folder “_Templates’.  You can use it to change the designs, colors, or anything you want to do with the screen background or buttons. 
       
       


      This mod uses a font known as Orbitron.  I included it in _Fonts folder.

      I want to express my sincerely big THANKS to Menrva, Wrench, UllyB, Daddyairplanes, Wilches, JosefK, FalonCAF, and everyone else in CombatAce community for making this possible.  You all have been a huge help. 

      Because of Operation Desert Storm 30 years anniversary great mod, I was able to study the codes on how SF2 menu work, which led me into developing new menu for SF2.  This mod is truly fun to fly in SF2.  If anyone hasn’t tried it yet, I highly recommend it.


      There are detailed instruction that explains how to install in the proper ways in README file.  LEASE READ IT BEFORE INSTALLING! 

      I included the plans for the next version in the readme too.  

      The feedback are always welcomed!
       
       
       
    • By Eagle114th
      I did some experiment on converting the regular screenshot into 1970s and older photo style.  I thought "Why not?"  so here it is:

      Parked A-4s - Rregular screenshot

      Parked A-4s - 1970s style screenshot

      Parked A-4s - Older style screenshot


      Parked MiG-21s - Regular screenshot

      Parked MiG-21s - 1970s style screenshot


      Parked MiG-21s - Older style screenshot

    • By Eagle114th
      Good evening everyone,
      I have a few questions about MESSAGESYSTEMS.INI and .STR files;
       
      1) since I am looking for the way to do further changes to HUDDATA and GUI.  I did some researches and I found out that if I edit MESSAGESYSTEMS.INI, I will be able to do more customization to the in-flight screen.  I am unable to find MESSAGESYSTEMS.INI.  So where do I find it? I extracted flightdata and there is no MESSAGESYSTEMS.INI. Where can I find MESSAGESYSTEMS.INI?

      2) About .STR, I noted there are .STR on both flight and menu folders after extracting both using CAT extractor.  What kind of program is required, in order, to edit .STR files?  Or is there no way to mod them properly yet?

      As always, the information and advice are appreciated.

      Cheers!
       
    • By Eagle114th
      Hello everyone,
      While I was working on SF2 new MENU / GUI project, I realized that I really want to finish working on updating an ordinance list.  The reasons:

      I missed the old day of Jane's FA when I could view the list of ordinance that is separated between AA (Air to Air) / AS (Air to Surface).  I decided to work on it, so anyone who wants this can also enjoy SF2 with new ordinance list.  

      I created the notes with abbreviations I am using for the list.  The feedbacks are welcomed as always.  I will happily update the list if the community wants to see any abbreviations modified, changed, or added.  Here is the list:
      Abbreviations -------------------------------------------------------- <MISSILE PLATFORM - TYPES> AAM AIR TO AIR MISSILE ALCM AIR-LAUNCHED CRUISE MISSILE AGM AIR TO GROUND MISSILE ARM ANTI-RADIATION MISSILE ASM AIR TO SURFACE MISSILE AShM ANTI-SHIP MISSILE M-SAM MOBILE SAM SAM SURFACE TO AIR MISSILE <MISSILE - GUIDANCE TYPES> ARH ACTIVE RADAR HOMING CG COMMAND GUIDANCE CLOS COMMAND TO LINE-OF-SIGHT SARH SEMI-ACTIVE RADAR HOMING LG LASER-GUIDANCE LOSBR LINE-OF-SIGHT BEAM RIDING INS INERTIAL NAVIGATION SYSTEM IR INFRARED HOMING IIR IMAGING INFRARED GUI TGM TELEVISION GUIDANCE TV ELECTRO-OPTICAL GUIDANCE RA RADAR ALTIMETER GUIDANCE RC RADIO COMMAND RL RADIO LINK <BOMB - TYPES> CBU (CLUSTER BOMB UNIT) FFD FREE-FALL DEMOLITION GBU (GLIDE BOMB UNIT) GPB GENERAL-PURPOSE BOMB LGB LASER-GUIDED BOMB LDGPB LOW-DRAG GENERAL-PURPOSE BOMB NPB NAPALM BOMB PGM PRECISION GUIDED MUNITION <ROCKET - TYPES> AP ARMOR PIERCING FFAR FOLDING-FIN AIRCRAFT ROCKET HE HIGH EXPLOSIVE HVAR HIGH VELOCITY AIRCRAFT ROCKET <OTHER> DT DROP TANK ECM ELECTRONIC COUNTERMEASURES GP GUN POD RACK ORDINANCE RACK RL ROCKET LAUNCHER RP ROCKET PROJECTILE TGP TARGETING POD
      Here is the updated list of SF2 ordinances:
      NOTE: You will see duplicated names for drop tanks, don't worry about it.  It is connected to the aircraft.  You won't see duplicated drop tanks in SF2 Menu. This list is directly copied from weapondata. 
      The list is still WIP, there are probably mistakes I have not seen before.  So please let me know if you see anything needs fixing in the list.
       
      <AIR TO AIR MISSILES> (AAM) AIM-4D Falcon (IR) (AAM) AIM-7D Sparrow (SARH) (AAM) AIM-7E Sparrow (SARH) (AAM) AIM-7E-2 Sparrow (SARH) (AAM) AIM-7E-4 Sparrow (SARH) (AAM) AIM-7F Sparrow (SARH) (AAM) AIM-7M Sparrow (SARH) (AAM) AIM-7P Sparrow (SARH) (AAM) AIM-9B Sidewinder (IR) (AAM) AIM-9D Sidewinder (IR) (AAM) AIM-9E Sidewinder (IR) (AAM) AIM-9E-2 Sidewinder (IR) (AAM) AIM-9F Sidewinder (IR) (AAM) AIM-9G Sidewinder (IR) (AAM) AIM-9H Sidewinder (IR) (AAM) AIM-9J Sidewinder (IR) (AAM) AIM-9L Sidewinder (IR) (AAM) AIM-9M Sidewinder (IR) (AAM) AIM-9N Sidewinder (IR) (AAM) AIM-9P Sidewinder (IR) (AAM) AIM-9P-2 Sidewinder (IR) (AAM) AIM-9P-3 Sidewinder (IR) (AAM) AIM-9P-4 Sidewinder (IR) (AAM) AIM-9P-5 Sidewinder (IR) (AAM) AIM-54A Phoenix (SARH / ARH) (AAM) Matra R.530 (SARH / IR) (AAM) Matra R.530E (SARH / IR) (AAM) Matra R.550 Magic (IR) (AAM) Matra R.550 Magic 2 (IR) (AAM) Shafrir-1 (IR) (AAM) Shafrir-2 (IR) (AAM) Python-3 (IR) (AAM) Firestreak (IR) (AAM) Red Top (IR) (AAM) Sky Flash (SARH) (AAM) V3A Kukri (IR) (AAM) V3B Kukri (IR) (AAM) RS-2US "AA-1 Alkali-B" (LOSBR) (AAM) R-3S "AA-2 Atoll-A" (IR) (AAM) R-13M "AA-2 Atoll-D" (IR) (AAM) R-23R "AA-7 Apex-A" (SARH) (AAM) R-23T "AA-7 Apex-B" (IR) (AAM) R-24R "AA-7 Apex-C" (SARH) (AAM) R-24T "AA-7 Apex-D" (IR) (AAM) R-60T "AA-8 Aphid-A" (IR) (AAM) R-60M "AA-8 Aphid-B" (IR) -------------------------------------------- < BOMBS > (CBU) CBU-24B Cluster Bomb (CBU) Mk.20 Rockeye II (FFD) M-117 750-lb Bomb (GPB) AN-M57 250-lb Bomb (GPB) AN-M64 500-lb Bomb (GPB) UK 250-lb Bomb (GPB) UK 540-lb Bomb (GPB) UK 1000-lb Bomb (GPB) FAB-100 100-kg Bomb (GPB) FAB-250 250-kg Bomb (GPB) FAB-500 500-kg Bomb (LDGPB) Mk.81 250-lb Bomb (LDGPB) Mk.82 500-lb Bomb (LDGPB) Mk.82 Snakeye (LDGPB) Mk.83 1000-lb Bomb (LDGPB) Mk.84 2000-lb Bomb (LGB) GBU-12 Paveway (LG) (LGB) GBU-12 Paveway II (LG) (LGB) GBU-10 Paveway (LG) (LGB) GBU-10 Paveway II (LG) (NPB) BLU-1 Napalm (PGM) Mk.1 Walleye I (TGM) (PGM) Mk.5 Walleye II (TGM) (PGM) Mk.21 Walleye I ERDL (TGM) (PGM) Mk.23 Walleye II ERDL (TGM) (PGM) GBU-8 HOBOS (TGM) -------------------------------------------- <AIR TO GROUND MISSILES> (ARM) AGM-45A Shrike (ARM) AGM-45B Shrike (ARM) AGM-78A Standard ARM (ARM) AGM-78B Standard ARM (ARM) AGM-78C Standard ARM (ARM) AGM-78D Standard ARM (AShM) AGM-84A Harpoon (RA / ARH) (AShM) AGM-84C Harpoon (RA / ARH) (AShM) AGM-84D Harpoon (RA / ARH) (AShM) K-10S "AS-2 Kipper" (INS / RL) (AShM) Kh-22 "AS-4 Kitchen" (INS / ARH) (ALCM / AShM) KSR-5 "AS-6 Kingfish" (INS / ARH) (ASM) AGM-65A Maverick (TV) (ASM) AGM-65B Maverick (TV) -------------------------------------------- <ROCKET LAUNCHERS> (RL) LAU-3 Rocket Pod (RL) LAU-10 Rocket Pod (RL) LAU-32 Rocket Pod (RL) LAU-33 Rocket Pack (RL) Matra 155 Rocket Pod (RL) 2" Microcell Rocket Pack (RL) 2" Microcell Rocket Pack (RL) JL-100 Rocket Pod (RL) UB-16-57 Rocket Pod (RL) UB-32-57 Rocket Pod -------------------------------------------- <GUN PODS> (GP) SUU-11 Gun Pod (7.62x51mm) (GP) SUU-23 Gun Pod (20mm) (GP) Mk.4 Gun Pod (20mm) (GP) 30mm Aden Gun Pack -------------------------------------------- <DROP TANKS> (DT) 75-gal Drop Tank (DT) 100-gal Drop Tank (DT) 150-gal Drop Tank (DT) 170-gal Drop Tank (DT) 195-gal Drop Tank (DT) 175-gal Ventral Drop Tank (DT) 200-gal Drop Tank (DT) 230-gal Drop Tank (DT) 250-gal Drop Tank (DT) 275-gal Drop Tank (DT) 280-gal Drop Tank (DT) 300-gal Drop Tank (DT) 335-gal Drop Tank (DT) 370-gal Drop Tank (DT) 450-gal Drop Tank (DT) 500-ltr Supersonic Tank (DT) 600-gal Drop Tank (DT) 610-gal Drop Tank (DT) 625-ltr Drop Tank (DT) 650-gal Drop Tank (DT) 1300-ltr Drop Tank (DT) 1700-ltr Drop Tank (DT) 293-gal Drop Tank -------------------------------------------- <RACKS> (RACK) A/A37B-5 TER (RACK) A/A-37B-6 MER (RACK) NAPGACH (RACK) Harrier Twin Store Carrier (RACK) Mirage Twin Bomb Rack (RACK) LAU-88A/A (RACK) LAU-105 DRA (RACK) F-105 Twin AIM-9 Rail (RACK) RPK10 Bomb Rack Fuel (RACK) APU-60-II -------------------------------------------- <TARGETING POD> (TGP) AN/AVQ-23A/B Pave Spike -------------------------------------------- <ECM> (ECM) AN/ALQ-71 (ECM) AN/ALQ-101 (ECM) AN/ALQ-119 (ECM) AN/ALQ-131 -------------------------------------------- <SAM> (SAM) RIM-2F Terrier HTR-3 (SARH) (SAM) RIM-7E Sea Sparrow (SARH) (SAM) RIM-7H NATO Sea Sparrow (SARH) (SAM) RIM-66B Standard MR (SARH) (SAM) "SA-2B Guideline Mod 1" (CG) (SAM) "SA-2C Guideline Mod 2" (CG) (SAM) "SA-2E Guideline Mod 4" (CG) (SAM) "SA-2F Guideline Mod 5" (CG) (SAM) "SA-6A Gainful" (CG / SARH) (SAM) "SA-N-3 Goblet" (RC / SARH) -------------------------------------------- <MOBILE SAM> (M-SAM) "SA-8 Gecko Mod 0" (CLOS) (M-SAM) "SA-8B Gecko Mod 1" (CLOS) (M-SAM) "SA-N-1B Goa" (CLOS) (M-SAM) "SA-N-4 Gecko" (CLOS)
      I will share the progress of this mod through time.
×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..