DCS Aircraft Skins

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.
 
The Marine Expeditionary Unit (MEU) is a deployable, quick reaction air-ground task force of the United States Marine Corps (USMC) that includes both a battalion sized ground and support force as well as a group sized composite air component. The air assets are pulled from various stateside Marine squadrons and take on the squadron name and tail code of the medium lift squadron (formerly the CH-46 helicopter squadron, now the V-22 tiltrotor squadron), and the medium lift squadron is designated as "Reinforced" (e.g. "VMM-263 (Rein)"). Among the helicopter assets in the MEU are the UH-1N Huey (now the UH-1Y Venom) and the AH-1W Super Cobra or AH-1Z Viper, themselves taken from composite Marine Light Attack Helicopter (HMLA) squadrons.
 
Since the HMLA assets that comprise the Light Utility/Attack portion of the MEU are "on loan" to the medium lift squadron, they tend to paint their aircraft strictly to regulation, applying the tail code and modex (side number), painting over their own squadron insignia but not taking on the insignia of their host squadron. This may make for less interesting aircraft, but it makes for very easy skinning. As a result, I was able to create tails of each Reinforced HMM/VMM squadron that has deployed in a MEU, as well as modexes 30-47 (3x and 4x are normally the modexes used for HMLA assets in a MEU with one range for the UH-1 and the other for the AH-1). All of this allows for 168 separate combinations realistically representing the UH-1s that have deployed over the past 20 years, all with a minimum of textures. This allows the mission editor to create larger scale missions with unique skins for the UH-1 while keeping the texture overhead to a minimum, and allowing for realism at the same time!
 
Each of the Hueys in the reinforced squadrons use the proper modexes in their proper timeframes (with possible exceptions of a single isolated deployment or detachment during the timeframe), and where a reinforced squadron's UH-1 modex has shifted from 3x to 4x, a separate timeframe has been indicated in the skin name. In these instances, the skins spanning only the 1990s will feature Marines in green flightgear with all other skins featuring Marines in desert gear.
 
The following reinforced medium lift squadrons are represented (HMM are helicopter squadrons, H/VMM indicates both HMM and VMM tiltrotor squadrons):
HMM-161 (Rein) Greyhawks HMM-162 (Rein) Golden Eagles HMM-163 (Rein) Ridge Runners (aka Evil Eyes) HMM-164 (Rein) Knightriders H/VMM-165 (Rein) White Knights H/VMM-166 (Rein) Sea Elk H/VMM-261 (Rein) Raging Bulls HMM-262 (Rein) Flying Tigers H/VMM-263 (Rein) Thunder Eagles HMM-264 (Rein) Black Knights H/VMM-266 (Rein) Fighting Griffins HMM-268 (Rein) Red Dragons HMM-364 (Rein) Purple Foxes HMM-365 (Rein) Blue Knights

A note about the Crew Chief & Door Gunner:
 
Since enlisted US troops don't wear rank/rate insignia on flightsuits, their rank/rate is displayed on their nametag. Since there are no specific nametag textures for the crew chief/door gunner texture, I have added a nametag to the velcro on the chest armor (as is standard practice).
 
In choosing names for the texture, I opted for US servicemembers who received the Medal of Honor. CPL Jason Dunham represents the Unites States Marine Corps in these skins. The following is his Medal of Honor citation:
 
For conspicuous gallantry and intrepidity at the risk of his life above and beyond the call of duty while serving as Rifle Squad Leader, 4th Platoon, Company K, Third Battalion, Seventh Marines (Reinforced), Regimental Combat Team 7, First Marine Division (Reinforced), on 14 April 2004. Corporal Dunham's squad was conducting a reconnaissance mission in the town of Karabilah, Iraq, when they heard rocket-propelled grenade and small arms fire erupt approximately two kilometers to the west. Corporal Dunham led his Combined Anti-Armor Team towards the engagement to provide fire support to their Battalion Commander's convoy, which had been ambushed as it was traveling to Camp Husaybah. As Corporal Dunham and his Marines advanced, they quickly began to receive enemy fire. Corporal Dunham ordered his squad to dismount their vehicles and led one of his fire teams on foot several blocks south of the ambushed convoy. Discovering seven Iraqi vehicles in a column attempting to depart, Corporal Dunham and his team stopped the vehicles to search them for weapons. As they approached the vehicles, an insurgent leaped out and attacked Corporal Dunham. Corporal Dunham wrestled the insurgent to the ground and in the ensuing struggle saw the insurgent release a grenade. Corporal Dunham immediately alerted his fellow Marines to the threat. Aware of the imminent danger and without hesitation, Corporal Dunham covered the grenade with his helmet and body, bearing the brunt of the explosion and shielding his Marines from the blast. In an ultimate and selfless act of bravery in which he was mortally wounded, he saved the lives of at least two fellow Marines. By his undaunted courage, intrepid fighting spirit, and unwavering devotion to duty, Corporal Dunham gallantly gave his life for his country, thereby reflecting great credit upon himself and upholding the highest traditions of the Marine Corps and the United States Naval Service.
 
