Note: this is an EXE installer that creates shared texture folders and adds paths to your autoexec.cfg.
Su-27 Fictional Skins: US Navy Fighter Squadrons
for DCS World 1.2.14 and later
Volume I of II
This is a collection of eight skins representing three US Navy fighter squadrons using historical F-14 Tomcat liveries.
The squadrons included are:
VF-21 Freelancers (CAG, CO, Line birds)
VF-103 Jolly Rogers (CAG, CO, Line birds)
VF-124 Gunfighters (CO, Line birds)
The VF-103 skins date from their 2000 deployment with CVW-17 on the USS George Washington. Included as the CO bird is the famous "Santa Cat", which has the jolly roger decked out in Christmas gear.
Most markings have been westernized, and the pilots have been given USN flightsuits with Naval Aviator wings and squadron patches. The helmet remains Russian made.
These skins were inspired by Clave's Deviant Art gallery:
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 autoexec.new, 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.
1.0 Initial Release
1.01 Made compatible with DCS World 1.2.6
1.05 Changed wheels/undercarriage to white
Minor texture fixes
1.06 Fixed for DCS World 1.2.14
1.10 General Texture Improvements
1.10a Added Installer
1.11 Updated for DCS World 1.5.5
Added USAF Aggressors nation
1.12 Added rank to pilots
Minor texture enhancements
1.13 Updated installer for DCS 2.5 and DCS Legacy 1.5
If you have any squadron requests, please PM me. If possible, provide top and profile views of the aircraft, preferably line art (much easier to extract color), and for CAG/CO birds, a close up of the tail fin is greatly appreciated.
You are free to use any of these skins in other projects as long as proper credit is provided in the readme file.