Eagle114th

That is noted and thank you for correcting me. As always, I learn new things everyday. Cheers!

AH! I SEE NOW! This may have solved the problems I was having. I will test it. (Fingers crossed) Eagle114th

Ah I see. Since you don't have F-4K and F-4M DLC, you can't help me in this situation. I need someone who has F-4K and F-4M DLC to see if their F_4K and F-4K_75 are bugged too. I still appreciate your help. Cheers!

May I ask, do you have SF2 + ALL expansion pack + ALL DLCs? I just realized I forgot to add to the readme stating that this mod is bieng built with SF2 Complete Edition. Eagle114th

I appreciate your help. May I ask if you can experiment it on F-4K, F-4K_75, and F-4K_80? I have done the same with all of them. Only F-4K_80 works. I will re-test with all three planes. Eagle114th

I think you installed the mods in the wrong way. I recommend you to clean theSF2 mod folder and start over. Make sure you read the README carefully. Eagle114th

The problem with F-4K and F-4K_75 is that if you use SpecificStationCode, their weapon station no longer works or the weapon does not show up on the loadout screen, even when you change the nation or attachmentType. I am able to use SpecificStationCode with F-4K_80 successfully. That surprised me. Hence I think that F-4K and F-4K_75 are glitchy and need patches to fix it. Eagle114th

This is even more strange; My new codes posted abover does NOT work with F-4K or F-4K_75. It still work with F-4K_80. TW F-4K and F-4K_75 are glitchy. F-4K_80 is stable. So be careful when messing with F-4K and F-4K_75 weapon station codes. I am not going to mess with any UK F-4s, I'll leave them be and only tweak the loadout. Eagle114th

