Jump to content

Ka-50 USMC HMLA-269 "Gunrunners" Skin Pack 1.12a

   (0 reviews)
Sign in to follow this  

7 Screenshots

About This File

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 fictional skin pack of Ka-50 Black Sharks with HMLA-269 markings. There are six 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


What's New in Version 1.12a

Released

  • Updated Installer



User Feedback

Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..