Wrench

could come in really handy! something like that will absolutely need the ability to reload from within, without have to exit and restart the program

File Name: SF2 WW2 MTO Fiat G-55 by Veltro2K File Submitter: Wrench File Submitted: 26 March 2015 File Category: Italian Origin SF2 WW2 MTO Fiat G-55 by Veltro2K 3/25/2015 = For SF2, Full 5 Merged RECCOMENDED! = This is a Re-release of the Veltro2k's WW2 Italian Fighter. This is a fairly "quick and dirty" upgrade for Veltro's Fiat G-55 Centauro. It's been given a "new" FM, but as always, will need some fine tuning. I've split the 2 skins, into "before and after" the Italian surrender of 1943. You have: 51 Stormo, RA (circa mid-1943) Squadriglia Montefusco, ANR (post 10/1943 -- although the paint scheme is more in Luftwaffe style) I did NOT use the SF2 "date switch" for these. *Please note that the Aeronautica Nazionale Repubblicana, is =NOT= on the existing ww2 Nations.ini. Nor is the Allied-aligned Aviazione Cobelligerante Italiana. If you want, you'll have to create the new nations yourselves. See "Notes" below.* Skins remain in their bmp format, and decal radomization is set to TRUE. New damage textures are supplied, in DDS format. My standard "box art" style hangar and loading screens are also included. And, thanks to Mue's Lod viewer, I've exported a lined map psd for those wishing to attempt to create other skins. This should give you a base to draw new panel and rivet lines. A userlist ini was created, but is incomplete (most post-war versions were Merlin powered). Included are a pilot figure, AvHistory engine sound, and a new drop tank. All other weapons you should have in the WW2 weapons pack (it uses LW bombs, until we get freeware Italian ones) The canopy open/closes with the Standard Animation Keystroke ™ (shift/0). As always, fairly easy to follow, detailed install instructions are included. PLEASE read them!!! Give the "Notes" section a glance, as well. ** The aircraft herein is released in "AS IS" Condition. Any and all issues/problems that cannot be solved via ini edits will exist forever, or until such time as if/when new models are created and released.*** Happy Landings! Wrench Kevin Stein Click here to download this file

hopefully, we'll have the Sea Fury for you in a few days ("2 weeks!!!"). Carlo is making some adjustments on the hit boxes. It's nearly ready!!

in the meantime, Ed says I can re-release this one "as Is". I'll just turn off the shadow statement. Otherwise, it'll look like that old "planes on sticks" game (I never played it, but watched one time. looked cool!)

I have the Yamato DVD set, of the US series. Capt Harlock was cool as well. There are a LOT of anime that have exceptional stories. Unlike most Americans, I don't see them as cartoons, but animated films. for a good one, try royal space force: the wings of honneamise

only if Ed still has the MAX files. I've narrowed down the shadow issue to meshes at the nose gun troughs. One can always turn off the shadow in the main ini. FM feels pretty good, but it need a lot of other work .. hit boxes are WAAAAAY off (mue's tool is godsend for this!! -- but something I don't know enough about to tweek), minor tweeking here and there -light properly positioned and such. Been straightening out some skin/diecal issues since my first post... One skin is definitely ANR (LW style, so it might even BE LW!), so had to make some new decals (new user list too, but ANR is not in the ww2 nations ini). Even made 2 smaller drop tanks (RA versions of Raven's 54 gallon P-40 tanks). If Veltro says it's ok, I'll release it "as is", and other can go fiddle with it.

probable FM issues, but LOD issues as well....shadow tractor beams

out-frakking-standing!!!! the attention to detail was amazing; like the Dupe's rotary magazine (although the 'reflex warheads' was a bit much! and a female Imp pilot??). Interesting to see the 2 ISDs supported by an Interdictor. VERY well done!!

the Re-2005 is DAT; s/b available in their MTO mod I have veltro's G-55, but it has "issues", and isn't ready for prime time SF2