CPL Dunham is also the namesake of the USS Jason Dunham (DDG-109), the Marine Corps Security Force barracks in Kings Bay, GA, and Crucible stations at both MCRD Parris Island and MCRD San Diego.
 

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 Open Alpha, Open Beta, or Release 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.
 
 
 
Special thanks to upuaut for assistance with the more "exotic" material names, as well as the assistance with custom rotor colors.
 
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

NOTE: This only works with DCS World 1.2.16 or earlier. DCS World 1.5/2.0 uses a new MiG-29 model.
 

I originally did this at the request of a friend, who wished to have the Czech camouflage pattern on fictional Georgian MiGs. Once I completed the pattern, I decided that since the hard work was already done, I should just go ahead and finish the Czech skin. So this is a Czech MiG-29A of the First Fighter Air Regiment ca. 1993 (before the airframe was traded to Poland, where it currently serves). Since the Czech Republic is not a selectable nation, the nations who can use this skin are Russia, Ukraine, and Insurgents.
 
 
 
Installation:
 
These MiG-29A skins do not require you to overwrite any existing "slots"; they exist as individual skins using the standard definition.lua format. Simply put the skins in your Saved Games\DCS\Liveries\ folder; you should be able to extract using the path that exists in this archive file.
 
In order to have the MiG-29A (and this skin) available for the Insurgents in the Mission Editor, you will need to update the db_countries.lua file located in DCS World\Scripts\Database. Open the file in a text editor like Notepad++ and search for the following string:
-- INSURGENTS
This is the comment line that starts the Insurgents section.
 
In the first section,you will see the following entry:
cnt_unit( units.Planes.Plane, "P-51D");
This is the plane available to the Insurgents in the mission editor. Just add the following line:
cnt_unit( units.Planes.Plane, "MiG-29A");
This opens more possibilities for scenarios, and all of the included skins are available to the Insurgents as well as Russia and the Ukraine.
 
Special thanks to Jack for allowing the use and modification of his enhanced pylon texture, as well as his collaboration in developing MiG-29 skins that are not dependent on the original "slots" of the Flanker 2.5/LOMAC models.

NOTE: This only works with DCS World 1.2.16 or earlier. DCS World 1.5/2.0 uses a new MiG-29 model.
 

I originally did this at the request of a friend, who wished to have the Czech camouflage pattern on fictional Georgian MiGs. I used the Czech pattern as a starting point, then used the colors on the Georgian MiG-21 to finish the job. Once I completed the pattern, I eventually decided to release it to the public.
 
In addition to Georgia, the skin is available to Russia, Ukraine, and Insurgents.
 

Installation:
 
These MiG-29A skins do not require you to overwrite any existing "slots"; they exist as individual skins using the standard definition.lua format. Simply put the skins in your Saved Games\DCS\Liveries\ folder; you should be able to extract using the path that exists in this archive file.
 
In order to have the Georgian MiG-29A (and the skins) available for Georgia in the Mission Editor, you will need to update the db_countries.lua file located in DCS World\Scripts\Database. Open the file in a text editor like Notepad++ and search for the following string:
-- GEORGIA
This is the comment line that starts the Georgia section.
 
In the first section,you will see the following entries:
cnt_unit( units.Planes.Plane, "Su-25"); cnt_unit( units.Planes.Plane, "An-26B"); cnt_unit( units.Planes.Plane, "Su-25T"); cnt_unit( units.Planes.Plane, "L-39ZA"); cnt_unit( units.Planes.Plane, "Yak-40"); cnt_unit( units.Planes.Plane, "P-51D");
These are the planes available to Georgia in the mission editor. Just add the following line:
cnt_unit( units.Planes.Plane, "MiG-29A");
You may also optionally add that line to the section starting with
-- INSURGENTS
This opens more possibilities for scenarios, and all of the included skins are available to the Insurgents as well as Russia and the Ukraine.
 
 
 
