gerwin

F-15A I noticed TK uses differently named models for the USAF F-15A and the IAF F-15A Baz, but can someone point me to the actual differences between the two models. I am not talking about the cockpit here, just the outside view of the aircraft. F-16A I read something about TK correcting he F-16A in the SF2 Suez Expansion. But what was wrong with it anyways?

I know of at least one way the export settings take effect in the series 1 ('08) games: Some terrains have a limitednationslist, or one can add a limitednationslist section in their xxxx_nations.ini. It will allow the AI to only fly aircraft from the listed nations on a particalar terrain UNLESS it has been exported. Example: vietnamSEA: limitednationslist: Nvietnam vs. USAf/USMC/USN. you will not encounter a german add-on plane in single missions unless it has been set as exported=true.

For the above aircraft addon I attached some decals: 'MARINES' and VMA-131 QG. With new decals.ini A-4M_decals.zip

Okay, this week I made something of an A-4M Skyhawk for my Wings over X merged install. It has a few inconveniences I am afraid: - There is no proper cockpit for it so I use it as AI only. - It is based on the SF2 A-4F '74 Skyhawk lods, which I cannot distribute, and which show a few differences with an actual A-4M. - There shall be a few inaccuracies in the skin conversion and datafiles, and I did not work on the decals much So therefore I just release it here. If somebody is interested it can easily be made into a mod for SF2. http://hotfile.com/d...c/A-4M.zip.html

Are you sure hiding "numbers.lst" makes things work? I don't have much luck with it, the only difference is that I cannot see the number preview in the loadout screen. Otherwise the misbehaviour is the same. It is like this: -It seems the first time I create/generate a single mission the number is valid. -creating missions after this: it usually displays the last number of the list in the loadout screen, and displays nothing in game. only like 10 to 20% of the time do I get a valid working number. (Tested with WOI with several aircraft with "numbers.lst" files containing 8 to 24 entries) So it seems like the game chooses a number below 100, picks that entry, if that entry is not referenced you get nothing.

Okay I actually now remember that thread about the F-16A. So as far as we know F-15A and F15A Baz in the game look the same, even though in reality the Baz can have different launch rails. I am wiser now thank you!

Wow, I am glad to hear that. Thanks in advance!

Veltro, does this mean you will try to add lower detail lods in some of your projects? As I noticed you normally do not.

It better be, because tga's are dump uncompressed bitmaps by themselves.

I still mostly use .zip, sometimes .rar if file size matters more. Using winrar for both these formats. .7z seems to be comparable to .rar, only more modern. Obviously 7z/rar have better compression ratios, but the old zip format is very responsive/fast if one just want to browse the contents of an archive or extract just a few files from it. File Compression ratio tests

Okay, for now I have a workaround by using the F-14B model for the F-14A. That one always shows symmetrical exhausts. I dug out the earlier F-14 aircraft mod that has been around for some years, just to compare; The new F-14 model is quite a bit better.

View File Mercenary Sand Skin for F-16A Netz (fictional) Mercenary Sand Skin for F-16A Netz (fictional) version 1.1 by Gerwin 26-06-2010 DESCRIPTION: Made for the stock Wings over Isreal F-16A Netz Model. For use by the nation of Paran. This skin is part of a Skin set, all in the same style, by the same author. This work is based on existing skins. INSTALLATION: Copy the included folder with contents to the folder that contains the F-16A_Netz files, for example: WOI\Objects\Aircraft\F-16A_Netz When in the game select the skin in the loadout screen. or: My Documents\ThirdWire\Strike Fighters 2 Israel\Objects\Aircraft\F-16A_Netz The SF2 Model of the F-16 has some texture mapping changes. Use the bitmap in the folder "SF2-Version" to make the set SF2 compatible. UPDATE 1.1 of 21-4-2019: New Screenshot, decals and ini files. Now comes with SF2 specific bitmap. THANKS TO: Third Wire for the Strike Fighters Based Games. Base color is taken from the LARAF Mirage 5. Sharktooth are copied from A-10. Submitter gerwin Submitted 06/26/2010 Category F-16 Fighting Falcon Skins  

With some minor edits I put it in my Wings over Israel install. Works fine. I like the weathering on the later blue-ish skins. Did notice the thing gives more lag then other aircraft (when on the runway near the rest of the flight). The model .lod file is big. I tried to show the second lod at closer distance, which solves the lag, but that model is missing part of the left exhaust.

As the title says, Can someone please post a proper loadout for the SF2V skyraider. I know there is one in the Air&Ground war enhancement pack, but it is a bit of a large download for just this little thing.

Thanks a lot! This gives the skyraiders something to carry.

Here is the one I talked about, don't tell me it is not one of the 250 known patterns. Rapidshare: LSK Camo skin Only 249 more to come... ;)

Thanks!, I can certainly use this one. Made a replacement East German skin for it today, using the stock SF2 LSK camo but changing the colors. PS. This MiG uses a non-standard afterburner effect, but IIRC it was not included.

I suspect that if the catpack tool cannot read a certain SF2 Cat archive after patching, that the game cannot read it either. So anyone who has trouble extracting from a cat archive might have a faulty installation to some extend. It is also a bit difficult to manually merge patched games, ObjectData002.CAT and ObjectData003.CAT from SF2 contains files that are not in the same files form SF2E, but the ones from SF2E contain files that are not in the ones from SF2. If you get what I mean.

I put way to much time in making an ultimate Wings over everything install after the oct 2008 patches were released. So many tweaks to terrains, planesets, skins, weapons, CAT archives. Guess I enjoy modding more then playing games ;) 90% is stock models and artwork though, 10% from Combatace and myself. I am quite happy with it and am not up to jumping into SF2 yet. Mostly because of two reasons: I would never be able to resist tweaking SF2 to the same extend, and I don't have the time available for doing so. Second I noticed the loading times are 2x longer for each mission? Also my system is not really welcoming the higher res skins and models. (99% of my skins are currently 512x512). So it is no verdict on SF2, just a personal choice for the time being. Now a year later the SF2 series have been taking up all the ThirdWire efforts. I purchased SF2 to check out the engine, and later SF2E just to extract all these beautiful new skins and move them to my SF1 install. I applied the december 2009 update nonetheless, and noticed a suprising change; Some of the aircraft models in SF2E are no longer in the new LOD format, but in the original SF1 LOD format. This enabled me to put the following SF2 Third-wire aircraft in SF1: MiG-17PF, MiG-23ML, MiG-23MLA, MiG-23MLD, and a proper MiG-21BIS. They work 100%, I am having a blast with the new MiG-23's! the Corsair A-7D and MiG21S can also be imported but I haven't done so yet. Now I must warn you; Adding additional skins from SF2E is easy, but the Aircraft are not easy to do.

I was just joking, I hope ;) Honestly, I am tempted to just mod a Merged SF2 installation and buy a new system for it, but I cannot do so in the months to come, nope.

I wrote down my reasons did I not? If that ain't enough just try to understand that I am a Fool, and proud of it .

Thank you, this works for me! Though I had to clean up this package extensively, as 70% of the graphics files are not at all used for the cockpit. Also some files are missing, they are in the Su-27 package. The same remarks go for the MiG-23 MLD cockpit package. Here the actual files referenced:

Thanx everyone for your appreciation! UPDATE ALERT: CatPack V1.12 has some additional features when extracting a Cat archive: First it automatically creates an index file of the Cat file. Second and it allows one to optionally pass a wildcard string, only files matching this wildcard string will be extracted from the archive. For example "mig" will only extract files that have "mig" in their name or extension. ...This should save you some time and disk space.

You will find it here: CatPack