Wrench

pasko's even the 3 view in the "In Action" shows more slope. wish i had a better one (damn Warbird Tech ain't even got one!)

i llike it; however, I think the nose greenhouse is too flat; that's more like the C-87 version

forgot to mentinon, after extraction, the _cockpit.ini goes INTO that's aircraft's folder. Otherwise the changes won't be read by the game engine

***_cockpit ini you'll have to know WHICH aircraft, and then go the the ObjectData***.cats to find the various files you'll need the latest 3W extractor (arpil 2012), available in the SF2 Downloads, Tools/Utilities http://combatace.com/files/file/13040-3rd-wire-toolkits-april-2012/ or at 3rd Wire it's very easy to use

what it's gonna take to fix it, is going to break any campaign built for it, as we're going to be removing all target areas ABOVE Lingayan Gulf, and switching sides for the 2 northernmost airstrips so.... open the Philippines1941_targets.ini, and for the following target areas Aparri Gonzaga Vigan Vigan Airstrip Tuguegarao Tuguegarao Airstrip change the Alignment=ENEMY to Alignment=NEUTRAL this will effectively remove them from play Now, to give your IJAAF/IJN land base fighters/bombers somewhere to roost, for the following target areas: Balaoan Airstrip Jones (city) Jones Aistrip change their alingnment to ENEMY. Changing Jones city will prevent 'red-on-red' incidents. I realize this put enemy A/C very close to Clark and the other bases near Manila, but this can't be helped. Experimentaly, you can add this at the bottom of the targets ini... [TargetArea116] Name=Tainan Air Base Position=146189,996923 ActiveDate=0 Location=21 Alignment=ENEMY OffMapAirBase=TRUE and for the pre-existing Formosan bases... [TargetArea059] Name=Taichung Field ;Formosa Position=340000.000000,-200000.000000 Radius=4242.640625 ActiveYear=0 LOCATION=21 Alignment=ENEMY OffMapAirBase=TRUE [TargetArea060] Name=Pingtung Field ;Formosa Position=300000.000000,1200000.000000 Radius=4242.640625 ActiveYear=0 LOCATION=21 Alignment=ENEMY OffMapAirBase=TRUE of, couse, this may only work when the WW2 game is built from the SF2NA.exe. Worth a try, at least the major flaw is the map is simply too small, and there's no way I know to expand it along the x/y axis the required 200km. Put simply, a complete NEW terrain is requred.

why not just give the guy the easiest way out??? No need to overcomplicate this s**t....

first things first.... the Phill 1941 map is for the INVASION of the PI in Dec 41 by the Japanese. that shouldn't be used for anything BUT that....and it'll need major overhauling to take advantge of SF2NA off map basing (ie: IJN bombers from Formosa) the standard "1944" map should be used for anything AFTER the US invasion of Leyte (and that's how my PI 44 mod is set up). Unfortuantely, that one also need the targeting rebuilded. But is quite usabe. Let me know which map you want the "key" for; the money goes to CombatAce.

Fuselage section of the data ini ShowFromCockpit=FALSE

that oddly shaped red line is the FRONT LINE, seperating friendly and enemy forces. It's set up in the Movement.in, and should (normally!) be relatively straight across -east/west, and on that map (assuming the American landings on Leyte), bend north-ish on the eastern end. The Wall has always been 80km from the edges, all the way back to Day 1 SFP1. Up untl a few patches ago (Jan 12???) we had the ability to edit the World setting in the FlightEngine.ini, but many terrains got f***ed when that was removed/locked out For that same 20bucks, I'll tell ya what to do, to prevent being tasked with mission "beyond the Rim"

from the readme:

part of the diagonistic procedure, is to see if or if not something works in game ... you can't just go by what's on the loadout screen. Has to be tested in the 'game world'

yes as you stated, you just encounterd "The Wall" (or if we're into Stephan King, "The Dome") i'll bet 20 bucks the target was near the northern end of Luzon ....

the M2 30 cal is a STOCK 3w gun ... you should have NO issues don't worry that the 'ammo' display is grayed out .. in game they fire.

looking good for your next one, can we talk you into the A-20 series? I've got a buttload of skins/decal set that need a new home (for several marks!)

which Peashooter? There used to be 2 in the d/l section edit: just tested both, the AAF/PAAF and CAF and the guns work fine

oh, yes indeed!!!

thanks Daniel!! wish we had Geo's max files ... he'd started a Jack 5-6 year ago....

now moved to the "SF2 What If.." Hangar nice bird, too!

i was hoping for more work on the spitfire 5, both the standard and trop versions, and maybe the seafire 3.... it needs finishing! (no pressue, of course!)

there's shouldn't be ANYTHING worng the FWs ... other than that little odd dark bit o the lower left. ------ Have you tried turning OFF the fuselage in the various data inis?? This goes for dswan as well, since he posted the very same qestion on the DAT site why are you playing on Easy mode? you know NONE of them had radars .... --- Edit: this issue has be prevlant since SF2 came out. It's know as the "double cockpit issue". FastCargo has addressed this in the SF2 Knowledge Base. For those with some skill in editing (and for those that can't find it), here's the link http://combatace.com/topic/58372-the-double-cockpit-issue/

rather early redtitions of Cocas' Spit 5 -- these are the 1st iteration lods, and still need some "massaging" Both are partly skined, and mostly decaled. European Day scheme and Desert Day Mk.V Trop (will need help with skinning once the LODs are finalized!!! I really suck at trying to figure out how the camo patterns match up!!!)

i would think you don't need the min/max extensions at all ... never used them for the "faked" pyolons for the WW2 ones I've added

which aircraft???? I've probably already fixed it in my installs...oi! so much frakking work!! other than cockpit ini editing (if known nodes of the cockpit lod), there's data ini editing as well, with the 'moves/removes' like I did for Raven's Hurricanes, open cockpit statements, CG offsets, ShowFromCockpit (true/false) and so forth edit: oh, and screenshot of the offending cockpit, loooking forward, is helpfull too!!

not if you've done it couple thousand times ..... LOL!!