AJS-37: US Marine Corps VMA(AW)-332 "Moonlighters"

Accueil > Fichiers Utilisateurs > AJS-37: US Marine Corps VMA(AW)-332 "Moonlighters"
DCS: World
AJS-37 Viggen

AJS-37: US Marine Corps VMA(AW)-332 "Moonlighters"

Type - Skin
Uploadé par - Home Fries
Date - 05.08.2017 23:58:43
This skin pack is a collection of fictional skins representing the Moonlighters flying the AJS-37 Viggen, an aircraft with an all weather strike role similar to the A-6.  The skins represent a CO bird, and seven line birds, each with separate MODEXes (side numbers) and accurate A-6 BuNos (serial numbers).  The tactical grey pattern is based on the MIL-STD-2161A(AS) pattern for the F-4 Phantom, which has a fuselage shape similar to the AJS-37 Viggen.  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.  All organizational markings are based on VMA(AW)-332 markings from 1991-1993.

Marine All-Weather Attack Squadron 332 (VMA(AW)-332) was commissioned in 1943 as Marine Scout Bomber Squadron 332 (VMSB-332), and flew the SBD Dauntless in the World War II Pacific theater. Following World War II, the squadron transitioned to the TBM Avenger and was redesignated Marine Torpedo Bombing Squadron 332 (VMTB-332).  VMTB-332 was deactivated in 1945, and was recommissioned as Marine Attack Squadron 332 (VMA-332) in 1952, when it would fly the  F6F Hellcat and F4U Corsair.  It was during this timeframe that VMA-332 took nickname "Polka Dots," along with the gentlemanly hat and cane logo.  From 1953-1957, VMA-332 flew the AD-1 Skyraider, after which it transitioned to the A-4 Skyhawk.  In 1962, VMA-332 changed its nickname to the "Moonlighters."

In 1968, the Moonlighters transitioned to the A-6 Intruder and were redesignated with the all-weather designation (VMA(AW)-332). The Moonlighters flew the Intruder until 1993, when they were redesignated VMFA(AW)-332 and transitioned to the two-seater F/A-18D Hornet, which they flew until their decommissioning in 2007.

For Compact Installations - A Note About Autoexec.cfg:

Rather than copying texture files to their respective livery folders, I prefer to use a series of common texture folders along with unique filenames.  This allows a single instance of many of my common textures, and keeps the hard drive footprint to a minimum (especially nice if you run a SSD for your system drive).

The installer will add a series of folders to the DCS Texture path; if you do not have these folders created, then it is no  problem.  The autoexec.cfg included will automatically point to the Texture folder in your Saved Games\DCS folder, and regardless of whether you run the Release, Open Beta, or Legacy version of DCS, the path will always point to your Saved Games\DCS\Texture folder.  Again, this saves space on your hard drive.

If you use your own Autoexec.cfg, then when prompted to overwrite you can click "no".  This will create a file called autoexec.new, and you can manually make the updates as you like.  Just don't modify the top line with the file date; this is used by the installer for version control.  However, feel free to include it in your existing autoexec.cfg, so you don't get prompted to overwrite until there's another update to the autoexec.cfg.

If you inadvertently overwrite your autoexec.cfg, it is actually backed up as autoexec.old.  Just open it and copy the appropriate information to the new file.

For Traditional Installations or JSGME Compatible Extractions:

If you don't wish to use the shared texture folder and custom autoexec.cfg, you have a couple of other options available.  Selecting the Traditional Install copies all textures to each livery folder, then copies each livery to each version of DCS detected (up to three versions, including release, legacy 1.5, and open beta).  As a result, the listed hard disk space requirement assumes all three DCS versions are installled.   Each skin is independent and portable.

If you wish to install to a location other than your Saved Games folder, you must select the Single JSGME Extraction, or else the installation will fail for not detecting existing Saved Games\DCS folders.  Selecting this option will create a JSGME compatible install that can be dropped directly into your JSGME _MODS folder for installation.  Each skin is independent and portable.

For either of these installation options, if there is an issue with textures not displaying, then it is likely a problem with the installer.  Please let me know what textures are missing so that I can troubleshoot the issue.

Change Log:
1.0        Initial Release
1.01        Squadron ID relocated based on USMC conventions    
1.03        Applied ARAK M70B textures
        Updated Installer for DCS 2.5

If you have any squadron requests, please PM me.  If possible, provide top and profile views of the aircraft, preferably line art (much easier to extract color), and for CAG/CO birds, a close up of the tail fin is greatly appreciated.

You are free to use any of these skins in other projects as long as proper credit is provided in the readme file.

Fly Navy!

-Home Fries
  • Licence: Freeware - Version Gratuite, Ne Pas Redistribuer
  • Langue: N'importe quel langage
  • Taille: 227.71 Mo
  • Téléchargé: 894
  • Commentaires: 0