Jump to content
Sign in to follow this  
HomeFries

M-2000C: US Marine Corps Adversary Squadron VMFT-401 "Snipers"

Recommended Posts

M-2000C: US Marine Corps Adversary Squadron VMFT-401 "Snipers"


M-2000C: US Marine Corps Adversary Squadron VMFT-401 "Snipers"
for DCS World 1.5.6 and later

 

VMFT-401 was commissioned in 1986 and in 1987 received the IAI Kfir (designated F-21A) under lease from the Israeli government. The "Snipers" flew the Kfir until 1989, when it transitioned to the F-5E Tiger II. This skin is inspired by the 1987-89 timeframe in which USN and USMC flew the Kfir, a delta-wing aircraft of French origin.

 

The Kfir was built by IAI based on the Mirage V airframe. The closest flyable substitute to the Kfir in DCS is the M-200C, so this is a fictional skin that paints the M-2000C as a USMC adversary. This skins uses the traditional Israeli Air Force desert pattern that was used on some of the VMFT-401 adversary aircraft. Since the original aircraft were leased and kept much of their original markings, so is the case with the M-2000C skins. No original markings (e.g. rescue arrows and safety markings) were subdued to match US paint schemes. However, minor liberties were taken with the pilot skins in order to make the pilots look more American.

 


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 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, open alpha 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.

 

 

 

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


 

Share this post


