Wrench

Ah! I see now! we have different ones we use in our WW2 installs... so let me se.... in the /Menu folder, (must use the 3W names) all, obviousl are .wav AwardMedal HangarRadio1 Loading DebriefSuccess DebriefFail DebriefKilled OptionsScreen MainScreen SingleMission what I don't remember are the 'specs' (smaple rate, mono/stero?, etc) hope that helps!

"This is Gold Lead; we're starting our attack run"

put the sound in the /Flight folder? (named as loading.wav)

File Name: Cessna O-1E BirdDog Upgrade Pak -for 3rdWire O-1E- File Submitter: Wrench File Submitted: 09 September 2011 File Category: Other Cessna O-1E BirdDog Pak -for 3rdWire O-1E- = For SF2, Any and All = Please Note: this is =NOT= a full aircraft mod. The LOD files are =NOT= included, as they are propritery of 3rdWire, and cannot be shared. So ... you =MUST= have one of the original 1stGen games - SFP1, WoV or WoE to extract the 4 needed LOD files from their Objects.cat. Instructions are in the 'To Install' section. = This is a major overhaul of the stock, 1stGen O-1E BirdDog with a new, functioning cockpit, 4 skins and all new historically accurate serial numbers (albeit generic in nature, representing no particular unit; even the Canadian ones) The skins are: RCAF/CF CO-119 by ext (iirc) OD Green by ??? USAF white (stock) Pakistani Army Green (based on above, from Indo/Pak mod) The RCAF/CF skin has all new decals, matching those used by Canada (*please seen "Notes" below for more on the CF serials*). The OD Green skin from ?? has the "US Army" tag remade new, replacing that from my ancient L-19 mod, that was in the wrong font. The USAF skin uses stock decals, as it has always done (F-100 serials). Basically, other than stock National Insigia (and serials on the USAFWhite), all decals are new. The cockpit is based off Kesselbrut's Yak-3 pit, HEAVILY modified to fit the O-1, with gauges repainted and converted/recalibrated to US standard (knots & feet). Some gauges do not work properly, but this is the closest we have (or more truthfully, the best I could find). Lots of moves and other tweeks to both the data and cockpit ini make it fit like it kinda sorta shoulda. Decal randomization is set to TRUE, so be at least at whichever patch level gave that to us. The aircraft uses stock HVARs, but for fun I've included the M-60 underwing machine gun. So you can shoot stuff up. A revamped version of the 7.62mm M-60 gun is also included. A new Userlist.ini is supplied, with most of the Dog's users. As always, fairly easy to follow, yet detailed install instructions are included. So, please read them -CAREFULLY-!! .... Also, see the "Notes" section for Vitally Important Information ™. Seriously ... you NEED to read it. In fact, after unzipping, you might want to read this document through before installing. Happy Landings! wrench kevin stein Click here to download this file

LOL! can't be any sillier than my LOTR NZAF Kfirs, or Sauron & Saruman's Fishbeds! *for fun, google "Texas Israeli War of 1999"* don't know if i still have the book.....

Moved to a more correct Forum PLEASE do NOT post questions in the Knowledge Base -- It's for answers ... Questions/comments go here, in the appropriate Forums =========== Like Stary said, you'd have to create a totally new terrain from scratch. And anything as small scale as a WW1 map would be next to useless for a jet-based sim The smallest terrain I know of for either series would be the Canary Islands map -- I think it's just under 500x500 km (if that!) wrench kevin stein

Folks REALLY need to start learning how to do things for themselves. As to the Bort number issue, that's an easy fix. 1) extract all the borts from (whichever) objectdata***.cat they're in. 2) find the ones needed, 3) rename as necessary to get the 'correct' ones, discarding those uneeded. 4) create new subfolder in /Decals folder for 'PolishNums'. 5) place renamed decal there. 6) edit decals ini of said skin to point there. 7) creat new numbers.lst to refelct corrected numbers for said skin 8) OPTIONAL: use the new randomization feature to 'scramble' how the numbers appear in-game (ie: non-sequentially) shouldn't take more than an hour to do

It NEEDS a better pit than the Meteor I been using!!!!

O-2A Skymaster, all new decals and markings Soon!

glad that book will be of some help!!