Looks like I fixed the problems by changing "UK" to RAF,RoyalNavy and the weapon now appears on loadout screen. Here is the codes: [SidewinderStation1] SystemType=WEAPON_STATION StationID=10 StationGroupID=2 GroupLimit=3 StationType=EXTERNAL AttachmentPosition=-2.24,2.63,-1.18 AttachmentAngles=0.0,-1.0,85.0 LoadLimit=120 DiameterLimit=0.15 AllowedWeaponClass=IRM AttachmentType=RAF,RoyalNavy ModelNodeName=missile_rails_L PylonMass=39.46 PylonDragArea=0.001 LaunchRailNodeName= MinExtentPosition= MaxExtentPosition= SpecificStationCode=RAF_RN_IRM [SidewinderStation2] SystemType=WEAPON_STATION StationID=11 StationGroupID=2 GroupLimit=3 StationType=EXTERNAL AttachmentPosition= 2.24,2.63,-1.18 AttachmentAngles=0.0,-1.0,-85.0 LoadLimit=120 DiameterLimit=0.15 AllowedWeaponClass=IRM AttachmentType=RAF,RoyalNavy ModelNodeName=missile_rails_R PylonMass=39.46 PylonDragArea=0.001 LaunchRailNodeName= MinExtentPosition= MaxExtentPosition= SpecificStationCode=RAF_RN_IRM [SidewinderStation3] SystemType=WEAPON_STATION StationID=12 StationGroupID=2 GroupLimit=3 StationType=EXTERNAL AttachmentPosition=-1.86,2.63,-1.18 AttachmentAngles=0.0,-1.0,-85.0 LoadLimit=120 DiameterLimit=0.15 AllowedWeaponClass=IRM AttachmentType=RAF,RoyalNavy ModelNodeName=missile_rails_L PylonMass=39.46 PylonDragArea=0.001 LaunchRailNodeName= MinExtentPosition= MaxExtentPosition= SpecificStationCode=RAF_RN_IRM [SidewinderStation4] SystemType=WEAPON_STATION StationID=13 StationGroupID=2 GroupLimit=3 StationType=EXTERNAL AttachmentPosition= 1.86,2.63,-1.18 AttachmentAngles=0.0,-1.0,85.0 LoadLimit=120 DiameterLimit=0.15 AllowedWeaponClass=IRM AttachmentType=RAF,RoyalNavy ModelNodeName=missile_rails_R PylonMass=39.46 PylonDragArea=0.001 LaunchRailNodeName= MinExtentPosition= MaxExtentPosition= SpecificStationCode=RAF_RN_IRM [WeaponData001] TypeName=AIM-9Gswift FullName=[IRM] AIM-9G (SWIFT) Sidewinder UK ModelName=AIM-9d Mass=89.360001 Diameter=0.127000 Length=2.830000 SubsonicDragCoeff=0.689000 SupersonicDragCoeff=0.811000 AttachmentType=NATO,RAF,RoyalNavy SpecificStationCode=RAF_RN_IRM NationName=RAF StartYear=1983 EndYear=1999 Availability=2 BaseQuantity=4 Exported=FALSE ExportStartYear=0 ExportEndYear=0 ExportAvailability=0 WeaponDataType=1 RailLaunched=TRUE RocketPod=FALSE Retarded=FALSE FinStabilized=TRUE SpinStabilized=FALSE HasGrowl=TRUE EffectClassName=SmallMissileEffects ReleaseDelay=0.800000 WarheadType=0 Explosives=5.000000 FusingDistance=6.000000 ClusterBomblets=0 ClusterDispersion=0.000000 GuidanceType=10 Accuracy=70 MaxTurnRate=18.000000 MaxLaunchG=10.000000 LockonChance=70 LaunchReliability=80 ArmingTime=0.500000 SeekerFOV=2.500000 SeekerGimbleLimit=40.000000 SeekerTrackRate=12.000000 SeekerRange=16000.000000 CLmax=14.000000 MinFreq=0.000000 MaxFreq=0.000000 MinLaunchRange=400.000000 MaxLaunchRange=16000.000000 Duration=55.000000 CounterCountermeasure=80.000000 NoiseRejection=60.000000 CapabilityFlags=0x00000280 LoftAngle=0.000000 DescentAngle=0.000000 MaxLoftAltitude=0.000000 BoosterStart=0.000000 BoosterDuration=4.700000 BoosterAccel=13.900000 BoosterEffectName=MissileFireEffect BoosterSoundName=Missile BoosterNodeName= BoosterPosition=0.000000,-1.456000,0.000000 SustainerDuration=0.000000 SustainerAccel=0.000000 SustainerEffectName= SustainerSoundName= SustainerPosition=0.000000,-1.456000,0.000000 InFlightEffectName=MissileInFlightEffect InFlightSoundName= ReleaseAnimationID=1 ReleaseAnimationTime=0.000000 ReleaseAnimationDelay=0.000000 EODisplayFlags=0 CEP=5.000000 Now I can see AIM-9G (SWIFT) without seeing another missiles, which is a good news! The most important note I learn today about SpecificCodes, only use what is shown in NATION.ini. Anything that is not there, do NOT use it. the code "UK" won't work with SpecificStationCode=". Eagle114th

Thank you for the feedback. Can you explain this problem in detail, please? I can not help if there is not enough information. Which plane were you flying? What kind of setting do you set in the graph? Are you running on a video card? The reason why I ask is that I don't have any problem when running SFCE mods. As soon I get answer from you, I will investigate in SFCE and see if I encounter the errors. Eagle114th

Yes, it does. It turns out that if you use SpecificStationCode with code "UK", it will NOT work at all. And I realized why; the "UK" is not even part of NATION, it is probably reserved codes written by TK inside the game engine that handles UK ordinances. And anything that is not listed in NATION.ini, you can not use SpecificStation. Eagle114th

Thank you for clarification. That is noted. I will make sure that all USN and USAF F-4s stay with AIM-9F except for F-4G. Cheers!

Good morning! Are you trying to change the initializing screen? If you do, you will need to meet this requirement for it to load in SF2: 1) MAKE SURE YOU BACK UP FOLDER "MENU", in case if you make a mistake or mess up the files. 2) IT MUST be in 1024 x 768 resolution 3) The file should be named as InitScreen.bmp With that, you will have a new initializing screen. Eagle114th

Wow that look more realistic and great! I am impressed with the details you worked on with the ground vehicles including AAA truck. Eagle114th

May I ask, you mean that any USN and USAF F-4s have the ability to carry AIM-7M? That is interesting. About AGM-78 and F-4G / A-6A and B, that is noted. Thank you for the information. I found out is that Israel and South Korea F-4s were modified to carry AGM-78s. Cheers

