Jump to content

Search the Community

Showing results for tags 'dcs'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • CombatACE General Forums
    • The Pub
    • CombatACE News
    • Military and General Aviation
    • Digital Recon
    • Virtual Squadron Chat
    • Site Support / Bug Reports / Suggestions
  • Editorial Reviews and Interviews
    • Hardware Reviews
    • Game Reviews
    • Interviews
    • Mission Reports
  • Modding and Developer Forums
    • Razbam
    • Mod Mafia
    • CAF Development
  • Eagle Dynamics Digital Combat Simulator Series
    • Digital Combat Simulator News
    • Digital Combat Simulator Series File Announcements
    • Digital Combat Simulator Series General Discussion
    • Digital Combat Simulator Series Modding/Skinning Chat
    • Digital Combat Simulator Series Mission/Campaign Building
  • Thirdwire: Strike Fighters 2 Series
    • Thirdwire: Strike Fighters Series News
    • Thirdwire: Strike Fighters 2 Series - File Announcements
    • Thirdwire: Strike Fighters 2 Series - Knowledge Base
    • Thirdwire: Strike Fighters 2 Series - General Discussion
    • Thirdwire: Strike Fighters 2 Series - Screen Shots
    • Thirdwire: Strike Fighters 2 Series - Mods & Skinning Discussion
    • Thirdwire: Strike Fighters 2 Series - Mission & Campaign Building Discussion
    • Thirdwire: Strike Fighters 2 Series - Sci-Fi/Anime/What If Forum
    • Thirdwire: Strike Fighters 2 Series - World War II Forum
  • Thirdwire: Strike Fighters 1 Series
    • Thirdwire: Strike Fighters 1 Series - File Announcements
    • Thirdwire: Strike Fighters - Knowledge Base
    • Thirdwire: Strike Fighters 1 Series - General Discussion
    • Thirdwire: Strike Fighters 1 Series - Mods/Skinning Discussion
    • Thirdwire: Strike Fighters 1 Series - Mission/Campaign Building Discussion
    • Thirdwire: Strike Fighters 1 Series - Sci-Fi/Anime/What If Forum
    • Thirdwire: Strike Fighters 1 Series - Prop Heads Forum
  • Over Flanders Fields
    • OFF / WOFF 1 2 3 / UE - General Discussion
    • OFF / WOFF 1 2 3 / UE - Knowledge Base
    • OFF / WOFF 1 2 3 / UE - File Announcements
    • OFF - Retired Threads
  • WW1 Flight Simulation
    • WWI Flight Sim Discussion
    • Thirdwire - First Eagles 1&2
    • Rise of Flight
  • IL-2 Series / Pacific Fighters / Cliffs of Dover
    • IL-2 Series / Pacific Fighters / Cliffs of Dover: News
    • IL-2 Series / Pacific Fighters / Cliffs of Dover: File Announcements
    • IL-2 Series / Pacific Fighters / Cliffs of Dover: General Discussion
    • IL-2 Series / Pacific Fighters / Cliffs of Dover: Mods & Skinning Chat
    • IL-2 Series / Pacific Fighters / Cliffs of Dover: Mission & Campaign Building
  • Canvas Knights WW1 Game
    • Canvas Knights WW1 Game - Official News Releases
    • Canvas Knights WW1 Game - General Discussions
    • Canvas Knights WW1 Game - Works In Progress (WIP)
    • Canvas Knights WW1 Game - Other Mods
    • Canvas Knights WW1 Game - Videos and Screenshots
    • Canvas Knights WW1 Game - File Announcements
  • EAW - European Air War
    • EAW - File Announcements
    • EAW - General Discussions
    • EAW - Support and Help
    • EAW - Skinning, Modding, Add-ons
    • EAW - Online Multiplay
    • EAW - Knowledge Base
  • Flight Simulation
    • General Flight Sim News
    • General Flight Sim Discussion
    • Microsoft Flight Simulator
    • Jet Thunder
    • Falcon 4 Series
    • Combat Pilot Series
  • Helo Simulation
    • The Hover Pad
  • World Language Forums
    • Español
    • Português
    • Deutsch
    • Polski
    • עִבְרִית
    • Italiano
    • 한국어
    • 中文 (正、简)
    • 日本語
    • Русский
    • Français
    • Česky
  • West Coast ATC / PROPS Racing
    • West Coast ATC General Topics
    • PROPS Racing General Topics
  • Racing Sims
    • Racing Simulations General Discussions
  • Tactical Sims/FPS
    • The Bunker
    • Americas Army
    • Armed Assault Series
    • Call of Duty
    • BattleField
  • Naval Simulation
    • Naval Combat Information Center
    • Killerfish Games - Cold Waters, Atlantic & Pacific Fleet
    • Silent Hunter Series
    • Dangerous Waters
  • Space Simulations
    • Sci-Fi Simulations
    • Star Trek Legacy
    • Star Wars
    • Battlestar Galactica
  • Hardware/Tech/Gadgets
    • Hardware/Software Chat
    • Game Controllers
    • Case Modding
  • Odds & Ends
    • Strategy Simulations
    • Game Console Corner
    • Buy/Sell/Trade Corner