UK, I went and moved this here, as it's more of an SF2-series question. making seperate installs for the various theatres is a very simple matter take your game exe of choice say, SF2.exe. Rename to which ever theatre you want. We'll start with standard WW2 Europe (ETO) so, copy and paste the exe BACK into the SF2 folder (C:\Program Files (x86)\ThirdWire\Strike Fighters 2), and it'll call itsef copy of SF2.exe (or words to that effect). Then, rename it ETO.exe. Create a new shortcut wherever you put them (there's even theatre-specific icons avaliable -- check the 1stGen DL section. if not, I have them -as I made most of them!) Run the exe and let the game build the new ETO mods folder, in the saved games folder. Run the game and do uor setups for controls, and graphics, and etcs. Then delete ALL modern aircraft (note: if you're merged, with Expansion Pak 1 -don't delete the Spit 9s!! You might want them!) Delete all the modern ships (leave the cargo ship and tanker), tanks, AAA, SAMs, etc. Leave the USTruck, ZilTrucks and USJeep -- they'll be needed. Then you can start populating the /Aircraft and /GroundObjects and /Terrains folders with the WW2 era terrains and aircraft and vehicles and whatnots Be advised -- 99.9% of all WW2 aircraft now available from 3rdParties are NOT fully speced for SF2 usage. Even those with 08 1stGen level flight models. They CAN be used, but expect some 'oddities' now and then. Any other questions, just ask! edit: I converted WoA to SF2, and it works fine with very little tweeking of the terrains data ini -which will be needed for ALL 1stGen terrains imported to SF2. FMs are still a bit 'quirky'. Of course, you know that SF2 handles decals differently, so you'll need to drop all the aircraft folder INTO the /Objects/Decals folder, and delete EVERYTHING from inside EACH folder, excepting the /D subfolder. This keeps the pathways intact, so no decal ini editing is/will/should be required.

don't install to program files .. install to the root of /C covered in the knowledge base

we'd discussed Kamikazies in one of the thread in the PropHeads forum ... but I can't find it!! what we'd figured out, was using an aircraft, changing the AI parameters for bomb release to 0 altitude, so it releases AFTER it impacts with the ground or ship or whatever. For a cruise missile, you'd need to cinvert it to an aircraft or something like that targetable missiles would be the best way -- which we ain't got (I do remember being able to do that in ATF/FA way back when, but I think only after editing the missiles)

would this help? Red Star #34: MiG-25 (one of Gordon's books) cockpit pics near the end also have the Aerofax on the 25 & 31, but it mostly just rehashs the Red Star book

missing the MaxDecalLod= statement from each of the decal entries. A very common problem on reallllllllllllllllllllyyyyy old 1stGen mods ported over. OTH.... why not just download this one: http://combatace.com/files/file/9082-at-6g-texan-mosquito-fac/ where all the work has been done (with 100% historical serials -albeit no paticular unit) the 'at6g' fakepilot-antenna pak will need updating to SF2 /Pilots spec, but that's a no brainer (and ifyou get stuck, I'll shoot you mine)

PLEASE DO NOT POST QUESTIONS IN THE KNOWLEDGE BASE!!! It's for answers only! --------- to answere the question, there's the WoVSQMD and Kreelins mission creator/editor -- both in our downloads section

my best guesstimate as to TCAs location the hardest part, would be replicating that iconic terminal building, and parking ramp (without building a completly new airfield)

i'd suggest READING the targets ini for that terrain, (ie: locating that target area) and LOOKING at the listing of target objects IN that area, then looking for them IN the _types ini. It ain't that hard to figure out and yes, they DO have shadows (but are seriously f***ed up due to lod internal mesh issues) again, this is one of the piddley things that really don't matter, and shouldn't be worried about

I don't see why the stock GermanyCE couldn't be used for that (45-48 timeframe). The basic demarkations between East and West are already there. Berlin is lacking Templehoff, however, but some retiling could probably take care of that relatively easily (ie: new city-to-airbase tiles would be required for ALL 4 seasons) don't seem all that hard to do (maybe replace SAMs with AAA units via the Active/inactive line in the targets ini ie: Target[0xx].ActiveYear=1945 Target[0xx].InactiveYear=1959 (when SA-2 first started deploying) of course, flying in years before SAMs operatinal start, automatically limits to static or mobile AAA units

yes there is look in the terrain folder to answer the next question, yes there's one for the af63 as well

out for a morning jog....

it's amazing what a single typo will do....was going nuts trying to figure out WHY the serial number decals weren't showing on the BirdDog.... the difference was between the 0 (zero) and O (oh). Eyes must be going....

there's a whole thread about the "Double Cockpit Issue" in the SF2 Knowledge Base http://combatace.com/topic/58372-the-double-cockpit-issue/

RedAirs= in general Migs, Sukhois, Tupelovs, etc. In other words, any AI controled aircraft (which includes the Skyraiders and Canberras and Starfighters -oh my!) a little helpfull hint is here: http://combatace.com/topic/55746-patching-made-easy-part-deux/ the 2nd or 3rd post (don't exactly remeber which)