UllyB

ok, thank you for your precious insight. I will take a look and I hope I won't me messing those files /values up too much.

alright,alright...If presence of a see is request, that condition is fullfilled, cause I play in WOI. I just play missions in WOI, where there is see and should be virtual ship targets random generated, of course. The type of plane shouldn't matter (with a few obvious exceptions, of course, I won't be making a loadout for transport planes, for instance etc, I am talking about usually multirole fighters here), should it ? They are add on-ed planes, all kind of (F5s, F4s, Ja-37 etc). I noticed that if I add antiship loadout to one which INITIALLY didn't have that in dataini.file declared, when I when I enter the game and look to loadouts, they look like the recon one as you pointed out. So, bottom line, following your logic, it shouldn't be problems here (there is a sea in this map and plenty of virtual ship targets), BUT there are. So it means , that this is not it, it has to be the terrain restrictions or something else. That's why I asked if there is a setting which it can be modified. Long story short, if you wanna test what I said, and that won't work on WOI map , try the F4-E Iran add-on plane (it's just one made) and you will see that if you add/declare in its datini file that can make antiship missions and you specifiy its load in loadout.ini, when entering game , it will show the recon load no matter what. I hope I gave you as much info I could think of. PS- all other add -on multirole fighters I tested so far (except the F-4e Iran) which have declared in their dataini file that can make antiship missions, are working (antiship loadouts appear correct in the loading window)

Thank you for the help. So that means that a specific file into terrain CAT file has those settings (what loadout is allowed and what is not) ? Is it hardcoded or can be modified ?

Is there a way, please, to modify the fonts from the window which appears when a AI enemy aircraft is targeted ? if so, what is the name of the file (and where is it) and what paragraph does concern exactly that ? Thank you.

Thank you very much Sir. Much appreciated.

After a week searching and exploring I discovered, I think, the reason. I guess that the aircraft models have already fixed what kind of role it has (CAS, Antiship etc). Having in aircraft folder a loadout.ini file, I guess it means that it overrides any other settings, if there areany in the CAT file concerning the loadout.ini so, through elimination I think that I found the reason why I get for antiship or any other role that is not supposed to be for that aircraft, the CAS settings etc. Can anyone confirm that or I am wrong ?

No one knows ? No one encountered that ever ?

Can anyone, please do this skin for stock F-4E ? I tried but I am not skilled enough to match it.

I thought that this skin, if made, it could be a good addition to the combatace heritage. Do you think that the skin is ugly, is that you are trying to say ? It's not about wishing something badly like a stupid kid, I just like the skin how it looks and I can't make it on my own, that's all. If I would had proper skill to do exactly that, I wouldn't hesitate a second to make this skin and share it with rest of the crowd. Maybe someone will take it into consideration one day...

I ran it on Win 7 64x without any problems and never crshed once ! I set the compatibility to Win XP(service pack 3)

I want to correct an error: the SEAD preload is the same for antiship.

Where (in wich pack) can I find the avq23sight1.tga file please ? I noticed that is listed in F-14D data.ini file and I guess it should be in flight folder or am I mistaken ? Also could you please explain what exactly is with this file and it does exactly ? Thank you.

I have this F-15E I downloaded from here and I can't make it load the GBU-10 and GBU-12 (LGB) bombs through loadout.ini and I don't know where I am wrong, I tried everything and I failed. The LGB ammo is there (stations can support LGBs weight, the stations have LGB enabled etc) and I can load it manually, but I can't automatically, via loadout.ini file. I also noticed that, when I am downloading the GBU-12 manually, the plane has a built-in twin rack, which loads ammo in pairs. Please help. Here's the aircraft stations: // Internal Guns --------------------------------------------------------- [internalGun] SystemType=FIXED_GUN GunTypeName=20MM_M61A1 InputName=FIRE_PRIMARY_GUN MuzzlePosition=1.85,1.40,0.600 LightPosition=1.85,1.40,0.600 AimAngles=-0.2,2.7,0.0 MaxAmmo=500 EjectShells=FALSE MinExtentPosition= MaxExtentPosition= // Weapon Stations --------------------------------------------------------- [LeftWingStation] SystemType=WEAPON_STATION StationID=1 StationGroupID=1 StationType=EXTERNAL AttachmentPosition=2.9740,-2.5737,-0.0409 AttachmentAngles=0.0,0.0,0.0 LoadLimit=2280 AllowedWeaponClass=LGB,BOMB,EOGR,TLR,CGR,EOGB,LGR AttachmentType=USAF,NATO ModelNodeName= PylonMass=86.18 PylonDragArea=0.02 [RightWingStation] SystemType=WEAPON_STATION StationID=2 StationGroupID=1 StationType=EXTERNAL AttachmentPosition=-2.9740,-2.5737,-0.0409 AttachmentAngles=0.0,0.0,0.0 LoadLimit=2280 AllowedWeaponClass=LGB,BOMB,EOGR,TLR,CGR,EOGB,LGR AttachmentType=USAF,NATO ModelNodeName= PylonMass=86.18 PylonDragArea=0.02 [CenterlineStationFT] SystemType=WEAPON_STATION StationID=3 StationGroupID=6 StationType=EXTERNAL AttachmentPosition=0.0000,-2.3138,-0.89 AttachmentAngles=0.0,0.0,0.0 LoadLimit=2280 AllowedWeaponClass=FT AttachmentType=USAF,NATO ModelNodeName=Centerline_Pylon PylonMass=41.75 PylonDragArea=0.02 FuelTankName=F15E_CTANK //----------- Left CFT- 1 2 3 is Bottom 4 5 6 is Top [LCFT_Station1] SystemType=WEAPON_STATION StationID=8 StationGroupID=4 StationType=EXTERNAL AttachmentPosition=-1.8480,0.440,-0.87 AttachmentAngles=0.0,0.0,0.0 EjectVelocity=0.0,0.0,-5.0 LoadLimit=1250 AllowedWeaponClass=BOMB,LGB AttachmentType=USAF,NATO ModelNodeName= PylonMass=86.18 PylonDragArea=0.02 [LCFT_Station2] SystemType=WEAPON_STATION StationID=10 StationGroupID=4 StationType=EXTERNAL AttachmentPosition=-1.8480,-2.3661,-0.87 AttachmentAngles=0.0,0.0,0.0 EjectVelocity=0.0,0.0,-5.0 LoadLimit=500 AllowedWeaponClass=BOMB AttachmentType=USAF,NATO ModelNodeName= PylonMass=86.18 PylonDragArea=0.02 [LCFT_Station3] SystemType=WEAPON_STATION StationID=12 StationGroupID=4 StationType=EXTERNAL AttachmentPosition=-1.8480,-5.008,-0.81 AttachmentAngles=0.0,-2.750,0.0 EjectVelocity=0.0,0.0,-5.0 LoadLimit=1250 AllowedWeaponClass=BOMB,LGB AttachmentType=USAF,NATO ModelNodeName= PylonMass=86.18 PylonDragArea=0.02 [LCFT_Station4] SystemType=WEAPON_STATION StationID=14 StationGroupID=4 StationType=EXTERNAL AttachmentPosition=-2.0817,-0.0790,-0.6193 AttachmentAngles=0.0,1.0,28.0 EjectVelocity=0.0,0.0,-5.0 LoadLimit=500 AllowedWeaponClass=BOMB,LGB AttachmentType=USAF,NATO ModelNodeName= PylonMass=86.18 PylonDragArea=0.02 [LCFT_Station5] SystemType=WEAPON_STATION StationID=16 StationGroupID=4 StationType=EXTERNAL AttachmentPosition=-2.0817,-2.8445,-0.6514 AttachmentAngles=0.0,0.0,28.0 EjectVelocity=0.0,0.0,-5.0 LoadLimit=500 AllowedWeaponClass=BOMB AttachmentType=USAF,NATO ModelNodeName= PylonMass=86.18 PylonDragArea=0.02 [LCFT_Station6] SystemType=WEAPON_STATION StationID=18 StationGroupID=4 StationType=EXTERNAL AttachmentPosition=-2.0817,-5.4681,-0.5642 AttachmentAngles=-4.50,-4.5,28.0 EjectVelocity=0.0,0.0,-5.0 LoadLimit=500 AllowedWeaponClass=BOMB,LGB AttachmentType=USAF,NATO ModelNodeName= PylonMass=86.18 PylonDragArea=0.02 //----------- Right CFT- 1 2 3 is Bottom 4 5 6 is Top [RCFT_Station1] SystemType=WEAPON_STATION StationID=9 StationGroupID=5 StationType=EXTERNAL AttachmentPosition=1.8480,0.440,-0.87 AttachmentAngles=0.0,0.0,0.0 EjectVelocity=0.0,0.0,-5.0 LoadLimit=1250 AllowedWeaponClass=BOMB,LGB AttachmentType=USAF,NATO ModelNodeName= PylonMass=86.18 PylonDragArea=0.02 [RCFT_Station2] SystemType=WEAPON_STATION StationID=11 StationGroupID=5 StationType=EXTERNAL AttachmentPosition=1.8480,-2.3661,-0.87 AttachmentAngles=0.0,0.0,0.0 EjectVelocity=0.0,0.0,-5.0 LoadLimit=500 AllowedWeaponClass=BOMB AttachmentType=USAF,NATO ModelNodeName=BOMB PylonMass=86.18 PylonDragArea=0.02 [RCFT_Station3] SystemType=WEAPON_STATION StationID=13 StationGroupID=5 StationType=EXTERNAL AttachmentPosition=1.8480,-5.008,-0.81 AttachmentAngles=0.0,-2.750,0.0 EjectVelocity=0.0,0.0,-5.0 LoadLimit=1250 AllowedWeaponClass=BOMB,LGB AttachmentType=USAF,NATO ModelNodeName= PylonMass=86.18 PylonDragArea=0.02 [RCFT_Station4] SystemType=WEAPON_STATION StationID=15 StationGroupID=5 StationType=EXTERNAL AttachmentPosition=2.0817,-0.0790,-0.6193 AttachmentAngles=0.0,1.0,-28.0 EjectVelocity=0.0,0.0,-5.0 LoadLimit=500 AllowedWeaponClass=BOMB,LGB AttachmentType=USAF,NATO ModelNodeName= PylonMass=86.18 PylonDragArea=0.02 [RCFT_Station5] SystemType=WEAPON_STATION StationID=17 StationGroupID=5 StationType=EXTERNAL AttachmentPosition=2.0817,-2.8445,-0.6514 AttachmentAngles=0.0,0.0,-28.0 EjectVelocity=0.0,0.0,-5.0 LoadLimit=500 AllowedWeaponClass=BOMB AttachmentType=USAF,NATO ModelNodeName= PylonMass=86.18 PylonDragArea=0.02 [RCFT_Station6] SystemType=WEAPON_STATION StationID=19 StationGroupID=5 StationType=EXTERNAL AttachmentPosition=2.0817,-5.4681,-0.5642 AttachmentAngles=4.50,-4.5,-28.0 EjectVelocity=0.0,0.0,-5.0 LoadLimit=510 AllowedWeaponClass=BOMB,LGB AttachmentType=USAF,NATO ModelNodeName= PylonMass=86.18 PylonDragArea=0.02 // Missile Stations ----------------------------------- //outboard [sidewinderStation1] SystemType=WEAPON_STATION StationID=4 StationGroupID=2 StationType=EXTERNAL AttachmentPosition=-3.1793,-1.6792,0.1527 AttachmentAngles=0.0,0.0,90.0 LoadLimit=200 AllowedWeaponClass=IRM,AHM AttachmentType=USAF ModelNodeName= PylonMass=34.02 PylonDragArea=0.005 [sidewinderStation2] SystemType=WEAPON_STATION StationID=5 StationGroupID=2 AttachmentPosition=3.1793,-1.6792,0.1527 AttachmentAngles=0.0,0.0,-90.0 LoadLimit=200 AllowedWeaponClass=IRM,AHM AttachmentType=USAF ModelNodeName= PylonMass=34.02 PylonDragArea=0.005 // inboard [sidewinderStation3] SystemType=WEAPON_STATION StationID=6 StationGroupID=3 StationType=EXTERNAL AttachmentPosition=-2.7778,-1.6792,0.1527 AttachmentAngles=0.0,0.0,-90.0 LoadLimit=200 AllowedWeaponClass=IRM,AHM AttachmentType=USAF ModelNodeName= PylonMass=34.02 PylonDragArea=0.005 [sidewinderStation4] SystemType=WEAPON_STATION StationID=7 StationGroupID=3 StationType=EXTERNAL AttachmentPosition=2.7778,-1.6792,0.1527 AttachmentAngles=0.0,0.0,90.0 LoadLimit=200 AllowedWeaponClass=IRM,AHM AttachmentType=USAF ModelNodeName= PylonMass=34.02 PylonDragArea=0.005 // CFT Missile Stations ----------------------------------------------- // Left CFT [LCFT_MSLStation1] SystemType=WEAPON_STATION StationID=20 StationGroupID=4 StationType=EXTERNAL AttachmentPosition=-1.851,-0.29,-0.87 AttachmentAngles=0.0,0.0,0.0 EjectVelocity=0.0,0.0,-5.0 LoadLimit=231 AllowedWeaponClass=AHM,SAHM AttachmentType=NATO,USAF ModelNodeName= PylonMass=34.02 PylonDragArea=0.005 [LCFT_MSLStation2] SystemType=WEAPON_STATION StationID=22 StationGroupID=4 AttachmentPosition=-1.851,-4.058,-0.83 AttachmentAngles=0.0,-2.750,0.0 EjectVelocity=0.0,0.0,-5.0 LoadLimit=231 AllowedWeaponClass=AHM,SAHM AttachmentType=NATO,USAF ModelNodeName= PylonMass=34.02 PylonDragArea=0.005 // Right CFT [RCFT_MSLStation1] SystemType=WEAPON_STATION StationID=21 StationGroupID=5 StationType=EXTERNAL AttachmentPosition=1.851,-0.29,-0.87 AttachmentAngles=0.0,0.0,0.0 EjectVelocity=0.0,0.0,-5.0 LoadLimit=231 AllowedWeaponClass=AHM,SAHM AttachmentType=NATO,USAF ModelNodeName= PylonMass=34.02 PylonDragArea=0.005 [RCFT_MSLStation2] SystemType=WEAPON_STATION StationID=23 StationGroupID=5 StationType=EXTERNAL AttachmentPosition=1.851,-4.058,-0.83 AttachmentAngles=0.0,-2.750,0.0 EjectVelocity=0.0,0.0,-5.0 LoadLimit=231 AllowedWeaponClass=AHM,SAHM AttachmentType=NATO,USAF ModelNodeName= PylonMass=34.02 PylonDragArea=0.005 // Weapon Stations --------------------------------------------------------- [LeftWingStationFT] SystemType=WEAPON_STATION StationID=24 StationGroupID=1 StationType=EXTERNAL AttachmentPosition=2.9740,-2.570,-0.035 AttachmentAngles=0.0,0.0,0.0 LoadLimit=2280 AllowedWeaponClass=FT AttachmentType=USAF,NATO ModelNodeName= PylonMass=86.18 PylonDragArea=0.02 FuelTankName=F15E_WTANK [RightWingStationFT] SystemType=WEAPON_STATION StationID=25 StationGroupID=1 StationType=EXTERNAL AttachmentPosition=-2.9740,-2.570,-0.035 AttachmentAngles=0.0,0.0,0.0 LoadLimit=2280 AllowedWeaponClass=FT AttachmentType=USAF,NATO ModelNodeName= PylonMass=86.18 PylonDragArea=0.02 FuelTankName=F15E_WTANK and these are the lines for STRIKE in loadout.ini file: Loadout[03].WeaponType=F15E_CTANK Loadout[03].Quantity=1 Loadout[04].WeaponType=AIM-9L Loadout[04].Quantity=1 Loadout[05].WeaponType=AIM-9L Loadout[05].Quantity=1 Loadout[06].WeaponType=AIM-9L Loadout[06].Quantity=1 Loadout[07].WeaponType=AIM-9L Loadout[07].Quantity=1 Loadout[08].WeaponType=GBU-10 Loadout[08].Quantity=1 Loadout[09].WeaponType=GBU-10 Loadout[09].Quantity=1 Loadout[12].WeaponType=GBU-10 Loadout[12].Quantity=1 Loadout[13].WeaponType=GBU-10 Loadout[13].Quantity=1 Loadout[24].WeaponType=F15E_WTANK Loadout[24].Quantity=1 Loadout[25].WeaponType=F15E_WTANK Loadout[25].Quantity=1

I discovered where was the mistake. In loadout.ini old file, which came with the aircraft, made by its author, it was written GBU-10 and GBU-12. When I put GBU-10D and GBU-12D, the weapons showed up, finally. In that knowledge base, which I studied it with other occasions, too, no one, unfortunately, tells you that you have to keep the syntax exactly, so I failed to figure it out looking there for answers. Maybe my failing will help others, with this thread to evade the same mistakes (and lose precious time) in the future.

File Name: F-14A_iriaf_desert_fox File Submitter: UllyB File Submitted: 06 July 2016 File Category: F-14 Tomcat Skins This is a skin for F-14A model and it's inspired from the real camo of some iranian F-14A (see the main shot in photo gallery). It should work with the F-14D as well. The skin is a remake of the original one, credits for the original skin goes to the real author, of course. You may use the skin in your future projects but don't forget to add me to the credits list. Click here to download this file

I recently bought an UHD resolution pc monitor and I would like to upgrade from 1920x1080 to 2560x1440 resolution, the default bitmaps for loading screen, menu etc but they won't work. I made custom bmp files, in 2560x1440 and saved them as BMPs (24bit) and then replace them all, changing the bmp file name accordingly of course, but they are not displayed or they are displayed wrong. Where is the mistake I made please? I really need help.

well if it's so I am still puzzled, in a way, because game (SF1_WOI) accepts 2560x1440 ones for main screen, for hangars and aircraft loading screens at least. Could they accept UHD for ones and none for others ? Assuming that it could accept for, let's say full HD (1920x1080), which I already changed 3 years ago and worked for everyone of them, how could have been even this limit (full HD) hardcoded , if that's the case you imply, in 2008, when full HD standard was in the beginning (correct me if I am wrong) ?

File Name: MirageIIICJ_Shahak_Loading_screens 2560x1440 File Submitter: UllyB File Submitted: 04 July 2016 File Category: SF/WO* Hanger/Menu/Loadout This is a pack for people who want diversity when it comes to an aircraft loading screen and use a UHD monitor which can handle 2560x1440 resolutions. This pack is designed for the Israeli Mirage IIICJ Shahak. I was inspired by the "Six day warriors" Deuces work. Instructions: I made this pack for the SF1_WOI game but it should work with the other SF1_X games, as well. Just unzip the pack and choose a picture you like. Change its name into Shahak_Loading.bmp and place it into /Wings over Israel/Objects/Aircraft/Shahak/ folder. That's it. Start the game and when the game will load the mission, presuming you will choose to fly a Mirage IIICJ Shahak single player random generated mission, you will see this screen. I hope you will enjoy it. You can use my mod in your projects but you must add me to the credit list. Click here to download this file

I took a look to the link. Viper63 made changes for SF2 series I understood. I was asking about SF1 series loading screen stuff. They are different made, in SF1 they are bmp, in SF2 they are jpg or something. Anyway I wrote to him a PM. I hope he will help me in the end to discover what I am doing wrong. Thank you for helping.

In campaignendscreen.ini there is a line whch calls for DefaultEndScreen.bmp. I checked the CAT files, there is no such bmp with this name. Have anyone seen what this file looks like,? just asking.... Another question for WOI , please: in which condition the CAMPAIGNWIN.bmp shows up ? I won a campaign but I saw the Winner.bmp file only. The same went for losing it....If I screwed the campaign , killing myself for instance, it pops up the loser.bmp file. When does the CAMPAIGNLOSE.bmp show up ?

what happens if all the skins in ini file have StartDefaultDate=1 ? I noticed that some aircraft had that parameter fixed thatway for more than one plane in the ini file of the aircraft. Does that mean that skins will appear randomly and not just the default one as in SF1 series ? I'm talking about single missions. It would be great to be thatway but it's too good to be true I'm afraid...

Well someone older in SF2 matters maybe will enlighten me a bit here. What I understood reading about this new feature userlist.ini was this: What happens in this situation: - operational theater WOI/single missions - the aircraft is let's say Lybian (Mirage 5D) - I have two skins , both under Libya flag - Egypt, in user list used this aircraft between 1971 and 1974 - Libya used it between 1971 and 2020 (well it's not 2020 yet , but you know what i meant) In this scenario I thought that IF I choose the plane and choose then Lybia as country from the list, I will see the year list between 1971 and 2020. Similar, if I choose Egypt I thought I will be able to use it just between 1971 and 1974, but for Egypt you can use it until 2020. as well. If the list doesn't limit anything according with the years each country use it in that file, then what is the point of that file ? Furthermore , it seems I can play with it under any flag found there in the list. Is the file in relationship with data.ini file interval only .or in single mission it doesn't work ? How does it work actually, I don't get it ? (And YES , I read the KB, otherwise I wouldn't be here now writing this post.)