not a problem! it's always good when someone actually answers the question, not just tells you what you already know, and have done. in truth, the 'read only' trick is not my discovery; I don't remember if it was Paulo or Ravenclaws! Works on all the AIs made flyable (all my MiGs, Sus, and 104s are done that way, too

it's a well know fault of the game engine itself. The A-1, like all the Red Air ™ birds (and all the Zippers, too..), are by default AI controlled ONLY. Every so often, at completely random intervals, the Game Engine ™ will automatically rewrite ALL the main inis of AI-onlys made player flyable. There are 2 alternatives: A) Keep a copy of my patent-pending "one click restore" main ini INSIDE the main aircraft folder. Then, just do the "save as..." and it'll return to flyable (or do the copy/paste thing) B) Add all the lines to make it flyable, making sure any and ALL add-on skins are already added and listed!, as the next step will lock it ... Right click the ini, ---> Properties ... make "read only". That will prevent the Game Engine ™ from automatically overwriting it.

As some of you may know, from some recent posts, that I'm rebuilding the old Israel 2 map to SF2 spec. However, I've run into a couple of issues as to 'what should be targeted'... Egypt Alexandria -- should I add the 2nd airport (Borg El Arab)? Should the port be detailed? I've come across very little (read: no!) information of what part was played by Egyptian forces based there, all the way back to the 56 war. It's out of reach of 99.9% of all IAF aircraft.... I did retile Alex, a bit closer to reality. Syria Tripoli (port) Latakia (port and refineries) same goes with these 2. I know about the naval battle of Latakia; that's problematic in this game. (meaning nearly impossible to replicate). However, adding some ships and support facilities to all the ports creates a new set of targets to be attacked. Again, no references in my books (real books!) or web searches has turned up much. One major problem, is we lack almost ALL naval vessels as used by both sides (excepting the Komars either WBS or colmak updated) Opinions and thoughts, please. I'm 99% done right now, but it'd be a simple matter to detail these regions, if enough feel it's necessary thanks!

File Name: DBS Terrain, Full File Submitter: Wrench File Submitted: 17 January 2011 File Category: Full Terrains Full DBS Terrain, Complete Someone asked for the full terrain, set up with all the goodies and fixes. So here it is. No readme is included, but you should all know the drill. If not, you'll figure it out!! Enjoy!! Wrench kevin stein Click here to download this file

can anyone tell me when did Assad International AP, at Latakia opened?? nothing in my searches has turned up anything!! TIA!

I agree. The precedent was set with the Baltimore and Maryland

that helps quite a bit! Bridges may be "problematic", as there's no rivers placed. The "undulations" of the terrain may prohibit their inclusion. I still have to build the Jordanian oil refinery complex at Zarqa, too

When I have a chance, I'll take a look at it. I haven't flown over it in a looooooooooooooooooong time!! just to be safe, make sure all the ground objects are there, the cat pointer is pointing to (wherever) it should be, and the usual checks

arty duel across the canal...

same guy

did you hex edit the tank lod internally to change the skin name? check the Attachment Type = iirc, it's W_Germany (with the underscore)

NICE!!!

just release it. that's what I did when I did the upgrade a few year back.

radiators, yes. oil coolers, don' t know, but as it's a radiator??

min/max extents are set only in max (but are possibly 'adjustable' in the data ini). More ot less, if I under stand them correctly, they describe the physical space the object takes up. I do recall GregoryP making adjustments to them on some of the AvHistory FMs. this is from TKs Mirage3C, from the fuselage section: you can see they don't exactly match each other, which is what one would assume (oh! that word!!) if they describe the exact "space" taken up the 'world'. As I under stand collision points -- and I'm probably quite wrong -- they are the spots that the model "touches" other things, like mid-air collisions, missile and gun hits, the ground and so forth. In truth, I think a 3d guy might have to answer that one, cause I might be waaaaaaaaaaaaay off the beam!

great stuff!! Been on the HORNET some years back when we were in Frisco. Really want to see YORKTOWN at Patriot's Point. Of course, can't forget MIDWAY down south of me in San Diego, it's on my short list!