Jump to content

SF2 WW2 ETO, "D-Day" Spitfire IX Blank Skin set

   (1 review)
Sign in to follow this  

1 Screenshot

About This File

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




User Feedback

You may only provide a review once you have downloaded the file.


×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..