Calendars

  • Community Calendar

Categories

  • Strike Fighters by Thirdwire
    • Strike Fighters 1 Series by Thirdwire
    • Strike Fighters 2 Series by Thirdwire
  • First Eagles by Thirdwire
    • First Eagles - General Files
    • First Eagles - WWI and Early Years 1914 - 1920
    • First Eagles - Golden Era 1920 to 1940
  • OFF/WOFF - Over Flanders Fields by OBD Software
    • Aircraft Skins
    • Aircraft Models
    • Scenery and Ground Objects
    • Maps, Missions, and Campaigns
    • Modding Tools and Add-on Software
    • OFFice / OFFbase / OFFworld
  • Digital Combat Simulator Series
    • DCS Aircraft Skins
    • DCS Aircraft Mods
    • DCS Singleplayer Missions
    • DCS Multiplayer Missions
    • DCS Campaigns
    • DCS Object Mods
    • DCS Sound Mods
    • DCS Tracks / Videos / Tutorials
    • DCS Utilities
    • DCS Joystick Config Files
    • DCS Misc. Files
    • DCS Patches
  • Canvas Knights WW1
    • Main Game Files and Updates
    • Aircraft
    • Aircraft Skins
    • Ground and Sea Vehicles
    • Scenery, Maps, and Objects
    • Missions
    • Miscellaneous
    • Mods
    • Tools
  • EAW - Europen Air War
  • IL2: Forgotten Battles / Pacific Fighters by Ubisoft
    • IL2 Series Aircraft Skins
    • IL2 Series Campaigns & Missions
    • IL2 Series Game Mods
    • IL2 Series Utilities/ Editors
  • Rise Of Flight
    • ROF - Aircraft Skins
    • ROF - Missions and Campaigns
    • ROF - Miscellaneous Files
  • FALCON 4.0: Allied Force by MicroProse
  • Flight Simulator by Microsoft & PROPS Racing Files
    • FSX by Microsoft
    • FS9 and Pre-FS9 by Microsoft
    • PROPS Racing Files
  • Racing Simulations
    • rFactor
    • GTR/GTR2
  • Sci-Fi Simulations
    • Star Trek Legacy
    • Star Wars Games
    • Misc - Other
  • First Person Simulations
    • Armed Assault
    • America's Army
  • Naval Simulations
    • Cold Waters
    • Silent Hunter Series
    • Dangerous Waters

Group


AIM


MSN


ICQ


Yahoo


Jabber


Skype


Location


Interests


Website


Twitter


Facebook

