Wrench

I think the term is "near fatal flaws". To say nothing of the physical models themselves needing serious overhauling (with very few expceptions)

The SF2 Sup Etendard pak I released last year was NOT designed for use with the Falklands mod ... may even be mentioned in the readme. As the falklands mod is -and should be a stand-alone, adding my upgrad pak is probably not a good idea. I'd reccomend RE-reading those readmes...

I was going to post something about 'pivoting balls', but thought better of if at the last second.... a Bevis & Butthead quote is needed here, methinks .....

it's called the "Default.ini", and it'll be in the C:\Users\* your name here *\Saved Games\ThirdWire\StrikeFighters2*\Controls *=or whatever game your using is .. it'll be the same for all the SF2 series

ccchhhhaaaa --- CHING!!!!

That's a common problem ... ther's no Huns in WoI, so you'll need all it's cockpit bits the FishFix is easy it's not a cockpit issue, but a DATA ini issue ... extract the newest data ini for each model (meaning all of them), drop them into their respective /Aircraft folders, and like magic the pilots should appear in front of their seats, now cowering behind them like the cheesy candy-ass commies they are (btw, that should be coverd in the 08 patch "Things To Change" thread in the KB ... the 08 patch made some small but significant changes in lods and inis) the section you're looking for is .... (08 21MF shown) [Pilot] SystemType=PILOT_COCKPIT PilotModelName= SetCockpitPosition=TRUE Position=0.0,2.83,0.85 <---this line MinExtentPosition=-0.30, 2.37, 0.05 MaxExtentPosition= 0.30, 3.42, 1.05 HasArmor=TRUE ArmorMaterial=GLASS Armor[FRONT].Thickness=62 CanopyNodeName=Canopy CanopyAnimationID=4 Vatour should use the F-4B pit, as it got twin-engine 'steam gauges', even if the radar is slightly wrong. In a pinch, you can use the MirageIII pit for it. For the Mystres, you can always swap in the TMF Mirage5 pit, as it has no radar, and is very French looking. Yes, I think outside the box!!!

this is from the SF2 Canberra B.2... [Pilot] SystemType=PILOT_COCKPIT PilotModelName= SetCockpitPosition=TRUE Position=-0.24,4.74,0.69 SeatModelName= Position= <---insert seat name and positions here --add those 2 lines MinExtentPosition=-0.49, 4.20,-0.42 MaxExtentPosition= 0.01, 5.21, 0.79 CanopyNodeName= HasArmor=TRUE ArmorMaterial=STEEL Armor[FRONT].Thickness=6 Armor .Thickness=6 Armor .Thickness=6 Armor[REAR].Thickness=6 Armor[bOTTOM].Thickness=6 BUT... it appears the seat is 'molded' into the aircraft lod. Might cause some problems!

Needed: that cool Cuban Green/Blue camo too!! (just adding to the workload...... )

so...tell me the truth.... do these missiles make my wings look fat???

if you can edit a data ini.... yes (extraction will be necessary)

easiset way, just extract the entire Objects.cat, and look for anything with the associated name. Which aircraft, exactly, are you trying to import???

you got all the inis, too, right??? (***.ini, _data.ini, _avionics.ini, _loadout ini, _cockpit.ini, etc) you'll need everything associated with that aircraft it's like when we were importing the SF1 F-104G into WoV, we had a whole "parts list" (posted below, as an example) double check you've got everything, and the allowed dates fit. EVERYTHING has to go into the main /Aircraft/Name-of-Aircraft folder (except any weapons/drop tanks)

no, becaus the AC always responed that way, as there was insufficent data

an oddity of the targets ini, when targets areas are set to NEUTRAL, they show up red. Guess there's only red or blue markers in a dll somwhere!

File Name: F-16A Falcon, Generic USAF/NATO Gray Skin/Decal/Ini Pak File Submitter: Wrench File Submitted: 05 February 2012 File Category: F-16 F-16A Falcon, Generic USAF/NATO Gray Skin/Decal/Ini Pak = For SF2, Full-4 Merged Required =* *Note: at minimum, you =MUST= have SF2:I, as this mod references the cockpit, aircraft and other required items =ONLY= found within a Full-4 or SF2:I. If you don't meet these minimium criteria, don't D/L this, as you wont be able to use it* This package expands on the work of MigBuster and others, and will allow for the creation of a stock 3W F-16A (probably Blks 1-10, although I'm not as 'up' on Falcon block numbers as I should be...). A complete set of inis are included, fully updated as of Nov, 2011. Newly added is a Userlist.ini, although this may need expansion/clarification of StartYear dates. Changes are welcomed and encourged! -Remember, this is the Early Production A model only!! All new Hangar and Loading screens are included. The canopy operates via a manual animation key (Shift/0, as always). Other Ini edits remove the internal jammer, and add one to the external centerline position, and other small Loadout modifications. See "Notes" below for more info. It should be noted at this time, that seperate from the main section of this download, are 'fixed' Decal and Textureset inis for MigBuster's F-16A skins. These skins are NOT included. You can find them in the SF2 Aircraft Skins download section (links are supplied in the "To Install" section below). BE ADVISED: install his -first!!-, then add the inis I've supplied. See below for more info on the "MigBuster Skin Fixes" in the "To Install" section. As always, fairly easy to follow, yet detailed install instructions are included. So, please read them!! Also, don't forget the "Notes" section for expansive esplainations and other illuminations. Happy Landings! wrench kevin stein Click here to download this file

(I'd have removed the tailhook) great idea! After all, the Dart and it's predecessors (XF-92) are Lippisch designs!

Pretty sure the lods will be locked in SF2NA, but even then with the data ini extracted, one could possibly use the 'remove component' trick and make the COD bird out of the Hawkeye.... Stoofs another matter ... a new freeware model is definately needed.

Let's hope so... the issue I'm dealing with, is Eritrea and Ethiopia BOTH use late-model SA-2 (LF??) and SA-3s. Added the nations to the appropriate Userlists, and they still won't come out to play (well, the 2s anyway .. the 3s just sit there looking dumb). Thought about using the 'ExportedToEnemy=TRUE' line, but that would open a 'hole nuther can of worms (can you say 'Soviet Hunters and Meteors?' I knew ya could!) Going to the generic tags, even though 'western' units will show, goes against the grain of 'making it right'. It's really diffucult to create historically accurate AD units, in they proper locations, when they stay home and watch TV!!!

somebody was asking/inquiring/whining the other day about 'generic' USAF/NATO F-16A skins for the Netz (made into a 'generic' Falcon).... 30 minutes of work gives us this: a plane-jane blank skin, using all decals so anyone can add whatever markings/serials/finflashes/doohickies they want. will upload this weekend. Of course, given my past history of such things... TK'll give us a A model with SF2NA!!!

You ain't seen MY request list, I take it!!????

I would think that fixxing the issues with hand-places SAMs & Radars would be far more important ... having that problem right now, and it's driving me bat-s**t crazy, as they don't show on the RWR and don't engage I loved that feature in ATF/USNF/FA ... and it's mission builder!

yah, you know... the site where you downloaded it from??? Dev A Team (aka: DAT)

nice T-Jets, PB!!! edit: just noticed the dual mounted HVARs!! nice!!

??????? your guess is a good a mine!!!