Wrench

you've flown too far to the Edge of the World ™ and hit The Wall. there's an 80km buffer from the edge of every terrain, flying into it, will give the observed results. Watch the in-flight map, and try to stay away from it

ain't that what I said I my post??? and if someone is clever enough, and talented enough, can actually DO it as East Africa; adding in the necessary lakes and so forth. A couple of years ago, I rotated the HFD/TFD and gave it someone that asked, but nothing has ever materialized from it. I've not idea of what value such a terrain would be, but ... there ya have it

Thai Fighters ...

add on (third party) planes that do NOT show up in the selection drop down are usually caused by improper/incorrect installation flying outside they're operational year ranges all the other aircraft listed by both the posters (CF-104s, MiG-21SM, etc) are NOT player flyable aircraft. By default, NO "Red Side" aircraft are player flyable. OTH, for some reason, neither are the Starfighers (a very long story, and not relevant here). one way to cross check "player flyability", is to simply open the main ini of one of the non-flyables (example: MiG-21MF.ini) and compare that to the main ini of one of the flyables (example: F-4E_.ini) The differences are QUITE obvious! So, no, the aircraft aren't really missing, just not (by default!) not Player Usable ™.

wouldn't that have been spelling out in the readme enclosed with the package??

File Name: SF2 WW2 ETO, "D-Day" Spitfire IX Blank Skin set File Submitter: Wrench File Submitted: 13 January 2015 File Category: Spitfire SF2 WW2 ETO, "D-Day" Spitfire IX Blank Skin set 1/12/2015 -- Something for the WW2 ETO players -- = For SF2, Full-5 Merged (w/whichever Expansion Pak gave us the Spitfire IXc) = Using my Home Grown Templates ™ for the stock 3rd Wire Spirfire 9c, this skin set adds the D-Day Invasion stripes set. This is a "blank" skin, with no marking other than the Invasion Stripes, and can be used with any of the available decal sets for the stock Mk.IXc AND Mk.IXe. A simple rename of the textures will allow it's usage on either one. See "Notes" for more details. The stripes represented here are the 'full' set, top/bottom of wings and fully wrapping around the fuselage, as used from June 6, 1944 to approx September 44 (ish). The Sky ID band has been omitted, although photographic evidence exists of it having been used, even with the Invasion stripes. Yellow wing IFF bands remain. REMINDER-- this is not a 'full' ready-to-use skin pak. The folder is just named "DDAY" for convience. You'll have to create specifically named skin folders (ie: 411-DDay, for example) for proper, historical usage. There is no decals or texture set inis included -- however, a "base" texture set showing the in-game labeling is included, but NOT usable per se. It's just there to show how to set the Displayed Name labeling. As the mapping for both the 9c and 9e is identical, as are their respective decal positions, any of the existing Spifire 9 decal sets can be reused with this skin. As always, fairly easy to follow, yet detailed install instructions are included. So, please =READ= them !!!. Happy Hunting! Wrench Kevin Stein Click here to download this file

very nice!!

interesting .... it only seems to open LODs that already in a mods folder; ie: within an already existing aircraft folder. As some may remember, there are NO lods in any of the object cats since one of the 2012 patchs. Many of us have archived extracted "pre lock" object cats. This don't seem to open them from their extracted folders. doesn't seem to have any issues opening a lod from WITHIN an in-game aircraft's folder, where all the inis and textures and so forth reside.

the correct statement is OpenCockpit= but that may cause additional problems

ok, then, well why don't one of you that has the "non defective" file, upload the zip of the viewer to this thread as an attachment???

can't download it ... eset is blocking the site. how about attaching the zip to the post above? --- another question, does it read both ANSI and Unicode?

