Wrench

move IJN to the SECOND position in the PTO terrains that support carriers. The side effect is, losing those missions against the Jap fleet. This very same problem is a MAJOR flaw in my Phillipines 44 WW2 terrain. Apparently, the coding is "one or the other, but not both". Kinda dumb, IMO. as to IcelandNA there's no movements in for that terrain, so you won't get armed recon missions, or anti-ship either. It's virtually impossible to generate the movements ini on the STOCK Iceland terrain, because there's no way to "see" the terrain in any of our editors (Gerwin's for example), to find the X/Y coordinates to plot the routes, as it's LOD based. OTH -- and I don't know this for certain -- Gerwin's "rebuld" of NA's Iceland into the "old style" TFD/HFD should be. If so, you can use the TFD tool to plot the various routes, including CAS. But that would be an undertaking, and only if the 2 terrains "match" so to speak in the general physical similarities (land contours, etc) As to the JGSME thingy, I can't say. Don't have it, don't know it; but a 1 terabyte HD (or larger!) takes care of having the separate mods folders. They're relatively inexpensive nowadays

Outbound for Romania.... (yes, Ed's new Libs)

don't forget, they'll need to be added to the terrain's _Types.ini first, before placing 'in-game' via targets ini editing

my pleasure!

let's get this straightened out once and for all. When each of the 5 games (included the 2 expansion packs) are installed, the total of 'core files' -- not counting the executables are merged within each other. This can be easily seen by examining the folders and files WITHIN the C:\Program Files (x86)\ThirdWire\Strike Fighters 2. One will quickly see there is only one set of dlls, and the various cat files used for all of them. One can expand this into included the DLCs available for purchase, but they reside within their own subfolder of the main "core install". OTH, the DLCs DO interact when installed with all the other program files. So, in essence: Each of the 5 games (7 counting the 2 expansion packs) have their own executables ... Which means each of the 5 (or 7) games all create their OWN mod folders when the exe is run. Within each of those mod folders, if one were to open the various sub-folders of the main /Objects folder, and study the contents therein (which is HIGHLY suggested for everyone), one will find EVERYTHING from ALL 5 (or 7) games readily available in ALL of them. The only things NOT created in the mods folder during install/running build -remember, we're talking STOCK with nothing added- is the /Terrains subfolder. The game engine ™ automatically sees all the terrain cats, making them readily available in each separate mods folder. This why user lists for Objects, and 'limited nations' statements in (add-on) terrains are so critical for correct operations. That's a subject for another day (and covered in the KB, btw) EVERYTHING within the various cats and dlls are used by the separate exes -- which is why you see only ONE core set of these files. In truth, 'merged' may be an incorrect term. The install programs, and the various exes automatically merge themselves together during installation -just watch the progress window when installing a new game or DLC; you'll all the same core files being updated-, effectively creating a (somewhat) seamless integration of all the required bits needed to run the games. Think of the 5 (or 7) exes as separate games, sharing common core files; which is EXACTLY what they are.

they're terrain objects, to be placed by the Terraformers

don't forget, in Real Life ™, Navy Skyrays WERE attached to ADC

we'll get you up to speed. eventually!!!

you screwed something up, somewhere. I looked it last night, and nothing like you're showing is presenting, Remember, it's using the FRENCH mirage IIC lod, NOT the Shahak's. use these inis in the zip attached

ok. my what if USAF Mirage. the data ini is WAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAY outdated. You'll have to extract a fresh one for the Mirage IIIC, and copy all the "top" section (MissionData) into the new one. Also, cross check the hardpoints for the nationality callouts and so forth. In essence, you'll be rebuilding the NEW data ini (don't forget to rename it) with all the USAF specifics. over the time when it was first released, MANY changes have been implemented by all the various patches and DLCs if you're speaking of the 500 ltr "supersonic" tanks, yes they do sit that tight against the wing (just look at the AdA Mirages for comparison).

the z value; (last one) move it -0.800 (rounded up!)

move it upwards in increments of 0.10, see where it sits

Knowing WHICH terrain might be of some assistance, no? You can make them show up by having RoyalNavy and FrenchNavy listing in whichever terrain's ***_Nations.ini you're flying over. remember: every terrain can have it's own region specific nations ini be advised, however. After making the edit, don't be surprised to see USN birds on a Royal Navy CV, or AeroNavale, or etc. The engine is kinda 'stupid' that way

can you be more specific? you mention "uses stock tw lods" Which ones in particular (the aircraft's name) also, check you don't have outdated data and loadout inis in the aircraft's folder. If so, rename them both and retest in-game to see if the double mountings show up. If they aren't showing, the inis are at fault, and you'll need to extract the LATEST version from whichever object cat their in. (or not, depending!) If they are still showing, more data will be necessary for us to run down the issues

it's shadow artifacts caused by the pit1.lod. It's been reported to TK several times over the last 3 or so years. copy/paste the text below into a blank notepad "sheet", and 'Save As...' pit1.ini in ALL your terrain folders (meaning, it goes into each and every one!. if said terrain subfolder don't exist, create one in the relevant mod folder) [LOD001] Filename=pit1.lod Distance=6000 [shadow] CastShadow=FALSE ShadowCastDist=500 MaxVisibleDistance=2000

405k takes up too much room on your hard drive? (that's the total size of those tga files. some may be leftovers from the original 2009 version.) the LP lod callout was a text edit I simply forgot to make. You all can make that adjustment, methinks

??? I'm at a loss????

I'll bet objectdata002.cat (the locked one, with all the lods)

since the terrain isn't in the state I originally released it in, I've no clue. So ????

well, obviously, it need to be flattened! Prolly fuck up the water big time around the beaches. right now I don't have time to rebuld a TE for the Marianas; I'll put it on a "to do" list

View File SF2 "Beer Bomb" SF2 "Beer Bomb" 4/18/2014 -- Something for Anyone, Anytime, Anyplace -- = For SF2 ONLY, Full-5 Merged (Reccomended/Preferred) = With the recent trend in the SF2 Screenshots Thread on discussions and displays of "potables", I thought this would be a nice little funny thing to add. Basicly, I took the 55 gallon Napalm bomb and repainted it to "represent" a kind of beer keg. It is fully "combat ready" and will act and explode just like Napalm. Included is the skin template, for those wanting (or nuts enough) to want to make the labels in any other languages, or for your favorite beer. As always, fairly easy to follow, yet detailed install instructions are included. So, please read them. Good Drinking!! Wrench Kevin Stein Submitter Wrench Submitted 04/19/2014 Category Single Ordnance Files

Korean era skins are in the KAW Corsair Pak, including the AU-1 http://combatace.com/files/file/13429-sf2-kaw-era-f4uau-1-corsair-pak-by-tmf/

oh! so Charles came through for you! Good on him!