Special thanks to Jack for allowing the use and modification of his enhanced pylon texture, as well as his collaboration in developing MiG-29 skins that are not dependent on the original "slots" of the Flanker 2.5/LOMAC models.

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 (the Corsairs which were later redesignated the VF-211 Checkmates, not to be confused with the VF-24 Renegades designated in 1959) flew the FJ-3 Fury for a short time (1956-1957) before transitioning to the F3H Demon. This skin pack features skins from 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.
 
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 Open Alpha, Open Beta, or Release 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.
 

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).
 

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

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 211 (the Red Checkertails which were later redesignated the VF-24 Renegades, not to be confused with the VF-211 Checkmates designated in 1959) flew the FJ-3M Fury from 1956-1957 before transitioning to the F8U-1 Crusader. This skin pack features skins from the 1956-57 deployment aboard the USS Bon Homme Richard (CVA-31) as part of Carrier Air Group 21 (CVG-21, Tailcode G).
 
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.
 
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 Open Alpha, Open Beta, or Release 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.
 

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).
 

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

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 191 flew the FJ-3 Fury from 1956-1957 before transitioning to the F11F-1 Tiger. This skin pack features skins from the 1957 deployment aboard the USS Yorktown (CVA-10) as part of Carrier Air Group 19 (CVG-19, Tailcode B).
 
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.
 
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 Open Alpha, Open Beta, or Release 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.
 

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).
 

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

This is the first in 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). The idea of this series is to have a single skin for each squadron, and separate decals for each side number (Modex). The last 4 digits of the serial number (BuNo) use the USAF serial number to allow for dynamic BuNos, though the side number must be selected by choosing the skin itself. This will allow a common Modex pool and a single texture for each squadron, thereby allowing you to employ an entire squadron in a mission while keeping the hard drive and in-mission RAM footprint to a minimum.
 
Fighter Squadron 142 (the Fighting Falcons, not to be confused with the VF-142 Ghostriders that was designated in 1963) flew the FJ-3M Fury for a short time (1956-1958), including a deployment on the USS Hornet (CVA-12) as part of Carrier Air Group 14 (CVG-14) before returning to NAS Miramar and transitioning to the F8L1-1 Crusader. This skin pack features skins from the 1957 Hornet deployment (CVG-14 Tailcode A) and the return to Miramar (1958) prior to transitioning to the Crusader. The 1958 skin displays the CVG-14 Tailcode NK, which replaced A once the US Navy went to 2 letter tailcodes.
 
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.
 
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 Open Alpha, Open Beta, or Release 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.
 

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).
 
 
 
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

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 121 flew the FJ-3M Fury operationally in 1957 before being redesignated as a Replacement Air Group (RAG). Of note, it was VF-121's status as a F-4 Phantom RAG at NAS Miramar that helped provide the squadron's reknown as the original host unit for the US Navy Fighter Weapons School ("Top Gun"). This skin pack features skins from the 1957 deployment aboard the USS Lexington (CV-16) as part of Carrier Air Group 12 (CVG-12, Tailcode D).
 
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.
 
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 Open Alpha, Open Beta, or Release 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.
 

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).
 

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

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 73 flew the FJ-3 Fury from 1956 until its decommissioning in 1958. Originally part of Carrier Air Group 7 (CVG-7, Tailcode L), VF-73 was transferred to CVG-4 (Tailcode AD) for its 1957 deployment on the USS Randolph (CVA-15). This skin pack features skins from CVG-7 and the 1957 Randolph deployment with CVG-4.
 
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.
 
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 Open Alpha, Open Beta, or Release 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.
 

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).
 

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

Flaming Cliffs 3 F-15C Skin Add On Pack by Dave USAFMTL Slavens
 
This skin packs contains 3 F-15C skins covering the 18th FW out of Kadena AB, Okinawa in the MOD Eagle paint scheme. I used the ED templates and parts of other templates made by Tom Weiss. Thank you both.
 
To install:
 
Just install to your DCS World directory and let it overwrite the folder names. It will not replace anything, just add.
 
Example:
X:\xxxxxxx\Eagle Dynamics\DCS World\Bazar

A-10C DCS Skin by Dave USAFMTL Slavens
 
This skin packs contains 1 A-10C skin from the 107th FS Selfridge ANGB, Michigan (MI)
 
I used the ED templates.
 
To install:
 
Just install to your DCS World directory and let it overwrite the folder names. It will not replace anything, just add.
 
Example:
X:\xxxxxxx\Eagle Dynamics\DCS World\Bazar

Flaming Cliffs 3 F-15C Skin Add On Pack by Dave USAFMTL Slavens
 
This skin packs contains 30 F-15A/C skins covering many units through the years of the F-15 Eagle. I used the ED templates and parts of other templates made by Tom Weiss. Thank you both.
 
To install:
 
Just install to your DCS World directory and let it overwrite the folder names. It will not replace anything, just add.
 
Example:
X:\xxxxxxx\Eagle Dynamics\DCS World\Bazar

Flaming Cliffs 3 F-15C Skin Add On Pack by Dave USAFMTL Slavens
 
