SUBCATEGORIES
- A-10A/C Skins
- F-15C Skins
- Su-25 Skins
- SU-25T Skins
- Su-27 Skins
- Su-33 Skins
- Mig-29A/G/S Skins
- Misc/AI Aircraft Skins
-
Ka-50 USMC HMLA-167 "Warriors" Skin Pack
By HomeFries
Marine Light Helicopter Squadron (HML) 167 was commissioned in April 1968 in Vietnam, and flew the UH-1E in combat operations until June 1971, where it was the last Marine helicopter squadron in Vietnam. Of note, HML-167 was the first unit to drop a bomb from a helicopter, accomplished with the use of the Helicopter Trap Weapon (HTW). In June 1971, HML-167 returned stateside to MCAS New River, North Carolina, as part of the 2nd Marine Air Wing.
In 1972, HML-167 received the UH-1N Twin Huey, which it would fly until 2012 when the UH-1N was replaced by the UH-1Y Venom. In 1984, HML-167 received its first AH-1T Cobras and became a composite squadron of Cobras and Hueys. HML-167 was redesignated Marine Light Attack Helicopter Squadron (HMLA) 167 in April 1986, and as such designated as a permanent composite squadron of both Cobras and Hueys. HMLA-167 began upgrading to the AH-1W Super Cobra in late 1989.
Today the HMLA-167 "Warriors" fly the UH-1Y Venom and the AH-1W Super Cobra.
This is a fictional skin pack of Ka-50 Black Sharks with HMLA-167 markings. There are five different Modexes (USN/USMC side numbers) allowing you to create packages of different aircraft. Each skin has a "normal" version and a weathered version. Weathered skins have a bleached effect as if the aircraft were heavily exposed to the sun for months on end. Normal skins include pilots with green flightsuits, while weathered skins include pilots with desert flightsuits.
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.
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 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.
For Traditional Installations:
If there is an issue with textures not displaying, it is likely a problem with the installer. Please let me know what textures are missing so that I can troubleshoot the issue.
Special thanks to EricJ for his USMC Ka-50 skin, which I used as the basis for this skin pack as well as the bleaching effects for weathered skins.
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
8 downloads
(0 reviews)0 comments
Updated
-
UH-1 USMC HMLA-169 "Vipers" Skin Pack
By HomeFries
Marine Attack Helicopter Squadron (HMA) 169 was commissioned in 1971 as part of Marine Aircraft Group 39 (Camp Pendleton, cA), and unlike most HMLA squadrons began with the Cobra (AH-1G) before becoming a composite squadron. By 1976, the AH-1G was replaced by the AH-1J Sea Cobra, which were eventually replaced by the AH-1T.
In 1986, HMA-169 was redesignated Marine Light Attack Helicopter Squadron (HMLA) 169, and replaced its AH-1Ts with the AH-1W Super Cobra. As a composite squadron, it also received its complement of UH-1N Hueys.
Today HMLA-169 flies the UH-1Y Venom and the AH-1Z Viper.
This is a fictional skin pack of SA342L/M/Mistral Gazelles with HMLA-169 markings. Each SA342 variant has four different BuNos (USN/USMC serial numbers), including one high color Commanding Officer's bird, allowing you to create packages of different aircraft. You still provide your own two digit MODEX (side number) in the mission editor. Each skin has a "normal" version and a weathered version. Weathered skins have a bleached effect as if the aircraft were heavily exposed to the sun for months on end. Normal skins include pilots with green flightsuits, while weathered skins include pilots with desert flightsuits. This skin pack is intended to satisfy one's "cobra itch" until the AH-1 is released.
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.
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.
9 downloads
(1 review)0 comments
Updated
-
SA342 USMC HMLA-169 "Vipers" Skin Pack
By HomeFries
Marine Attack Helicopter Squadron (HMA) 169 was commissioned in 1971 as part of Marine Aircraft Group 39 (Camp Pendleton, cA), and unlike most HMLA squadrons began with the Cobra (AH-1G) before becoming a composite squadron. By 1976, the AH-1G was replaced by the AH-1J Sea Cobra, which were eventually replaced by the AH-1T.
In 1986, HMA-169 was redesignated Marine Light Attack Helicopter Squadron (HMLA) 169, and replaced its AH-1Ts with the AH-1W Super Cobra. As a composite squadron, it also received its complement of UH-1N Hueys.
Today HMLA-169 flies the UH-1Y Venom and the AH-1Z Viper.
This is a fictional skin pack of SA342L/M/Mistral Gazelles with HMLA-169 markings. Each SA342 variant has four different BuNos (USN/USMC serial numbers), including one high color Commanding Officer's bird, allowing you to create packages of different aircraft. You still provide your own two digit MODEX (side number) in the mission editor. Each skin has a "normal" version and a weathered version. Weathered skins have a bleached effect as if the aircraft were heavily exposed to the sun for months on end. Normal skins include pilots with green flightsuits, while weathered skins include pilots with desert flightsuits. This skin pack is intended to satisfy one's "cobra itch" until the AH-1 is released.
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.
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 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.
For Traditional Installations:
If there is an issue with textures not displaying, it is likely a problem with the installer. Please let me know what textures are missing so that I can troubleshoot the issue.
pecial thanks to Upuaut for his templates that were used to create the flightsuit torso and legs.
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
15 downloads
(0 reviews)0 comments
Updated
-
SA342 USMC HMLA-167 "Warriors" Skin Pack
By HomeFries
Marine Light Helicopter Squadron (HML) 167 was commissioned in April 1968 in Vietnam, and flew the UH-1E in combat operations until June 1971, where it was the last Marine helicopter squadron in Vietnam. Of note, HML-167 was the first unit to drop a bomb from a helicopter, accomplished with the use of the Helicopter Trap Weapon (HTW). In June 1971, HML-167 returned stateside to MCAS New River, North Carolina, as part of the 2nd Marine Air Wing.
In 1972, HML-167 received the UH-1N Twin Huey, which it would fly until 2012 when the UH-1N was replaced by the UH-1Y Venom. In 1984, HML-167 received its first AH-1T Cobras and became a composite squadron of Cobras and Hueys. HML-167 was redesignated Marine Light Attack Helicopter Squadron (HMLA) 167 in April 1986, and as such designated as a permanent composite squadron of both Cobras and Hueys. HMLA-167 began upgrading to the AH-1W Super Cobra in late 1989.
Today the HMLA-167 "Warriors" fly the UH-1Y Venom and the AH-1W Super Cobra.
This is a fictional skin pack of SA342L/M/Mistral Gazelles with HMLA-167 markings. Each SA342 variant has five different BuNos (USN/USMC serial numbers) allowing you to create packages of different aircraft. You still provide your own two digit MODEX (side number) in the mission editor. Each skin has a "normal" version and a weathered version. Weathered skins have a bleached effect as if the aircraft were heavily exposed to the sun for months on end. Normal skins include pilots with green flightsuits, while weathered skins include pilots with desert flightsuits. This skin pack is intended to satisfy one's "cobra itch" until the AH-1 is released.
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.
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 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.
For Traditional Installations:
If there is an issue with textures not displaying, it is likely a problem with the installer. Please let me know what textures are missing so that I can troubleshoot the issue.
Special thanks to Upuaut for his templates that were used to create the flightsuit torso and legs.
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
19 downloads
(0 reviews)0 comments
Updated
-
L-39C Fictional USN Desert Aggressor
By EricJ
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
8 downloads
(0 reviews)0 comments
Submitted
-
L-39C USAF Aggressor
By EricJ
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.
10 downloads
(0 reviews)0 comments
Submitted
-
L-39C VFC-12 Aggressor Splinter
By EricJ
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.
7 downloads
(1 review)0 comments
Submitted
-
L-39C Fictional CoNA Scheme
By EricJ
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.
7 downloads
(0 reviews)0 comments
Updated
-
L-39C Fictional Czech Winter Scheme
By EricJ
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.
5 downloads
(0 reviews)0 comments
Submitted
-
L-39C Fictional European 1
By EricJ
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.
6 downloads
(1 review)0 comments
Submitted
-
L-39C Fictional Arctic Scheme
By EricJ
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.
9 downloads
(0 reviews)0 comments
Submitted
-
L-39C FIctional Venezuelan Aggressor
By EricJ
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.
10 downloads
(1 review)0 comments
Submitted
-
L-39C Fictional South East Asia Scheme
By EricJ
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.
6 downloads
(1 review)0 comments
Submitted
-
L-39C Fictional Ferris No.3 Splinter
By EricJ
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.
9 downloads
(0 reviews)0 comments
Submitted
-
L-39C FIctional Russian White Splinter
By EricJ
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.
11 downloads
(1 review)0 comments
Submitted
-
L-39C Fictional Russian Desert Splinter
By EricJ
Based on an MIG-29 Prototype 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 Desert Splinter” and go fly
7 downloads
(2 reviews)0 comments
Submitted
-
L-39C Fictional Ukrainian Splinter
By EricJ
L-39C Fictional Ukrainian Splinter
Based on the Su-27 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 Ukraine and in the Payload Editor select “Fictional Ukrainian Splinter” and go fly
17 downloads
(2 reviews)0 comments
Submitted
-
F/A-18C Fight's On
By EricJ
Modeled on the F/A-18C, this livery from the USMC VMFA-312 is one of the more unique schemes devised based on Heather Ferris’s work. To use for the AI simply copy and paste the “Fights On” folder into the fa-18c folder, and let the AI go fly (or until the DCS: Hornet module comes out).
29 downloads
(2 reviews)0 comments
Submitted
-
A-10 Ferris Splinter [Fictional]
By EricJ
A-10 Ferris Splinter [Fictional]
This is a basic Splinter scheme based on an F-15C design modified for the A-10 airframe, and also some artistic liberties as well. While the A-10C is shown, this can also be used on the A-10A, simply copy and paste the folder into the Bazar\Liveries\A-10A or A-10C and select “Ferris Splinter No.1” in the Payload Menu and go fly.
22 downloads
(2 reviews)0 comments
Updated
-
FJ-3M VF-211 Red Checkertails Skin for DCS F-86F
By HomeFries
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
20 downloads
(0 reviews)0 comments
Updated
-
FJ-3 VF-191 Satan's Kittens Skin for DCS F-86F
By HomeFries
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
11 downloads
(0 reviews)0 comments
Updated
-
FJ-3M VF-142 Fighting Falcons Skin Pack for DCS F-86F
By HomeFries
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
8 downloads
(0 reviews)0 comments
Updated
-
FJ-3M VF-121 Pacemakers Skin for DCS F-86F
By HomeFries
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
9 downloads
(0 reviews)0 comments
Updated
-
FJ-3 VF-73 Jesters Skin Pack for DCS F-86F
By HomeFries
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
7 downloads
(0 reviews)0 comments
Updated
-
FJ-3 VF-24 Corsairs Skin for DCS F-86F
By HomeFries
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
9 downloads
(0 reviews)0 comments
Updated
Sign in to follow this
Followers
0
-
Download Statistics
14,212
Files12,494
Comments26,862
Reviews