That is noted and thank you for the feedback. This is what I precisely need. I will see if I can use StationGroupID more than once, so I can ensure it does not overlap with other store while disabling AIM-9s from being mounted. Cheers

Hello everyone! Report for today: I have been quiet for a while. It has been a busy week with researching, talking with friends who have vast knowledge and experiences related to military aircraft, overhauling multi-nation F-4s, and overhauling the weapon pack so certain weapons are only available for certain aircraft. For example, the AGM-78 series are only available for A-6s, F-4G, and F-105G. At the same time, the only nations that operates AGM-78s outside of USAF and USN are South Korea and Israel. There is still a lot to do before I can finally move to A-4s, A-6s, A-7s, and other aircraft for weapon data and loadout.ini overhauls. You can see that the new loadout.ini are working now: ROKAF F-4D Phantom II with AGM-78s: ROKAF F-4E Phantom II There is one thing I realize, I often hit the wall where I need more information that is not easy to find. This is why when the next version of the beta gets released, the feedback will be very helpful for fixing the errors and inaccuracies in SFCE. Eagle114th

Thank you for the information. I appreciate it. PM sent. Eagle114th

That is noted and thank you for the information. Cheers!

Thank you and this meant a lot to me! With your message, I am inspired to work on this even further. Cheers!

Thank you very much for the information! This is a big help! I will happily re-work on C.12 weapon data and loadout. I also removed AIM-9P from Iranian F-4, so they only have AIM-4D, AIM-9E,and AIM-9J. (Please correct me if I am wrong), Iranian F-4D have AIM-4D, AIM-9E, and AIM-7C. Then their F-4E have AIM-7E / E-2, and AIM-9J. What kind of ECM did Iranian F-4 have? Cheers!

Hello everyone! I want to share this with everyone. It have been humbly learning progres since a few days working on F-4s LOADOUT.ini and researches. It is like Daddyplane said, researching and finding information take most of our times. He is right. I also want to admit that I previously thought F-4s had the ability to carry AIM-9M and AIM-7M. I was wrong and I am happy I did further research to ensure loadout is tweaked more accurately. Now with the tweaks done, the latest AIM-9s and AIM-7s F-4s can carry is AIM-9P and AIM-97F for the late 1970s to 1980s. However, I want to talk a bit more about F-4s. In the late-era SF2 F-4s, by default, they will have loadout with the AIM-9P and AIM-7F. What I realized is that AIM-9L was reserved for newer aircraft such as F-15s, F-16s, and other aircraft. However, you still can manually load AIM-9L on F-4s which actually happened rarely in real life. According to the research, in the Vietnam war, early F-4D was armed with AIM-4D Falcon. Then later in the 1969, they would get phased out while being re-wired to use Sidewinder. In SFCE, early F-4D (1966 - 1968) have loadout.ini to carry AIM-4D but you still can manually change load to AIM-9B or E. However, for next version of F-4D (67) and onward, will be loaded with sidewinder by default. Same thing with early F-4E. I want to talk about userlist. I can see how TK is being efficient with it as stated previously, there is pro and con to it. For pro part, it make it easy to clone aircraft with exact same aircraft data and weapon stations. The con part is that, it does not work with other aircraft that uses different weapons, including AAMs. For example, with Iranian F-4s, userlist allow Iranian F-4s to use all what USAF F-4s could use, which is historically inaccurate. I had to split various foreigner F-4s out from USAF F-4s, in order, to give them an accurate AAMs and updated loadout.ini. I wish TK is still working on SF2 so they could add this codes which would make userlist system being perfect and efficient. For example, if TK ever added an extra line like this in aircraft data ini. Original codes: [SidewinderStation1] SystemType=WEAPON_STATION StationID=10 StationGroupID=2 StationType=EXTERNAL AttachmentPosition=-2.24,2.63,-1.12 AttachmentAngles=0.0,-1.0,90.0 LoadLimit=90.72 AllowedWeaponClass=IRM AttachmentType=NATO,USAF ModelNodeName=missile_rails_L PylonMass=24.95 PylonDragArea=0.001 LaunchRailNodeName= MinExtentPosition= MaxExtentPosition= Updated codes with "Nation_" suffixes [SidewinderStation1] SystemType=WEAPON_STATION StationID=10 StationGroupID=2 StationType=EXTERNAL AttachmentPosition=-2.24,2.63,-1.12 AttachmentAngles=0.0,-1.0,90.0 LoadLimit=90.72 USAF_AllowedWeaponClass=IRM USAF_AttachmentType=NATO,USAF IRAN_AllowedWeaponClass=IRM IRAN_AttachmentType=IRAN EGYPT_AllowedWeaponClass=IRM EGYPT_AttachmentType=EGYPT ModelNodeName=missile_rails_L PylonMass=24.95 PylonDragArea=0.001 LaunchRailNodeName= MinExtentPosition= MaxExtentPosition= USAF_SpecificStationCode= IRAN_SpecificStationCode=AIM9_IRAN EGYPT_SpecificStationCode=AIM9_EGYPT That would make the user list system work well. Finally, another thing that got me stumped was researching the specific AAMs for various nations that use F-4s, such as Spain C.12, South Korea F-4, and others. Finally got an answer to it, thanks to friends who introduced me to this website: Sipri database website https://www.sipri.org/databases/armstransfers With this, you can find information on which specific AAMs are sent to nations for certain aircraft. With this, accurate information can be found! This is where I find out that C.12 (F-4C) got orders of AIM-9P only, along with a few variants of AIM-7s. UPDATE: It turns out that even the trade registry database does not cover everything. It is like if I found pieces of dinosaur fossils with some parts missing. I would have to theorize how dinosaur looks like based on what I have. Same thing with the data on various aircraft loadout. I am unable to find the earlier IRM for C.12, and in order, to fill the missing gap for IRM needed for F-4C, it makes logical sense that C.12 would have AIM-9J prior to AIM-9P. I have to admit this project is not perfect but I do my best. I always learn new things everyday. Eagle114th

