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
-
US Navy Attack Squadron 97 (VA-97) "Warhawks" Skin Pack
By HomeFries
VA-97 was commissioned in 1967 and flew the A-7 Corsair. In 1968, the squadron deployed to Vietnam as part of Carrier Air Wing 14 (CVW-14) embarked on the USS Constellation. VA-97 conducted a second combat deployment with CVW-14 in 1969, where they flew over 2500 sorties. VA-97 conducted two more Vietnam combat deployments in 1971 and 1972. The Warhawks returned to Vietnam for a fifth time in 1975 in support of Operation Frequent Wind, the evacuation of Saigon. In early 1980, VA-27 provided air cover for Operation Eagle Claw, the failed attempt at rescuing the American hostages in Iran.
In January 1991, the Warhawks transitioned to the F/A-18 and were redesignated Strike Fighter Squadron 97 (VFA-97). Today the Warhawks fly the F/A-18E Super Hornet out of NAS Lemoore, CA, and they are slated to be the first fleet squadron to transition to the F-35.
This is a fictional skin pack of Su-25Ts painted like the A-7E Corsair II in accordance with MIL-STD-2161A(AS) with VA-97 markings circa 1986. There are four different skins with unique Modexes (side numbers) and historically correct BuNos (serial numbers). This allows you to create packages of unique 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.
Most markings have been westernized, and the pilots have been given US style flightsuits with US markings. The helmet remains Russian made (but with a black oxygen mask).
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.
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.
Fly Navy!
-Home Fries
15 downloads
-
Su-33 Fictional Skins: US Navy Fighter Squadrons (Volume II)
By HomeFries
Su-33 Fictional Skins: US Navy Fighter Squadrons (Volume II)
for DCS World 1.2.16 and later
This is a collection of seven skins representing three US Navy fighter squadrons using historical F-14 Tomcat liveries. The squadrons included are:
VF-2 Bounty Hunters (CAG, Line birds)
VF-111 Sundowners (CAG, Line birds)
VF-213 Blacklions (CAG, CO, Line birds)
The VF-213 skins date from their 2005 deployment with CVW-8 on the USS Theodore Roosevelt (the "Tomcat Farewell Tour").
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.
The VF-2 skins were inspired by GeorgeLKMT's VF-2 CAG skin for Dino Cattaneo's F-14D (for FSX), and the skin was also used as a starting point for my own VF-2 CAG skin.
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.
Su-33 template by jamison1982.
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.
Fly Navy!
-Home Fries
15 downloads
(0 reviews)0 comments
Updated
-
Su-33 Fictional Skins: US Navy Fighter Squadrons (Volume I)
By HomeFries
Su-33 Fictional Skins: US Navy Fighter Squadrons (Volume I)
for DCS World 1.2.16 and later
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.
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.
Su-33 template by jamison1982.
These skins were inspired by Clave's Deviant Art gallery:
http://ws-clave.deviantart.com/gallery/6112394?offset=432
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.
Fly Navy!
-Home Fries
15 downloads
-
Su-27 Fictional Skins: US Navy Fighter Squadrons (Volume I)
By HomeFries
Su-27 Fictional Skins: US Navy Fighter Squadrons (Volume I)
for DCS World 1.2.14 and later
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.
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.
These skins were inspired by Clave's Deviant Art gallery:
http://ws-clave.deviantart.com/gallery/6112394?offset=432
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.
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.
Fly Navy!
38 downloads
(0 reviews)0 comments
Updated
-
Su-27 Fictional Skins: US Navy Fighter Squadrons (Volume II)
By HomeFries
Su-27 Fictional Skins: US Navy Fighter Squadrons (Volume II)
for DCS World 1.2.14 and later
This is a collection of seven skins representing three US Navy fighter squadrons using historical F-14 Tomcat liveries. The squadrons included are:
VF-2 Bounty Hunters (CAG, Line birds) VF-111 Sundowners (CAG, Line birds) VF-213 Blacklions (CAG, CO, Line birds)
The VF-213 skins date from their 2005 deployment with CVW-8 on the USS Theodore Roosevelt (the "Tomcat Farewell Tour").
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.
The VF-2 skins were inspired by GeorgeLKMT's VF-2 CAG skin for Dino Cattaneo's F-14D (for FSX), and the skin was also used as a starting point for my own VF-2 CAG skin.
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.
Be sure to download Volume I.
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.
Fly Navy!
-Home Fries
33 downloads
(0 reviews)0 comments
Updated
-
UH-1 USMC HMLA-269 "Gunrunners" Skin Pack
By HomeFries
Marine Attack Helicopter Squadron (HMA) 269, commissioned in July 1971 at MCAS New River, NC, has the distinction of being the first Attack hHelicopter squadron in the Marine Corps. HMA-269 flew the AH-1J until December 1977, when it received the AH-1T. The Gunrunners then made history again in 1979 by being the first Marine Squadron to fire a TOW missile from an airborne platform.
In the early 1980s, HMA-269 received its first UH-1N Hueys, and as a permanent composite squadron was redesignated HMLA-269. Since then, the Gunrunners have deployed to hotspots such as Iraq, Kosovo, Somalia, Liberia, Haiti, and Afghanistan.
Today the HMLA-269 "Gunrunners" fly the UH-1Y Venom and the AH-1W Super Cobra.
This is a collection of six UH-1 skins representing HMLA-269. The skins included are:
HF-00 (2010)
HF-01
HF-04
HF-07 (ca. 2009)
HF-22
HF-44
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.
Skinner's Philosophy:
Because the 3D models used for the aircrew utilize modern flight gear I have chosen to model the skins as "modern aircraft with nostalgic patterns", as opposed to actual historical skins.. The significance of this is that I have chosen to skin the aircrew in contemporary flight uniforms. I felt that this was more fitting in a setting that involves modern orders of battle, and is also less of an immersion-killer than seeing Vietnam era "uniforms" on clearly modern objects.
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 was posthumously awarded the Medal of Honor in the Global War on Terror, and 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
13 downloads
(0 reviews)0 comments
Submitted
-
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
-
UH-1 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 collection of eleven UH-1 skins representing HMLA-167. The skins included are:
TV-30 (1969 as HML-167)* TV-29 (1970 as HML-167)* "Santa 1" (1969 as HML-167) TV-30 (1982 as HML-167) TV-11 (1999) TV-03 (ca. 2003) TV-06 (ca. 2003) TV-04 (ca. 2005) TV-06 (ca. 2005) TV-05 (CO bird ca. 2008) TV-00 (UH-1Y CO bird ca. 2013)
* TV-29 and 30 (1969-70) are also included in my USMC Vietnam Skin Pack version 1.21 and later.
Each skin (1999 and later) 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.
Skinner's Philosophy:
Because the 3D models used for the aircrew utilize modern flight gear I have chosen to model the skins as "modern aircraft with nostalgic patterns", as opposed to actual historical skins.. The significance of this is that I have chosen to skin the aircrew in contemporary flight uniforms. I felt that this was more fitting in a setting that involves modern orders of battle, and is also less of an immersion-killer than seeing Vietnam era "uniforms" on clearly modern objects.
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 was posthumously awarded the Medal of Honor in the Global War on Terror, and 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
13 downloads
(0 reviews)0 comments
Updated
-
UH-1 USMC Marine Expeditionary Unit Skin Pack
By HomeFries
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
10 downloads
(0 reviews)0 comments
Updated
-
MiG-29A Czech Republic, 1st Fighter Aviation Regiment #7702 (ca. 1993)
By HomeFries
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.
28 downloads
-
MiG-29A Georgian Skin (Fictional)
By HomeFries
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.
18 downloads
-
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
-
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
-
18th Fighter Wing For Flaming Cliffs 3
By Dave
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
116 downloads
-
A-10C DCS Michigan ANG Skin
By Dave
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
61 downloads
(1 review)0 comments
Updated
-
Flaming Cliffs 3 F-15 Skins
By Dave
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
257 downloads
-
Mod Eagle Skin Pack for Flaming Cliffs 3
By Dave
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
159 downloads
-
Flaming Cliffs 3 ANG F-15 Skins
By Dave
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
141 downloads
-
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
Sign in to follow this
Followers
0
-
Download Statistics
14,331
Files12,608
Comments26,977
Reviews