This skin pack is a collection of fictional skins representing VMFP-3 flying the AJS-37 Viggen, and is intended for use for missions when the Viggen conducts electronic surveillance. The skins represent six line birds, each with separate MODEXes (side numbers) and accurate RF-4B 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 VMFP-3 markings ca. 1986-1988.
Prior to 1975, the US Marine Corps utilized composite reconnaissance squadrons (VMCJ) that contained RF-4B Phantoms for multi-sensor imagery reconnaissnace and EA-6A Electric Intruders for escort jamming. In 1975, Marine Tactical Reconnaissance Squadron 3 (VMFP-3) was activated at MCAS El Toro, California and was assigned all RF-4B aircraft in the Marine Corps inventory (VMAQ-2 at MCAS Cherry Point was assigned all EA-6A aircraft). VMFP-3 would detach aircraft to support the Fleet Marine Force throughout the world until its decommissioning in 1990, when the imagery reconnaissance mission was assumed by the F/A-18D Hornet and the RF-4B was retired from service.
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.
1.0 Initial Release
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.