Hello everyone, I am currently working on overhauling loadout for various aircraft, there is one thing I am wondering about. Does SF2 automatically replace IRM or SAHM with newer one as soon they are available? Or are they stuck with one variant of IRM or SAHM until their service year runs out? Eagle114th

Hello everyone! Report for today: After asking questions about the loadout system in SF2. I noticed that AI keeps one variant of AAM based on what is read from loadout.ini. That breaks the immerisve experience for me, especially when they use one AAM until end of the service when newer AAM already come out. After asking the question at this thread: https://combatace.com/forums/topic/97452-question-about-loadoutini-being-automatic-with-weapons/ This confirms the concern I had with the loadout system. This is what gives me more reasons to overhaul AAM in loadout, so aircraft use newer variants or another type of AAM based on the nation's aircraft and years. After working on Iranian and Egyptian F-4Es, I decided to check USN and USAF F-4s. This is what I saw, only AIM-9B for early F-4B when they could use AIM-9B and then AIM-9D as soon they become available. Same thing with the AIM-7s situation by changing from AIM-7D to AIM-7E and then E-2, and the next variants. || So I rolled the sleeves and started working on all USN F-4Bs, then J and N variants. I am quite happy with the result. However, since I am not an expert with the air-to-ground ordinances, I will leave them alone for now. When I get the information and help with it, I will happily overhaul that part. Here is an example with F-4J Phantom II, this is the following AAM they will shift through from 1966 to 1983: Now that USN F-4s are completed, USAF F-4s are being worked on at the moment. There is another thing that also bothers me and that is how the vortex work. The higher speed I go, the more vortex stretch backward and would sink through the wing toward the bottom when pulling high Gs. There is one thing that gave me an "AH" moment. I am going to study the F-16 vortex and see if I can make the vortex stay in place at any speed. When AAM loadout overhaul for other aircraft that went through an overhaul and wing vortex being done, the work on Hawker Hunter and other aircraft will be restored. I have no idea how long this may take and it will be worth the wait. Eagle114th

Thought so. Thank you for the explanation. That is what I was concerned about. The reason why I ask is that I noted how AI keeps using the same variant of AAM until service run out, which breaks an immersive for me. That gives me more reasons to work on aircraft loadout so they will load the next variant or other types of IRM depending on the years. Cheers