Search the Community
Showing results for tags 'vfc-13'.
Found 3 results
-
Due to personal reasons, after a long hiatus of a year I decided to get back into video editing. Eagerly awaiting two things: GFX card prices to come down and the F-14. I hope you all enjoy, this has been a long and painful year..
-
Su-27 Fictional Skins: US Navy Volume III - Adversaries
HomeFries posted a topic in Digital Combat Simulator Series File Announcements
View File Su-27 Fictional Skins: US Navy Volume III - Adversaries This is a collection of 13 skins of the Su-27 Flanker in US Navy and Marine Corps Adversary paint schemes. Commands represented are: VFC-12 Fighting Omars VFC-13 Saints VMFT-401 Snipers Naval Strike Air Warfare Center (NSAWC, parent command of TOPGUN) The pack includes various combinations of camouflage and splinter patterns in air superiority blue, desert, arctic, woodland and one Su-34 fullback paint scheme based on a 2016 VFC-12 endeavor. Most markings have been westernized, and the pilots have been given USN/USMC flightsuits with Naval Aviator wings and squadron patches. The helmet remains Russian made. Be sure to download Volumes I and II: Volume I Volume II 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 Submitter HomeFries Submitted 01/21/2017 Category Su-27 Skins -
Version 1.12
50 downloads
This is a collection of 13 skins of the Su-27 Flanker in US Navy and Marine Corps Adversary paint schemes. Commands represented are: VFC-12 Fighting Omars VFC-13 Saints VMFT-401 Snipers Naval Strike Air Warfare Center (NSAWC, parent command of TOPGUN) The pack includes various combinations of camouflage and splinter patterns in air superiority blue, desert, arctic, woodland and one Su-34 fullback paint scheme based on a 2016 VFC-12 endeavor. Most markings have been westernized, and the pilots have been given USN/USMC flightsuits with Naval Aviator wings and squadron patches. The helmet remains Russian made. Be sure to download Volumes I and II: Volume I Volume II 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
