US Navy VF-24 Corsairs Skin Pack for DCS F-86F

Home > User Files > US Navy VF-24 Corsairs Skin Pack for DCS F-86F
DCS World
F-86F Sabre

US Navy VF-24 Corsairs Skin Pack for DCS F-86F

Type - Skin
Uploaded by - Home Fries
Date - 05/28/2015 21:13:33
Note: this is an EXE installer that creates shared texture folders and adds paths to your autoexec.cfg.

This is part of a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable).

Fighter Squadron 24 flew the FJ-3 Fury for a short time (1956-1957) before transitioning to the F3H Demon.  This skin pack features skins fr om the 1956-57 deployment aboard the USS Shangri-La (CVA 38) as part of Carrier Air Group 2 (CVG-2, Tailcode M).

Note: this skin pack uses an EXE installer that creates common texture folders and an autoexec.cfg (if you already have one, you can make manual changes). I would like your feedback on this system; if it works I intend to apply it to my other skin packs.  If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders.  Be sure to update any missions that used 1.x series skins.

Updating from the 1.x series of FJ-3 Skins:

With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek.  As such, organizational specific modex placement as well as modex placement on the wing is no longer possible.  The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection.  For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail).

If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders.  Be sure to update any missions that used 1.x series skins.  Be sure to update missions that use version 1.xx of these skins, as the old folder names are now obsolete.

For Compact Installations - A Note About Autoexec.cfg:

Rather than copying texture files to their respective livery folders, I prefer to use a series of common texture folders along with unique filenames.  This allows a single instance of many of my common textures, and keeps the hard drive footprint to a minimum (especially nice if you run a SSD for your system drive).

The installer will add a series of folders to the DCS Texture path; if you do not have these folders created, then it is no  problem.  The autoexec.cfg included will automatically point to the Texture folder in your Saved Games\DCS folder, and regardless of whether you run the Release, Open Beta, or Legacy version of DCS, the path will always point to your Saved Games\DCS\Texture folder.  Again, this saves space on your hard drive.

If you use your own Autoexec.cfg, then when prompted to overwrite you can click "no".  This will create a file called, and you can manually make the updates as you like.  Just don't modify the top line with the file date; this is used by the installer for version control.  However, feel free to include it in your existing autoexec.cfg, so you don't get prompted to overwrite until there's another update to the autoexec.cfg.

If you inadvertently overwrite your autoexec.cfg, it is actually backed up as autoexec.old.  Just open it and copy the appropriate information to the new file.

For Traditional Installations or JSGME Compatible Extractions:

If you don't wish to use the shared texture folder and custom autoexec.cfg, you have a couple of other options available.  Selecting the Traditional Install copies all textures to each livery folder, then copies each livery to each version of DCS detected (up to three versions, including release, legacy 1.5, and open beta).  As a result, the listed hard disk space requirement assumes all three DCS versions are installled.   Each skin is independent and portable.

If you wish to install to a location other than your Saved Games folder, you must select the Single JSGME Extraction, or else the installation will fail for not detecting existing Saved Games\DCS folders.  Selecting this option will create a JSGME compatible install that can be dropped directly into your JSGME _MODS folder for installation.  Each skin is independent and portable.

For either of these installation options, if there is an issue with textures not displaying, then it is likely a problem with the installer.  Please let me know what textures are missing so that I can troubleshoot the issue.

Change Log:
1.1    Initial Baseline Release for DCS World 1.2.16
1.11    Bug fix with description.lua files
2.0    Updated for DCS World 1.5.4/2.0.3 model
    Skin-based modexes (and decals) replaced by generic nose number.
2.0a    Added missing texture
    Updated Installer
2.1    Updated Specular files for DCS 2.5
    Added USAF Adversaries to available nations
    Updated installer for DCS 2.5 and DCS Legacy 1.5
2.11    Updated Specular texture
2.20    Added RoughMet textures for DCS 2.5 compatibility

Detail placement in textures based on USN skins by Crazyeddie.
Special thanks to SkateZilla for the awesome Photoshop template.

You are free to use any of the textures in other skins or projects as long as proper credit is provided in the readme file.

-Home Fries
  • License: Freeware - Free version, Do Not Redistribute
  • Language: Any language
  • Size: 19.11 Mb
  • Downloaded: 1638
  • Comments: 0
Tags: USN, VF-24, FJ-3, F_86