Found 113 results

  1. All things must come to an end so I present you my closing videos for the DCS video series I started over a year ago titled Eleven. The close is a three part video, with the first video titled : The Mighty Eagle The second video consists of the credits and a thanks to all of you for your advice, support, and critiques of my video edits. Finally, the last video is a tribute to the American Airman, particularly my father who served the United States during the Cold War period once in military uniform then again as a law enforcement officer. Perhaps the creative bug may bite me again and I may start a new project, but until then this is it! Hope all of combatace's service men and women from all the world's nations had a wonderful Veterans/Armistice day.
  2. Two seat Jet trainer aircraft L-39C is intended for basic and advanced pilot training in visual and instrument flight rules weather conditions, day and night and also for combat use against air and ground targets. Its development started in the middle 60s of the last century by the Czech “Aero Vodochody”. In the 70s the aircraft has entered service and is still in the operational use in over 30 countries worldwide. The DCS L-39C is the most accurate computer simulation of this aircraft among flight simulators available for PC. The aircraft systems, engine and weapons have been simulated in full. The professional flight model has been developed. All the real procedures are possible in two interactive cockpits. Highly detailed and accurate model of the aircraft will make you feel the unforgettable sense of flying the famous “flying school desk”, which opened the way to the sky to thousands of air forces pilots worldwide. Key Features of the DCS: L-39 Albatros: Professional Flight Model that accurately mimics the performance and flight characteristics of this legendary trainer Highly detailed, six-degrees-of-freedom (6 DOF) cockpit Interact with cockpit controls with your mouse Fully modelled weapon system Accurate L-39C model with correct country markings Detailed modelling of the L-39 instruments, weapons, engine, radios, fuel, electrical and hydraulic systems Fly from either the front seat or back seat Planned cooperative multiplayer in the same aircraft (not available at release) Two versions of aircraft: L-39C that will be available in the initial beta and L-39ZA that will be later http://www.digitalcombatsimulator.com/en/shop/modules/albatros/
  3. The 75th Virtual Fighter Squadron is a A-10C and UH-1N Huey group looking to recruit individuals to have fun and improve their skills at the same time. The core group consists of enthusiasts that have been flying sims for decades (yes we're old), and want to share time with like minded individuals to grow and have a load of good times with. We fly Wednesday and Friday nights at 7pm MST (CAN & US). If you think you will be a good fit, please come see our website for more information at the below link: 75th VFS Tiger Sharks
  4. http://www.digitalcombatsimulator.com/en/products/nttr_terrain/ The Fighter Collection with Eagle Dynamics are happy to announce that DCS: NEVADA Test and Training Range Map is available for pre-purchase from the DCS e-shop DCS: NEVADA Test and Training Range Map will sell for $49.99 in November 2015. Pre-purchase now for $39.99 and save 20%! The Nevada Test and Training Range (NTTR) has the largest contiguous air and ground space available for peacetime military operations in the free world. The NTTR land area includes simulated air defense systems, mock airbases, and several target ranges. The NTTR was also used for nuclear testing. Today, it is home to RED FLAG and other military exercises that include countries from around the world. The NTTR map for DCS World 2 includes Nellis AFB, Creech AFB and the infamous Groom Lake AFB (aka Area 51). This map also includes the city of Las Vegas, McCarran International Airport, and Hoover Dam. Key Features of DCS: NEVADA Test and Training Range Map: 366,000 sq. kilometres that covers portions of Nevada, Utah, Arizona and California. Highly detailed modelling of Nellis Air Force Base, Creech Air Force Base, McCarran International Airport, and the Area 51 facility. Hoover Dam and Lake Meade. All VOR and VORTAC radio navigation beacons. High resolution mesh and textures around the detailed airbases. The entire NTTR airspace as well indication of all sub-ranges. Las Vegas, Pahrump, Mesquite, Moapa, Indian Springs, Boulder City and other cities and towns in and nearby the NTTR. This also includes all major roads, railways, and power lines. For those that pre-purchase prior to October 1st, 2015, you will receive a 20% discount and two free Red Flag campaigns (one for the F-15C and one for the A-10C). For those that pre-purchase between October 1st and the Open Alpha release in late November, you will receive a 20% discount and one free Red Flag campaign. Both of these options also include a 20% bonus savings on future purchases at full price. Note: Customers that purchased DCS: A-10C Warthog while it was in beta (prior to February 21st, 2011) will be provided this map for free! https://www.youtube.com/watch?t=48&v=10h71xyU6C4 http://forums.eagle.ru/showpost.php?p=2470752&postcount=2
  5. The summer heat is here and so are the DCS savings! Take advantage of this mid-summer FLASH sale that runs from 15:00 (UTC time) Friday, July 31st to 05:00 (UTC time) Monday, August 3rd. Fill out your DCS World library before the big move to DCS World 1.5 in September 2015. This FLASH sale is for USD prices only and does not apply to former Soviet Union countries. http://www.digitalcombatsimulator.com/en/shop/ DCS: Flaming Cliffs 3: $39.99 to $11.99 (70% off) DCS: A-10C Warthog: $39.99 to $11.99 (70% off) DCS: Black Shark 2: $39.99 to $11.99 (70% off) DCS: P-51D Mustang: $29.99 to $8.99 (70% off) DCS: Fw 190 D-9 Dora: $49.99 to $14.99 (70% off) DCS: Bf 109 K-4 Kurfürst: $49.99 to $14.99 (70% off) DCS: Combined Arms: $19.99 to $5.99 (70% off) F-15C for DCS World: $9.99 to $2.99 (70% off) Su-27 for DCS World: $9.99 to $2.99 (70% off) Su-27 The Ultimate Argument Campaign: $9.99 to $2.99 (70% off) A-10A for DCS World: $9.99 to $2.99 (70% off) Su-25 for DCS World: $9.99 to $2.99 (70% off) DCS: MiG-15bis: $49.99 to $14.99 (70% off) DCS: F-86F Sabre: $49.99 to $14.99 (70% off) DCS: UH-1H Huey: $49.99 to $14.99 (70% off) DCS: Mi-8MTV2 Magnificent Eight: 49.99 to $14.99 (70% off) DCS: C-101 Aviojet: $59.99 to $17.99 (70% off) DCS: MiG-21bis: $49.99 to 19.99 (60% off)
  6. File Name: A-10 Ferris Splinter [Fictional] File Submitter: EricJ File Submitted: 18 July 2015 File Category: A-10A/C Skins A-10 Ferris Splinter [Fictional] This is a basic Splinter scheme based on an F-15C design modified for the A-10 airframe, and also some artistic liberties as well. While the A-10C is shown, this can also be used on the A-10A, simply copy and paste the folder into the Bazar\Liveries\A-10A or A-10C and select “Ferris Splinter No.1” in the Payload Menu and go fly. Click here to download this file
  7. Version

    18 downloads

    A-10 Ferris Splinter [Fictional] This is a basic Splinter scheme based on an F-15C design modified for the A-10 airframe, and also some artistic liberties as well. While the A-10C is shown, this can also be used on the A-10A, simply copy and paste the folder into the Bazar\Liveries\A-10A or A-10C and select “Ferris Splinter No.1” in the Payload Menu and go fly.
  8. For Sale: DCS Modules

    Never installed nor activated for lack of time, paypal please: DCS: UH-1H Huey by Belsimtek (download version): $25 USD DCS: Flaming Cliffs 3 (download version): $20 USD
  9. File Name: FJ-3M VF-211 Red Checkertails Skin for DCS F-86F File Submitter: HomeFries File Submitted: 30 June 2015 File Category: Misc/AI Aircraft Skins This is part of a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable). Fighter Squadron 211 (the Red Checkertails which were later redesignated the VF-24 Renegades, not to be confused with the VF-211 Checkmates designated in 1959) flew the FJ-3M Fury from 1956-1957 before transitioning to the F8U-1 Crusader. This skin pack features skins from the 1956-57 deployment aboard the USS Bon Homme Richard (CVA-31) as part of Carrier Air Group 21 (CVG-21, Tailcode G). 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. If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders. Be sure to update any missions that used 1.x series skins. 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. Updating from the 1.x series of FJ-3 Skins: With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek. As such, organizational specific modex placement as well as modex placement on the wing is no longer possible. The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection. For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail). Detail placement in textures based on USN skins by Crazyeddie. Special thanks to SkateZilla for the awesome Photoshop template. 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 Click here to download this file
  10. File Name: FJ-3 VF-191 Satan's Kittens Skin for DCS F-86F File Submitter: HomeFries File Submitted: 30 June 2015 File Category: Misc/AI Aircraft Skins This is part of a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable). Fighter Squadron 191 flew the FJ-3 Fury from 1956-1957 before transitioning to the F11F-1 Tiger. This skin pack features skins from the 1957 deployment aboard the USS Yorktown (CVA-10) as part of Carrier Air Group 19 (CVG-19, Tailcode B). 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. If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders. Be sure to update any missions that used 1.x series skins. 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. Updating from the 1.x series of FJ-3 Skins: With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek. As such, organizational specific modex placement as well as modex placement on the wing is no longer possible. The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection. For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail). Detail placement in textures based on USN skins by Crazyeddie. Special thanks to SkateZilla for the awesome Photoshop template. 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 Click here to download this file
  11. File Name: FJ-3M VF-142 Fighting Falcons Skin Pack for DCS F-86F File Submitter: HomeFries File Submitted: 30 June 2015 File Category: Misc/AI Aircraft Skins This is the first in a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable). The idea of this series is to have a single skin for each squadron, and separate decals for each side number (Modex). The last 4 digits of the serial number (BuNo) use the USAF serial number to allow for dynamic BuNos, though the side number must be selected by choosing the skin itself. This will allow a common Modex pool and a single texture for each squadron, thereby allowing you to employ an entire squadron in a mission while keeping the hard drive and in-mission RAM footprint to a minimum. Fighter Squadron 142 (the Fighting Falcons, not to be confused with the VF-142 Ghostriders that was designated in 1963) flew the FJ-3M Fury for a short time (1956-1958), including a deployment on the USS Hornet (CVA-12) as part of Carrier Air Group 14 (CVG-14) before returning to NAS Miramar and transitioning to the F8L1-1 Crusader. This skin pack features skins from the 1957 Hornet deployment (CVG-14 Tailcode A) and the return to Miramar (1958) prior to transitioning to the Crusader. The 1958 skin displays the CVG-14 Tailcode NK, which replaced A once the US Navy went to 2 letter tailcodes. 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. If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders. Be sure to update any missions that used 1.x series skins. 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. Updating from the 1.x series of FJ-3 Skins: With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek. As such, organizational specific modex placement as well as modex placement on the wing is no longer possible. The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection. For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail). Detail placement in textures based on USN skins by Crazyeddie. Special thanks to SkateZilla for the awesome Photoshop template. 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 Click here to download this file
  12. File Name: FJ-3M VF-121 Pacemakers Skin for DCS F-86F File Submitter: HomeFries File Submitted: 30 June 2015 File Category: Misc/AI Aircraft Skins This is part of a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable). Fighter Squadron 121 flew the FJ-3M Fury operationally in 1957 before being redesignated as a Replacement Air Group (RAG). Of note, it was VF-121's status as a F-4 Phantom RAG at NAS Miramar that helped provide the squadron's reknown as the original host unit for the US Navy Fighter Weapons School ("Top Gun"). This skin pack features skins from the 1957 deployment aboard the USS Lexington (CV-16) as part of Carrier Air Group 12 (CVG-12, Tailcode D). 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. If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders. Be sure to update any missions that used 1.x series skins. 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. Updating from the 1.x series of FJ-3 Skins: With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek. As such, organizational specific modex placement as well as modex placement on the wing is no longer possible. The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection. For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail). Detail placement in textures based on USN skins by Crazyeddie. Special thanks to SkateZilla for the awesome Photoshop template. 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 Click here to download this file
  13. File Name: FJ-3 VF-73 Jesters Skin Pack for DCS F-86F File Submitter: HomeFries File Submitted: 30 June 2015 File Category: Misc/AI Aircraft Skins This is part of a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable). Fighter Squadron 73 flew the FJ-3 Fury from 1956 until its decommissioning in 1958. Originally part of Carrier Air Group 7 (CVG-7, Tailcode L), VF-73 was transferred to CVG-4 (Tailcode AD) for its 1957 deployment on the USS Randolph (CVA-15). This skin pack features skins from CVG-7 and the 1957 Randolph deployment with CVG-4. 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. If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders. Be sure to update any missions that used 1.x series skins. 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. Updating from the 1.x series of FJ-3 Skins: With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek. As such, organizational specific modex placement as well as modex placement on the wing is no longer possible. The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection. For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail). Detail placement in textures based on USN skins by Crazyeddie. Special thanks to SkateZilla for the awesome Photoshop template. 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 Click here to download this file
  14. Version 2.0

    13 downloads

    This is part of a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable). Fighter Squadron 211 (the Red Checkertails which were later redesignated the VF-24 Renegades, not to be confused with the VF-211 Checkmates designated in 1959) flew the FJ-3M Fury from 1956-1957 before transitioning to the F8U-1 Crusader. This skin pack features skins from the 1956-57 deployment aboard the USS Bon Homme Richard (CVA-31) as part of Carrier Air Group 21 (CVG-21, Tailcode G). 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. If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders. Be sure to update any missions that used 1.x series skins. 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. Updating from the 1.x series of FJ-3 Skins: With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek. As such, organizational specific modex placement as well as modex placement on the wing is no longer possible. The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection. For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail). Detail placement in textures based on USN skins by Crazyeddie. Special thanks to SkateZilla for the awesome Photoshop template. 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
  15. Version 2.0

    7 downloads

    This is part of a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable). Fighter Squadron 191 flew the FJ-3 Fury from 1956-1957 before transitioning to the F11F-1 Tiger. This skin pack features skins from the 1957 deployment aboard the USS Yorktown (CVA-10) as part of Carrier Air Group 19 (CVG-19, Tailcode B). 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. If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders. Be sure to update any missions that used 1.x series skins. 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. Updating from the 1.x series of FJ-3 Skins: With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek. As such, organizational specific modex placement as well as modex placement on the wing is no longer possible. The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection. For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail). Detail placement in textures based on USN skins by Crazyeddie. Special thanks to SkateZilla for the awesome Photoshop template. 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
  16. Version 2.0

    6 downloads

    This is the first in a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable). The idea of this series is to have a single skin for each squadron, and separate decals for each side number (Modex). The last 4 digits of the serial number (BuNo) use the USAF serial number to allow for dynamic BuNos, though the side number must be selected by choosing the skin itself. This will allow a common Modex pool and a single texture for each squadron, thereby allowing you to employ an entire squadron in a mission while keeping the hard drive and in-mission RAM footprint to a minimum. Fighter Squadron 142 (the Fighting Falcons, not to be confused with the VF-142 Ghostriders that was designated in 1963) flew the FJ-3M Fury for a short time (1956-1958), including a deployment on the USS Hornet (CVA-12) as part of Carrier Air Group 14 (CVG-14) before returning to NAS Miramar and transitioning to the F8L1-1 Crusader. This skin pack features skins from the 1957 Hornet deployment (CVG-14 Tailcode A) and the return to Miramar (1958) prior to transitioning to the Crusader. The 1958 skin displays the CVG-14 Tailcode NK, which replaced A once the US Navy went to 2 letter tailcodes. 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. If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders. Be sure to update any missions that used 1.x series skins. 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. Updating from the 1.x series of FJ-3 Skins: With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek. As such, organizational specific modex placement as well as modex placement on the wing is no longer possible. The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection. For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail). Detail placement in textures based on USN skins by Crazyeddie. Special thanks to SkateZilla for the awesome Photoshop template. 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
  17. Version 2.0

    7 downloads

    This is part of a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable). Fighter Squadron 121 flew the FJ-3M Fury operationally in 1957 before being redesignated as a Replacement Air Group (RAG). Of note, it was VF-121's status as a F-4 Phantom RAG at NAS Miramar that helped provide the squadron's reknown as the original host unit for the US Navy Fighter Weapons School ("Top Gun"). This skin pack features skins from the 1957 deployment aboard the USS Lexington (CV-16) as part of Carrier Air Group 12 (CVG-12, Tailcode D). 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. If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders. Be sure to update any missions that used 1.x series skins. 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. Updating from the 1.x series of FJ-3 Skins: With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek. As such, organizational specific modex placement as well as modex placement on the wing is no longer possible. The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection. For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail). Detail placement in textures based on USN skins by Crazyeddie. Special thanks to SkateZilla for the awesome Photoshop template. 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
  18. Version 2.0

    5 downloads

    This is part of a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable). Fighter Squadron 73 flew the FJ-3 Fury from 1956 until its decommissioning in 1958. Originally part of Carrier Air Group 7 (CVG-7, Tailcode L), VF-73 was transferred to CVG-4 (Tailcode AD) for its 1957 deployment on the USS Randolph (CVA-15). This skin pack features skins from CVG-7 and the 1957 Randolph deployment with CVG-4. 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. If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders. Be sure to update any missions that used 1.x series skins. 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. Updating from the 1.x series of FJ-3 Skins: With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek. As such, organizational specific modex placement as well as modex placement on the wing is no longer possible. The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection. For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail). Detail placement in textures based on USN skins by Crazyeddie. Special thanks to SkateZilla for the awesome Photoshop template. 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
  19. File Name: FJ-3 VF-24 Corsairs Skin for DCS F-86F File Submitter: HomeFries File Submitted: 29 June 2015 File Category: Misc/AI Aircraft Skins This is part of a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable). Fighter Squadron 24 (the Corsairs which were later redesignated the VF-211 Checkmates, not to be confused with the VF-24 Renegades designated in 1959) flew the FJ-3 Fury for a short time (1956-1957) before transitioning to the F3H Demon. This skin pack features skins from the 1956-57 deployment aboard the USS Shangri-La (CVA 38) as part of Carrier Air Group 2 (CVG-2, Tailcode M). 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. If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders. Be sure to update any missions that used 1.x series skins. 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. Updating from the 1.x series of FJ-3 Skins: With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek. As such, organizational specific modex placement as well as modex placement on the wing is no longer possible. The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection. For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail). Detail placement in textures based on USN skins by Crazyeddie. Special thanks to SkateZilla for the awesome Photoshop template. 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 Click here to download this file
  20. Version 2.0

    7 downloads

    This is part of a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable). Fighter Squadron 24 (the Corsairs which were later redesignated the VF-211 Checkmates, not to be confused with the VF-24 Renegades designated in 1959) flew the FJ-3 Fury for a short time (1956-1957) before transitioning to the F3H Demon. This skin pack features skins from the 1956-57 deployment aboard the USS Shangri-La (CVA 38) as part of Carrier Air Group 2 (CVG-2, Tailcode M). 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. If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders. Be sure to update any missions that used 1.x series skins. 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. Updating from the 1.x series of FJ-3 Skins: With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek. As such, organizational specific modex placement as well as modex placement on the wing is no longer possible. The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection. For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail). Detail placement in textures based on USN skins by Crazyeddie. Special thanks to SkateZilla for the awesome Photoshop template. 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
  21. Close Call

    From the album Ironroad

  22. "Su-27 - The Ultimate Argument" Campaign is available! The Fighter Collection and Eagle Dynamics are pleased to announce that first payware DCS campaign: Su-27 - The Ultimate Argument is now available for download via ingame Model Manager and as separate module from the DCS E-Shop “Su-27 - The Ultimate Argument” is the storyline campaign for the Russian Air Force pilot flying the Su-27 aircraft for the Digital Combat Simulator. The campaign is based on a fictional Caucasus conflict scenario, into which border states of the region got involved. Throughout 20 missions you will have to put up intense air combat, to escort and protect your aircraft, combat air patrols, ground strikes, search for enemy in mountains and gorges, fly day and night. Features of the campaign “Su-27 - The Ultimate Argument”: 20 storyline missions for a single player. More than 300 triggers for interactive environment. 126 voice-overs. Briefing’s art with maps. Russian and English localizations. Voice-overs are recorded in Russian. In the English localization the voices are provided with English subtitles. The DCS: Flaming Cliffs 3 or DCS: Su-27 modules are required to be installed and activated into the DCS World for the campaign.
  23. Dear all, Welcome to the very awesome (boring) very first (meagre) issue of the new monthly Leatherneck Simulations updates! It's been a while since the last official LNS update, but don't fret – we've been as busy as ever behind the scenes. Our primary focus over the past few months has been on wrapping up the MiG-21, completing various auxiliary and management tasks, as well as gradually transitioning into our next project(s). We are incredibly excited to venture into the new year and experience all that lies therein. Without a doubt, DCS will be bigger and better than it has ever been before. We couldn't have been as successful as we have been in 2014 without the massive amount of support from everyone. Heartfelt thank you from the entire LNS team go out to all media representatives, streamers or writers who took the time to assess our product, the ever-patient and fantastic community, and the talented individuals at Eagle Dynamics & The Fighter Collection, who have gone above and beyond more frequently than I can count. We can't thank you all enough! As we've come some ways since release of the MiG-21, we are afforded the clarity of a distanced retrospective on what went right and wrong before, during and after release of the MiG-21. After taking an honest look at ourselves and what we should change moving forward, we have made some changes in how Leatherneck operates and produces content. The MiG-21 modules' development and release has been a learning experience in many ways, and we will be applying this new-found knowledge to better ourselves as we develop new and exciting products. One of the items that have been on the back-burner for a while have been the backer rewards. We've simply not had the resources available to design and produce these items in the immediate post-release period. We currently have quotes and suppliers for everything slated for production, but still have some decisions to make as to what we'll actually opt to go for. Some physical rewards will be consolidated into bigger items. This mainly refers to smaller items such as stickers. We hope to provide amicable options for all backers, but more importantly: ship only actually useful and well-crafted items. Quality over quantity, as it were. We hope to order production runs on these items during the course of January, and ship them to all backers as soon as they are delivered (est. February). The DVD jewelcase artwork will be based on the cover you can currently find on the ED E-Store (here) It will of course be expanded to encompass both sides of the case. Many of you opted for higher backer tiers during the crowdfunding campaign of 2012, and you are thus entitled to more than one MiG-21 key. These keys will be merged into the main key database and sent out in January. Apologies for the long delay on getting these out. The MiG-21 is our first product and thus it has without a doubt been a considerable learning experience. Despite our best efforts, a significant amount of flaws were pushed with the release build of the aircraft. We've put in a concentrated effort in order to eradicate these as quickly as possible, and we hope that progress has been palpable for the end-user. Nonetheless, there are a number of both large and small improvements and fixes still pending. Listed below are some of the major additions planned: New & improved sounds, both in interior and exterior views. Based on real MiG-21 samples. Improved Engine RPM Feedback and immersion. Improved radar screen visual representation. Re-Introduction of red cockpit floodlights Performance improvements wherever possible. Major improvements in exterior 3d model accuracy (pylon tilt, wing thickness, gear door shape, front windshield fuselage joint and more) New AAA quality pilot model in the cockpit (toggleable) (in conjunction with previous) Animated and correct post-ejection pilot model & animations Improved artwork & textures for various ordinance (SPS-141, ASO-2, Atomic bombs and more) Default cockpit livery variations. (Green, Finnish, etc.) 10+ New default liveries. (Bulgarian, Polish, Czech, GDR, Cuba, and much more) Re-introduction of tactical numbering We apologize for any inconvenience caused by issues found in the MiG-21, we hope they have not been too detrimental in your enjoyment of the aircraft. Also, a big thank you to all of you who have been diligently submitting helpful bug reports, they are simply priceless. As we move closer to the release of our next module, we plan to significantly expand the size of our internal testing team. We hope to reduce the amount of release-build bugs in any future product launches. In the next few weeks we also hope to resolve some of the silly activation errors occuring and causing issues for some users. This includes options to properly deactivate the module. While we wanted to release the paint kit immediately after release, we quickly realized that this was not quite feasible considering the amount of 3D and 2D changes coming with the updated and improved external 3D Artwork. Thus; we decided to delay the paint kit until the very final version of the external model is released. We know how frustrating it can be to update broken liveries, both as livery creators and end-users, so we'll make sure to try and keep any retroactive art changes to a minimum in the future. The updated external model is slated to arrive with DCS 2.0, so expect the Paint Kit at around the same time. The 10+ additional liveries that were created prior to release will also be made available at this time. Special thanks to Matija Huzjak for a beautiful Croatian Air Force skin that will be included in the package. The fine gentlemen at ThreeAppsStudios Studios (https://play.google.com/store/apps/d...reeAppsStudios) have created a great Android based application to help you fly the MiG-21. You can find it here: https://play.google.com/store/apps/d...sstudios.mig21 We'd like to extend our gratitude to Milan and his team for their perseverance and excellent craftsmanship. Hope to work with you again soon! 2015 will mark a year of considerable growth and expansion for Leatherneck Simulations. This will ensure that we are prepared to meet the ambitious content production goals that we have set forth for ourselves for the next few years. Reinvestment of resources into all facets of our business will allow us to provide you all with better and far more content than before. Since the release of the MiG-21, we have already grown to double our initial size. We'll be introducing you to each of our new members in the coming months. We expect to add yet another 3-4 members to our staff during Q1 of 2015. This, in addition to a new permanent office location in Swinoujscie, Poland. The release and performance of the MiG-21 solidifies our investment into DCS, and we remain genuinely committed to the flight simulation genre. We are here to stay for a long time to come. Currently we have three aircraft in advanced states of development, with a few more in mixed, but primarily earlier stages. We have already hinted heavily at one of the advanced ones, and we'll be showcasing more on all three as we get closer to their respective release dates. You shouldn't expect to have to wait until 2016 to fly a new Leatherneck module. Overall, we are confident that we will be able to cater to almost all of your tastes. Maybe we'll even manage to avoid the pitchforks. Regardless of the aircraft, we will always be trying to push the envelope, both in simulation and visual fidelity. Various planned features will require solving difficult design challenges (related to both gameplay and technical considerations), but we are confident in our ability to overcome these. By applying everything we've learned during the MiG-21's protracted development, we can focus on improving ourselves and building on our existing standards. Some of you have raised concerns about certain features or requirements precluding the development of various aircraft, but we do not currently feel limited by any such considerations. Moving away from aircraft, EDGE now affords us the ability to build new theaters and complement our aircraft with appropriate campaigns and missions. Currently, we have development plans stretching across a wide variety of locales and eras. Maps built by Leatherneck will adhere to the same rigorous standards we place upon our aircraft modules, and will be based on an appropriate fusion of artistic skill and real-world data. We did plan to push a little.. something out today to tease what is to come; but following an untimely missplaced bill, our site is still down, so it will have to wait a little longer. You'll live. I hope? This post turned out to far too long considering the meagre content. Excuse the long-windedness, and expect the next monthly update to be far more image heavy. Once again, thank you all for your unwavering dedication and support. It means the world to us. Stay tuned and expect to hear from us very soon. Sincerely, Leatherneck Simulations N, M, N, R, T, C, A, A __________________ /Nicholas Dackard Artist Leatherneck Simulations EVERYTHING IS SUBJECT TO CHANGE
  24. XI Interlude: Unsung Heroes

    A tribute to all those that work so hard to support the "pointy" end of the spear. **Stay Tuned for XI (Eleven) Part 8, because when the tankers start getting positioned you know it's about to go down.
  25. Anyone here familiar with Window's Movie Maker or Power Director? Forgive me if you feel this may be out of place as I would have posted this in the DCS forum, but I figured it was more of a rendering program-related question and not the sim itself. I'm trying to stop my DCS/FC3 videos from being so pixelated and degraded after I render them and upload them my Youtube channel. See my most recent releases here [video:youtube] [video:youtube] I'm using NVIDIA Shadowplay to do all of my capturing. The kicker is the raw files look pretty clean and only get degraded but so much. However, when I render the captured clips the degrade even more (slightly more pixelation but barley noticeable)and then when I upload the files to Boobtube it looks like I'm trying to get a rabbit ears VHF station during a snow storm. I have tired different program, Windows Live Movie Maker and Cyberlink's Power Director, and have rendered files in WMA, AVI, MPEG-2, AVC, and XAVC S at full HD at 1980x1080 and 30p or higher, but I still get the same pixelated effect. Sony Vegas (trial) showed a lot of promise and gave me the cleanest rendered files and those videos subsequently came out the cleanest on Youtube as well.. FYI: I run DCS at 1980x1080, all full settings (visible visible range is turned down some and civ traffic is off). My captures usually range between 30 and 65 FPS depending on the number of aircraft/objects active.
×

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