Wrench

they left behind s**tloads of stuff after the surrender; not only in Korea, but mainland China. Both sides used ex-JAAF aircraft during the civil war (until the spares ran out) there was also (unconfirmed!) reports of ex-Soviet P-63s and A-20s too. 2 regiments of MiG-9 Fargos were stationed at Bejing, and were NOT liked by the PLAAF flyers I'd reccomend "Red Wings over the Yalu" by Xiaoming Zhang - a full history of PLAFF from it's formation thru Korea. A very large, and VERY detailed booK

afaik, they are NOT player useable; mostly because they exist "beyond the rim" (ok, The Wall) designed for AI controled bombers, and maybe fighters too

holy crap!!!! unbelievable!!! not THATs simming!

ah...... HA!!! one of San Diego's finest products! (or Ford's, depending when it was built)

hmmmm....little early to venture an accurate guess... but I"ll go with Mitchell

yup, the 56th was the unit to field them .. and half were lost to accidents and mechanical failures

and remember the order of the numbers x left/right y fore/aft z up/down

exactly like the paint bucket tool in the 3W TE ... and it will also need a 'directionality' function, just like the TE. "0", "90", "180", "270" and "Randomize" otherwise you get 'checkerborading' of the tiles

yup, know issue with 1stGen terrains, where there exists a _enviormentalsystem.ini statement. Remove that line from the terrain's main ini, and all will revert to "stock" sf2

and then... since each airfiled is pointing the a 'germanyce' airfiled ini, you'll need to edit every single runway reference to switch them over. which terrain download EXACTLY are you using???. IIRC, the "Ostseeausgang" terrain folder for the baltic (displayed name is Baltic Sea (Denmark) ) was already converted touse the desert airfields. if it's the 'basic' Sweden map, you have 2 choices: 1) edit the targets ini, as stated above, and extract the desert airfield inis (all six), and drop them INTO the terrain folder 2) buy SF2:E, and make sure the catpointer line 'reaches around' to the GermanyCE cat. (<--- this is much easier!)

that's impossible to do, and do CORRECTLY, with being able to read the TODs. You need to know WHERE exactly every single 'solid object' and 'alpha object' resides on each and every tile as to not have you terrain objects wind up inside them. the only things that can be accurately dragged/dropped are airfields, as they use (read: need) a fully 'clear zone' tile for their placement

however, I recently learned that Gerwin's TFD tool WILL generate water bmps, but the "CVzone" will still need painting in

MOST interestering!! thanks Eric!! Things to remember, and check over! since the ability to move "The Wall" got locked out, methinks that might be part of the problem; as you say, bases too near The Wall.

this is true for all the "2" series ... they're sorta of optimized for multi-cores. You'll start seeing all kinds of cool stuff (both FE and SF!)

wellll..... yah!!!!!

irrc, the ks19 did NOT network to the SON-9s. otherwise, it would have specified that ini the data ini. all the Red AAA units that would network to the Fircan, are ALL already set up for it. There is no need to fiddle with things

your welcome nose art decals are a specalality of mine

oh yeah! that's were I get most of the squadron crests I use for the 'patch.bmp'. GREAT site!!!

depends on how fond you are of the terrain! try an experiment --and this WILL be a lot of work (and that I mean!). rename & backup the original movements ini, and create a new one. keep the upper section, as that defines the 'front line' dividing red & blue exmaple (from Waterworld): [FrontLine] FriendlyBase=Levu Vana EnemyBase=Gavabutu Position[001]=467511,552932 Position[002]=545958,512183 Position[003]=587163,512770 Position[004]=600237,536868 StartShow=1 EndShow=5 delete all the other routes have at least 1 each, for both sides, shipping routes truck routes ground attack routes keep them near the middle 2/3s of the map. see if the problem persists. like I say, this is a random f***up that just been appearing (to my notice) over the last 4-5 months (or I just was too selfinvolved TO notice it before!) And it's only on 3rdparty terrains. Which leads me to belive it's in an ini somewheres, as opposed to a dying terrain engine dll or other core file.

one of the biggest buggers would be the Luftwaffe.... breaking down each JG into the staffels (staffelen?) ... II/JG1, 9/JG26, etc .. best to just use the full geschwader (JG1), and let the skin 'name' show for each staffel. JG would be like the wing or group (4th FG), were the staffel are the individual squadrons (334th FS). Just soooooooooooooo much work!! don't even want to think about the Japanese (IJAAF or IJNAC) or the Regia Aeronautica!!!! Never have figured out either ww2 RA or modern AMI numbering systems!!

nope. the only way I can think of to do it, is go through EVERY ww2 skin (expecially the Allied and Axis ones that actually are named) and start listing them. A lot (most) of mine are called by their squadron numbers. I know some of my AA and RAF are already activated, as they call 'modern' pre-existing squadrons from the stock 3W squadronlist.ini. then, you'll have to edit every single decals ini, adding my fake "SqTail.tga" as a Level=1 decal to some mesh not covered (I like using an aileron), to activate the squadron display on the Loadout page. I wouldn't even worry about bombers .... far too much work, and as they're reccomened for AI-only, who cares??

like your stuck at one of The Walls, right?? it's happening to a LOT of terrains, and all of a sudden. same as the 'waypoint down at the lower left corner' issue. Don't know what it is, but seem releated to the movement ini (at least as my testing on the ww2 New Guinea seemed to indicate) Methinks something, in some dll when to s**t all of a sudden. Test for this on ALL terrains; preferably ones that are more geophysiclly correct than the norways

could you be more specific as to the problem?? what exactly is happening? the 2 norwary terrains are, well, crap at best....black sea works ok (have to check again, been a while)

read http://combatace.com/topic/77421-piracy/ and http://combatace.com...c/66613-piracy/

nope iirc, this was one of the pirated models, stolen from marcfighters