This skin packs contains 8 F-15C skins covering:
 
The 36th FW out of Bitburg AB, Germany:
22nd, 53rd and 525th Fighters Squadrons.
 
The 3rd Wing, out of Elmendorf AFB, Alaska:
19th, 43rd and 54th Fighters Squadrons.
 
The 53rd FS, 52nd FW when it moved from Bitburg to Spangdahlem.
 
All in the MOD Eagle paint scheme.
 
Finally I did the 32nd Fighter Squadron out of Soesterberg AB, The Netherlands
 
I used the ED templates and parts of other templates made by Tom Weiss. Thank you both.
 
To install:
 
Just install to your DCS World directory and let it overwrite the folder names. It will not replace anything, just add.
 
Example:
X:\xxxxxxx\Eagle Dynamics\DCS World\Bazar

Flaming Cliffs 3 F-15 Skin Add On Pack by Dave USAFMTL Slavens
 
This skin packs contains 4 F-15 skins covering the ANG units from:
186th FS, 120th FW Montana ANG
125th FW Flagship Florida ANG
128th FS, 116th FW Georgia ANG
199th FS, 154th WG Hawaii ANG
 
I used the ED templates and parts of other templates made by Tom Weiss. Thank you both.
 
To install:
Just install to your DCS World directory and let it overwrite the folder names. It will not replace anything, just add.
 
Example:
X:\xxxxxxx\Eagle Dynamics\DCS World\Bazar

Based on an A-4 VA-126 scheme (loosely I might add but the colors are correct) and adapted for the L-39C airframe. To install simply copy and paste the Livery folder in DCSWorld/CoreMods/aircraft/L-39/Liveries folder, select Ukraine and in the Payload Editor select “Fictional USN Desert Aggressor” and go fly

This scheme is an adaptation of an F-15C scheme. To install simply copy and paste the Livery folder in DCSWorld/CoreMods/aircraft/L-39/Liveries folder, select USA and in the Payload Editor select “USAF Aggressor Splinter” and go fly.

This scheme is an adaptation of an F/A-18A VFC-12 scheme. To install simply copy and paste the Livery folder in DCSWorld/CoreMods/aircraft/L-39/Liveries folder, select USA and in the Payload Editor select “VFC-12 Aggressor Splinter” and go fly. Additional help from HomeFries, particularly his adjusted decals and warning stickers.

This scheme is an adaptation of an EA-18G VAQ-129 scheme for the Centennial of Naval Aviation observance. To install simply copy and paste the Livery folder in DCSWorld/CoreMods/aircraft/L-39/Liveries folder, select USA and in the Payload Editor select “Fictional CoNA Scheme” and go fly.

This scheme is a simple “Winter” scheme that I made based on the previous European 1 scheme, with some modifications. To install simply copy and paste the Livery folder in DCSWorld/CoreMods/aircraft/L-39/Liveries folder, select Czech Republic and in the Payload Editor select “Fictional Czech Winter Scheme” and go fly.

This scheme is a simple “Aggressor” scheme that is based on the basic European 1 scheme found on early A-10s. To install simply copy and paste the Livery folder in DCSWorld/CoreMods/aircraft/L-39/Liveries folder, select USA and in the Payload Editor select “Fictional European 1” and go fly.

This scheme is a simple “Aggressor” scheme that is based on an F-16 scheme. To install simply copy and paste the Livery folder in DCSWorld/CoreMods/aircraft/L-39/Liveries folder, select USA and in the Payload Editor select “Fictional Arctic Scheme” and go fly.

This scheme is a simple “Aggressor” scheme that I felt like doing for fun. To install simply copy and paste the Livery folder in DCSWorld/CoreMods/aircraft/L-39/Liveries folder, select USA and in the Payload Editor select “Fictional Venezuelan Aggressor” and go fly.

This scheme is a simple “blank” scheme that I felt like doing for fun. To install simply copy and paste the Livery folder in DCSWorld/CoreMods/aircraft/L-39/Liveries folder, select USA and in the Payload Editor select “Fictional SEA Scheme” and go fly.

Based on a Heather Ferris F-15C scheme, this represents a fictional skin for the new L-39 Module. To install simply copy and paste the Livery folder in DCSWorld/CoreMods/aircraft/L-39/Liveries folder, select Russia and in the Payload Editor select “Fictional Ferris Splinter No.3” and go fly.

Based on a Prototype MIG-29 SMT scheme, this represents a fictional skin for the new L-39 Module. To install simply copy and paste the Livery folder in DCSWorld/CoreMods/aircraft/L-39/Liveries folder, select Russia and in the Payload Editor select “Fictional Russian White Splinter” and go fly.