File Name: SF2 WW2 MTO Spitfire Mk.IX, Polish Fighting Team Skinpak File Submitter: Wrench File Submitted: 08 January 2015 File Category: Spitfire SF2 WW2 MTO Spitfire Mk.IX, Polish Fighting Team Skinpak 1/8/2015 -- Something for the Med players -- = For SF2, Full-5 Merged (Reccomended/Preferred) = *This mod will NOT work in SF/Wo* 1stGen game installs, at any patch level. One should also have the SF2I expansion pak, that gave us the Spitfires, as this mod REQUIRES the 3W Spitfire Mk.IX, This package contains a new skin for MTO (specificly Tunisian) based RAF Spitfire Mk.IXs. It represents "C" Flight, No. 145 Squadron, aka "Polish Fighting Team" All marking are decals, and decal randomization is TRUE for the 16 plane-in-squadron and serial number decals. Serial numbers marked with a star (*) are 100% historically matched to their plane-in-squadron number. Those marked with a cross (+, ok the plus sign!), while having served with the PFT, could not be matched to a specific aircraft. Those without any markings, are 'generic'. It should be noted, that the PFT used numbers, instead of letter for their individual IDs. Please note, this is just the skin/decal set. I've not included any of the bits needed to make the aircraft Player Flyable ™. There's plenty of other mods that do this. When in game, on the Loadout Screen, you'll see Polish Fighting Team (145 Sqdn) in the upper right skin selection drop down. As always, fairly easy to follow, yet detailed install instructions are included. So, please read them. Good Hunting! Wrench Kevin Stein Click here to download this file

I've never really had problems with infantry. Mainly because I've usually rewritten the movements ini to account for the slow pace of the troops. In fact, most movement inis for all the stock terrains have their waypoints set too far apart. Which is (kinda) ok for tanks, but even their guns don't have the ranges their Real World ™ counterparts have. There's only a couple of ways around it ... don't use infantry give them (exceedingly) unrealistic movement speeds (ie: truck --this was done purposefully in the Falklands mod) recompute/rewrite the GroundAttack sections of the terrain's movement.ini, to move the "engagement" points LESS than 1 tile width apart (apporx 2km) or have them "already there" emplaced via addition to the _targets and _types inis, allowing them to "support" the AFVs. The same can also be said for artillery units -- defending units should already be there (again, placed via _targets and _types ini edits) the last one is the most difficult, as it ensures one side or the other will always have a 'friendly' unit (somewhere) in Enemy Territory. That may also cause issues with (enemy) side strike missions being tasked against them.

Removal of rocket stub on stock 3rd Wire Spitfire 9E (clipped wing) For some reason, this bird has 6 rocket mounting stubs. Which the Mk.9 never seemed to have. So, with the following edits, they can be removed from the aircraft. If you don't have the data ini extracted, you'll need to do that first. If you have one already in the Spitfire9e's folder (like from one of my mods), good for you!! Ok, so we open the data in and scroll down to the AircraftData section, where the major components are spelled out. Copy/paste the text below inbetween that section and the next one (the fuselage section) Save the data ini, then close it! You've just returned the aircraft to it's proper form Now...all we need is the right shaped 55 gallon slipper tank!! Happy Flying!

or just switch the canopy to manual animation. There's a tutorial in the 1stGen Knowledge Base on "How To" (check the 'things you need to up date thread, too -- that one was specifically designed for the 08 patch) gun sounds are changed in the GunData.ini (and will need the necessary wav added to the /Sounds folder). You may also have to edit the Soundlist. ini, unless the wav has the exact same name the shadow is controlled by a statement in the main ini (F-84G.ini)

proof it can be done without decals .. if one knows what one is doing stock Mk.9 Spitfire for D-Day!

cool! Allison 1710s sound different from Merlins, which sound different from DB601s -- which I had the distinct honor/pleasure of hearing a REAL 601 in a Emil ( a REAL Emil -- not a fake one!!) some year back, when it flew into Santa Monica Airport. A very different sounding inline!!

with "new purchase" versions of SF2, they can be installed in any order, as they are all "current" with each other ------ Dave, I think THIS is what you're talking about: http://combatace.com/topic/82326-running-mods-from-a-different-disk-partition/ migbuster's excellent tutorial

along with a discussion in the FE forums, I choose to go the other way ... import an FE2 bird into SF2 (in this case, my ETO mods folder). SPAD over London (one could also say, this is for an airshow?)

if the aircraft is not experiencing any abnormalities (like flipping over and/or blowing up), I wouldn't worry about it!!

I've got the old 'merlin' one that we've been using since 2004 ... unzip, and drop in the /Menu folder

yes, rotate the terrain 90 to the right (east). it's east Africa, approximately Mozambique it's in "standard" 3W World size -- 64% of reality, like all the stock maps