Link to post
Share on other sites

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
Sign in to follow this  

  • Similar Content

    • By Menrva


      View File Operation Desert Storm: 30th Anniversary Edition
      Welcome To Duty
      Built with the extraordinary expertise and dedication of modders from CombatACE.com, Operation Desert Storm – 30th Anniversary Edition promises to be the most complete total conversion ever made for Strike Fighters 2 by ThirdWire.
      Fly with more than 50 aircraft ranging from Cold War relics to the most advanced platforms. Gain air superiority in the mighty F-15C Eagle or challenge the Coalition with the agile Fulcrum. Support troops with the A-10A Thunderbolt II, bomb strategic targets with the stealthy F-117A Nighthawk, lead airfield denial operations in the iconic Tornado.
      Enjoy a beautifully rendered scenario on a scaled and accurate terrain. Fly over the lakes and rivers of Mesopotamia, the oil-rich fields of Kuwait, the mountains of Iran and Turkey. Take-off from aircraft carriers stationed in the Persian Gulf to watch over Kuwaiti oil rigs. Perform landings and patrols in more than 90 airports and air bases in the Middle East.
      Take part in different campaigns including the Iraqi blitzkrieg on Kuwait and the US-led liberation of the Kuwaiti Emirate. Discover how the Iraqi Army was one of the biggest in the world, through the eyes of American, British, Canadian, French, Italian and Arab pilots. Test your skills and abilities flying for the Iraqi Air Force during all stages of the conflict.
      Thirty years after, Operation Desert Storm still remains the largest air operation of modern warfare to date. Modders and flight sim enthusiasts at CombatACE teamed up to bring you a unique product in the lite flight sim world. Exquisitely detailed aircraft and paint schemes are delivered in a well-researched and thorough order of battle.
      The ODS 30th AE Development team would like to thank CombatACE.com, its admins, moderators and contributors.
      We are sure you will enjoy and appreciate this high-quality freeware product. From the aviation enthusiasts, to the aviation enthusiasts... and for the pilots of tomorrow.
       
      Minimum Requirements
      Required products from ThirdWire:
      Strike Fighters 2, July 2013 patch Strike Fighters 2: Israel, July 2013 patch Strike Fighters 2: North Atlantic, July 2013 patch Full support for:
      Mission Editor DLC Campaign Customizer DLC System specs:
      OS: Windows 7 x86 Processor: Dual Core 2.7 GHz Memory: 4.0 GB RAM Hard Drive: 17.0 GB Free Space Video Card: 1024 MB DirectX 10  
      Sneak Peek
       
      Disclaimer
      CombatACE.com shall at all times retain ownership of the Software as originally downloaded by you and all subsequent downloads of the Software by you. The Software (and the copyright, and other intellectual property rights of whatever nature in the Software, including any modifications made thereto) are and shall remain the property of CombatACE.com and of the respective developers/modders.
      In no event, unless required by applicable law or agreed to in writing, shall CombatACE.com, or any person be liable for any loss, expense or damage, of any type or nature arising out of the use of, or inability to use this installer or program, including, but not limited to, claims, suits or causes of action involving alleged infringement of copyrights, patents, trademarks, trade secrets, or unfair competition.
      The Operation Desert Storm: 30th Anniversary Edition modification does NOT comply with CombatACE's Freeware Licensing. Various contents of this modification are exclusive, as such you are NOT allowed to share, redistribute and/or make use of the mod and/or its contents for other purposes, without the consent of the mod's developers. Contents of the modification are the copyright of their respective authors.
       
      Notes about the installer
      Beware, the mod is available only in the ISO format. You can either mount it on a virtual drive, burn it on a DVD like in the good old days, or unzip it with 7-Zip or equivalent software.
      The installer will automatically detect your installation of the required Strike Fighters 2 games by reading through the registry keys. Game folders that are copied from or manually moved from where they were originally installed are not supported. You need all three aforementioned Strike Fighters 2 games and they must be installed with ThirdWire's original installers, not manually copied from other sources nor moved elsewhere after installation to other folders or drives. If you do not meet any of these requirements, installation cannot proceed and you are on your own. If you install all required games properly, the installation of the mod will proceed correctly as intended. The installer then lets you choose where to install the mod folder; you can even install the mod on a different drive or partition than the one where Strike Fighters 2 is installed. No further user input nor manual edits after installation are ever required; the installer takes care of creating all proper links to your desired path for the mod folder. After installation is over, simply run the mod by using the created Desktop and/or Start Menu links.
      If you have a previous version of the mod installed, please use the uninstaller to remove it completely. Clean installation is mandatory. You might want to make a backup of the Controls folder, so that you can easily restore your controller settings afterwards.
       
      Suggestions on common issues
      Make sure that you are using your dedicated GPU. By default, Strike Fighters 2 usually selects the integrated GPU you may have on your CPU, which is much weaker in terms of VRAM. In case you have frequent crashes or black/missing textures, I highly suggest you download and install the DXVK graphics wrapper (x86 DLLs) into your Strike Fighters 2 game folder: https://github.com/doitsujin/dxvk. You need a Vulkan-compatible GPU. The wrapper can greatly improve the experience with the mod. With DXVK I can play the mod on a mere Intel UHD 710, whereas without it the mod would always crash to desktop. Go to Sound and set Sound Channels to 32. We got reports that 16 is not enough and will cause crashes on some systems, due to the higher quality sounds included within the mod. The mod is pretty heavy for the game engine despite huge optimizations. Strike Fighters 2's engine is 32bit only and apparently does not manage VRAM properly; consecutive campaign missions might show black/missing textures on objects or cause crashes to desktop because the game does not release the occupied VRAM from the previous mission you played, thus the more missions are loaded consecutively, the more easily you may run out of memory. Set Ground Objects to Medium or Low, Horizon Distance to Near, and Shadows to Medium or Low. These are the most troubling settings. Avoid Unlimited settings as much as possible. If the mod used to work and suddenly crashes to desktop, updating or reinstalling video drivers should help. Make sure that DirectX June 2010 Redistributables are also installed, they are included inside the ISO disk image of the mod. Inside the mod folder, you'll find some extra text files. "(Coalition Order of Battle)" should be of your interest; the mod's terrain covers the entirety of Iraq, at the cost of not having all of Saudi Arabia; this means that a number of important units are based on airbases that are beyond the in-game playable area. With those units you always spawn near the target area, you'll never get to start from a runway nor to land on the assigned runway beyond the invisible wall. You have an entire list of the affected units in the aforementioned text file. By pressing ALT+N, the plane returns to base automatically. The mod is fully compatible with the Campaign Customizer and Mission Editor DLCs by ThirdWire. The Campaign Customizer might be an alternative way to experience those off map units I mentioned previously, since it assigns you to a random airbase of the in-game flyable area. Escort missions are often broken, this is not an issue of the mod, but a bug of the stock game; sometimes the AI flight you escort does not engage its target and keeps flying in a straight line instead of following waypoints, thus the trigger for mission success will never happen. Abandon the mission or retry it if the issue happens, sometimes it works. Pray for ThirdWire AKA Tsuyoshi Kawahito to work on a 64bit version of Strike Fighters 2, maybe even with support for DirectX 12. With that done, any out of memory issues should become an old memory. Submitter Menrva Submitted 01/16/2021 Category User Made Campaigns  
    • By Spinners


      View File [Fictional] McDonnell Douglas Phantom F-4L (USMC)
      McDonnell Douglas F-4L (USMC/USN) Phantom for STRIKE FIGHTERS 2
      This is a simple mod of the stock Third Wire F-4M_75 to give a fictional USMC Phantom F-4L with markings for VMFA-333 'Shamrocks'. Also included is a USN VF-111 scheme that generally uses stock decals but is included here to give a blank F-4L tail for you to do other squadrons by using stock decals. It goes without saying that you will need to have the F-4M_75 from SF2:Europe.

      BACKSTORY
      With all the considerable design effort being put into the marriage of the Phantom airframe and the Rolls-Royce Spey turbofan engine McDonnell Douglas thought it might be a good idea to propose a version to the US Navy to allow the Phantom to operate from the smaller carriers that were limited to F-8E Crusaders. In June 1966 the designation F-4L was given to the proposed Spey-powered Phantom and in October 1966 an initial order for 130 F-4L's (USN/USMC) was made, followed by an unexpected export order of 30 F-4L's for the Royal Australian Navy.
      Deliveries to the US Navy commenced in February 1969 with VF-24 becoming the first operational squadron followed by VMFA-333. By this time the wisdom of operating such a relatively large aircraft on the older, smaller carriers was being questioned and most F-4L's served aboard the larger carriers or with land-based units. 
      When the decision was made not to re-equip the USMC 'fighter-attack' Phantom squadrons with the hugely expensive Grumman F-14A Tomcat, McDonnell Douglas pushed hard for low-rate production of the F-4L to continue specifically for USMC use and they were eventually successful meaning that production continued until 1976 with an eventual total of 306 F-4L's being built. Apart from Australia, F-4L's also served with the Royal Air Force where 15 ex-USN F-4L's were sold to the UK Government to allow the formation of an additional home-based Phantom squadron to release a squadron for the defence of the Falkand Isles. 

      INSTRUCTIONS
      1. From the AIRCRAFT folder drag and drop the F-4L_75 folder into your Aircraft folder.
      2. From the DECALS folder drag and drop the F-4L_75 folder into your Decals folder.
      That's it!

      CREDITS
      As always, thanks to Third Wire for a great little game/sim.
      And, finally, thanks to everyone in the wider Third Wire community.
      Regards 
      Spinners
      Version 2 - February 17th, 2024.
       
      Submitter Spinners Submitted 01/24/2010 Category What If Hangar  
    • By Spinners
      McDonnell Douglas F-4L (USMC/USN) Phantom for STRIKE FIGHTERS 2
      This is a simple mod of the stock Third Wire F-4M_75 to give a fictional USMC Phantom F-4L with markings for VMFA-333 'Shamrocks'. Also included is a USN VF-111 scheme that generally uses stock decals but is included here to give a blank F-4L tail for you to do other squadrons by using stock decals. It goes without saying that you will need to have the F-4M_75 from SF2:Europe.

      BACKSTORY
      With all the considerable design effort being put into the marriage of the Phantom airframe and the Rolls-Royce Spey turbofan engine McDonnell Douglas thought it might be a good idea to propose a version to the US Navy to allow the Phantom to operate from the smaller carriers that were limited to F-8E Crusaders. In June 1966 the designation F-4L was given to the proposed Spey-powered Phantom and in October 1966 an initial order for 130 F-4L's (USN/USMC) was made, followed by an unexpected export order of 30 F-4L's for the Royal Australian Navy.
      Deliveries to the US Navy commenced in February 1969 with VF-24 becoming the first operational squadron followed by VMFA-333. By this time the wisdom of operating such a relatively large aircraft on the older, smaller carriers was being questioned and most F-4L's served aboard the larger carriers or with land-based units. 
      When the decision was made not to re-equip the USMC 'fighter-attack' Phantom squadrons with the hugely expensive Grumman F-14A Tomcat, McDonnell Douglas pushed hard for low-rate production of the F-4L to continue specifically for USMC use and they were eventually successful meaning that production continued until 1976 with an eventual total of 306 F-4L's being built. Apart from Australia, F-4L's also served with the Royal Air Force where 15 ex-USN F-4L's were sold to the UK Government to allow the formation of an additional home-based Phantom squadron to release a squadron for the defence of the Falkand Isles. 

      INSTRUCTIONS
      1. From the AIRCRAFT folder drag and drop the F-4L_75 folder into your Aircraft folder.
      2. From the DECALS folder drag and drop the F-4L_75 folder into your Decals folder.
      That's it!

      CREDITS
      As always, thanks to Third Wire for a great little game/sim.
      And, finally, thanks to everyone in the wider Third Wire community.
      Regards 
      Spinners
      Version 2 - February 17th, 2024.
       
    • By ludo.m54


      View File Mirage F1CR standard F5/6
      Mirage F1CR F5/6 standard
      When it became clear that the Mirage F1 was becoming a successful production aircraft, Dassault began investigating the possibility of a dedicated reconnaissance version for its most important client, the French Air Force. However, the escalating cost of fighter aircraft meant that add-on pods for this purpose were a more economical alternative. Many French Air Force aircraft, as well as those of some export clients (such as Iraq's Mirage F1EQ), did indeed have a variety of reconnaissance pods available, which were attached to the underside of the main fuselage. However, the development of a tactical reconnaissance aircraft for the French Air Force continued, and the first Mirage F1CR flew on 20 November 1981.
      F1CR F5/F6 standard specifics:
      Corail gondolas (P0 station)
      RWR BF double wingtip position lights Thomson CSF RAPHAEL TH SLAR Side Looking Aiborne Radar Recon Pod (P1 Id on AMCP) ASTAC (Analyseur de Signaux TACtiques) ELINT pod (P3 Id on AMCP This addon is and will in all cases remain freeware.
      Released under CombatAce Fair-Use terms.
      Enjoy
      The Mirage F-1 Team
      Submitter ludo.m54 Submitted 02/11/2024 Category Mirage F1  
    • By ludo.m54
      Mirage F1CR F5/6 standard
      When it became clear that the Mirage F1 was becoming a successful production aircraft, Dassault began investigating the possibility of a dedicated reconnaissance version for its most important client, the French Air Force. However, the escalating cost of fighter aircraft meant that add-on pods for this purpose were a more economical alternative. Many French Air Force aircraft, as well as those of some export clients (such as Iraq's Mirage F1EQ), did indeed have a variety of reconnaissance pods available, which were attached to the underside of the main fuselage. However, the development of a tactical reconnaissance aircraft for the French Air Force continued, and the first Mirage F1CR flew on 20 November 1981.
      F1CR F5/F6 standard specifics:
      Corail gondolas (P0 station)
      RWR BF double wingtip position lights Thomson CSF RAPHAEL TH SLAR Side Looking Aiborne Radar Recon Pod (P1 Id on AMCP) ASTAC (Analyseur de Signaux TACtiques) ELINT pod (P3 Id on AMCP This addon is and will in all cases remain freeware.
      Released under CombatAce Fair-Use terms.
      Enjoy
      The Mirage F-1 Team
×

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..