Jump to content

Search the Community

Showing results for tags 'fc3'.



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
    • EAWPRO - New Location Redirect
    • 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
  • EAWPRO's Discussions

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
  • 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
  • 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
  • Canvas Knights WW1
  • 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
    • Main Game Files and Updates
    • GTR/GTR2
    • Aircraft
    • Aircraft Skins
    • Ground and Sea Vehicles
    • Scenery, Maps, and Objects
    • Missions
    • Miscellaneous
    • Mods
    • Tools
  • 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 15 results

  1. 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
  2. and She HAS Reigned Supreme in her Domain... Been a while, but finally got some decent clips together for another video. Still toying with formatting, seems like I lost some "detail" during the multiple compressions these clips went through (DCS to FRAPs to Sony to WMV to Youtube). Still have not found a way to minimize that, while simultaneously keeping the file size down. Guest Appearances by the 67th FS and the California Air National Guard.
  3. Hi Chaps I'm having a problem with mission 6 in the Revanche campaign - if anyone here has flown it and got a mission success, I'd be keen to hear how you achieved it. I've flown the mission about 8 times now, and last night I thought I had finally cracked it, but no - I got neither a 'mission success' nor 'mission failed' - so I'm stuffed! I know what I am supposed to do - attack the units that get put in by the Chinook flight, and make sure our convoy gets through. The first problem is that it says there are four Su-25As in my flight, but in fact there are only two. Then there are lots of AA about and with the kind of weapons available to me, it means getting in close enough to ID the targets (at least 2 Strela vehicles and the odd Igla), and the wingman instantly ditches his load when we come under fire, and heads for home. So I am left to do everything myself. 5 times I eventually got shot down. Once I got a mission fail whilst flying and the convoy was miles away, so I've no idea why. Once I even ran out of fuel before the convoy had even reached the area where the enemy had landed! Just a kilometer from landing for fuel at Telek Last night I got to the area before the Chinooks had offloaded and together with my my wingman, we downed all but one of them, who limped home damaged - so no troops landed and I even waited for the allied convoy to get to Telek before exiting, but again, no mission success. I get the feeling I am going to have to hang back and wait until all the Chinooks have offloaded and left the area and then go in and kill everything with my meagre ordnance load (which wouldn't seem to be possible) on my own - maybe get reloaded at Telek once before the convoy arrives.
  4. File Name: Su-27 Fictional Skins: US Navy Fighter Squadrons (Volume I) File Submitter: HomeFries File Submitted: 26 June 2013 File Category: Su-27 Skins Su-27 Fictional Skins: US Navy Fighter Squadrons (Volume I) for DCS World 1.2.14 and later This is a collection of eight skins representing three US Navy fighter squadrons using historical F-14 Tomcat liveries. The squadrons included are: VF-21 Freelancers (CAG, CO, Line birds) VF-103 Jolly Rogers (CAG, CO, Line birds) VF-124 Gunfighters (CO, Line birds) The VF-103 skins date from their 2000 deployment with CVW-17 on the USS George Washington. Included as the CO bird is the famous "Santa Cat", which has the jolly roger decked out in Christmas gear. Most markings have been westernized, and the pilots have been given USN flightsuits with Naval Aviator wings and squadron patches. The helmet remains Russian made. 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. These skins were inspired by Clave's Deviant Art gallery: http://ws-clave.deviantart.com/gallery/6112394?offset=432 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! Click here to download this file
  5. Version 1.12

    33 downloads

    Su-27 Fictional Skins: US Navy Fighter Squadrons (Volume I) for DCS World 1.2.14 and later This is a collection of eight skins representing three US Navy fighter squadrons using historical F-14 Tomcat liveries. The squadrons included are: VF-21 Freelancers (CAG, CO, Line birds) VF-103 Jolly Rogers (CAG, CO, Line birds) VF-124 Gunfighters (CO, Line birds) The VF-103 skins date from their 2000 deployment with CVW-17 on the USS George Washington. Included as the CO bird is the famous "Santa Cat", which has the jolly roger decked out in Christmas gear. Most markings have been westernized, and the pilots have been given USN flightsuits with Naval Aviator wings and squadron patches. The helmet remains Russian made. 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. These skins were inspired by Clave's Deviant Art gallery: http://ws-clave.deviantart.com/gallery/6112394?offset=432 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!
  6. File Name: Broken Wing (Single Player) File Submitter: HomeFries File Submitted: 15 February 2013 File Category: DCS Singleplayer Missions "Broken Wing" Singleplayer Mission for DCS World A-10C + FC3 (optional) by Bahger. Uploaded with permission. Two hours ago, a "black" SpecOps UH-60 ("BROKEN WING") crashed near the Russian border. A USMC combat engineer team, "ROADKILL", is en route to recover the helo but intel sources now indicate that the Russians are preparing to mount a raid across the border to steal the bird's classified avionics. ROADKILL has been re-tasked to push to the crash site at maximum speed and to use explosives to destroy the Blackhawk before the Russians get to it. Your task is to protect ROADKILL and to respond to the Russian incursion with decisive force. Briefing: i. SITUATION: Enemy forces: Likely enemy disposition: Ground: A task force consisting of a platoon-sized armored recon element and a reinforced platoon-sized assault force. Both enemy armor formations will deploy with attached mobile Shilka (SA-9) air defense units. Air (CAP): 2x MiG-23MLD "Floggers". Friendly forces: ROADKILL is a combat engineer team consisting of 4x LAV-25s and 2x HMMWVs with attached support from 2x Stryker ATGMs. CAP: 2x F-15Cs"UZI" are about to push from Senaki-Kolkhi to fly CAP. CAS/Strike: 2x A-10Cs ("SPRINGFIELD") are about to push from Sukhumi-Babushara to provide CAS to ROADKILL, to help secure the crash site and to interdict all enemy units meaneuvering south of the border. 2x A-10Cs (DODGE) are holding south of the AO and can be deployed as a striker flight. AWACS: OVERLORD is on station and transmitting on 255 VHF FM. SEAD: No dedicated SEAD/DEAD is available at this time. A-10C flights must perform SEAD/DEAD against local air defenses attached to enemy armor. ii. MANEUVER - Enemy: Recon: We believe that the Russian Recon formation will push south-east through the town of LESELIDZE in order to form a bridgehead at the east end of the town to screen/block ROADKILL's only access point to the crash site from the south. Assault: The enemy Assault group will either reinforce the recon units in LESELIDZE or will divert to the east after crossing REDBRIDGE, approaching the crash site from high ground to the north-east, working with the recon group in Leselidze to attempt a "pincer" maneuver against the objective. Air: The AO will *not* be a permissive environment for Blue CAS as long as a threat exists from the MiG-23 CAP and from SA-9 units embedded with Red ground forces. - Friendly: CAP: Blue F-15s will deploy to intercept Red CAP south of the border and to secure the AO for safe operation of CAS in zone. UZI will fly CAP in zone until the crash site has been secured and the UH-60 destroyed. CAS: Both CAS flights have flightplan holds and should hold or push at the discretion of flight leads according to their assessment of remaining threats from the Red CAP. OVERLORD will provide SITREPs to update CAS flights re. UZI's arrival in the AO and elimination of the enemy CAP threat ("GRAND SLAM") Operational references: The following Mission Steerpoints are available to all CAS flights: BLUEBRIDGE: This bridge is ROADKILL's only possible approach point to the crash site from the south/east and is therefore a chokepoint. REDBRIDGE: This bridge is the likely border crossing point for enemy ground forces and is therefore a chokepoint. LESELIDZE COASTAL ROAD: This steerpoint marks the coastal road likely to be taken by enemy ground forces approaching BLUEBRIDGE. BROKEN WING: This steerpoint marks the exact location of the crashed helo. Comms: All elements will use 255 VHF FM for tactical comms. ROE: All Russian military vehicles and personnel south of the border will be violating Georgian territorial sovreignty. Allied units are authorised to attack any such unit, pre-emptively if necessary. iii. Victory Conditions: All victory conditions will be calculated when ROADKILL has remounted and extracted from BROKEN WING across BLUEBRIDGE, so CAS flights should take care to cover this movement to prevent any further attacks on the group by remaining enemy units. Players will be notified of their level of success in this mission when ROADKILL's extraction is complete, as follows: Blue TOTAL VICTORY Blue will win a Total Victory when: - The downed helo is destroyed and ROADKILL has sustained no casualties. Blue VICTORY: Blue will win a Victory when: - The downed helo is destroyed and ROADKILL has sustained less than 25% casualties. Blue DEFEAT: Blue will lose the mission when: - The downed helo is destroyed and ROADKILL has sustained more than 50% casualties. OR - ROADKILL has been wiped out. IV. Mission Editor's notes: This mission is flyable in one of three roles, assuming the player has DCS World with both FC3 and A-10C modules installed. Two of these roles will spawn as AI flights with identical tasking if the player does not choose to fly them himself: F-15C CAP and A-10C CAS. The following secondary flight is also available to the player: A-10C Strike ("Dodge") This flight is equipped for an LGB stand-off strike to destroy REDBRIDGE if the situation allows. If this flight is chosen, the primary AI CAS and CAP flights will still spawn. There is no AI substitution for this flight if it is not chosen by the player. If the player wishes to see the mission play out with both CAS and CAP roles taken by AI, or to "pinch hit" in an undefined role, he should choose to fly as the A-10C squadron c/o ("Ford"), a two-ship on alert at Kobuleti. Big thanks to: Bruce P for custom radio comms (ROADKILL). Don H (Home Fries) for custom radio comms (OVERLORD), playtesting, refinement of triggers and wise counsel re. programming logic. Click here to download this file
  7. File Name: Broken Wing (Multiplayer) File Submitter: HomeFries File Submitted: 16 February 2013 File Category: DCS Multiplayer Missions "Broken Wing" Multiplayer Mission for DCS World A-10C + FC3 (optional) by Bahger. Uploaded with permission. Two hours ago, a "black" SpecOps UH-60 ("BROKEN WING") crashed near the Russian border. A USMC combat engineer team, "ROADKILL", is en route to recover the helo but intel sources now indicate that the Russians are preparing to mount a raid across the border to steal the bird's classified avionics. ROADKILL has been re-tasked to push to the crash site at maximum speed and to use explosives to destroy the Blackhawk before the Russians get to it. Your task is to protect ROADKILL and to respond to the Russian incursion with decisive force. Briefing: i. SITUATION: Enemy forces: Likely enemy disposition: Ground: A task force consisting of a platoon-sized armored recon element and a reinforced platoon-sized assault force. Both enemy armor formations will deploy with attached mobile Shilka (SA-9) air defense units. Air (CAP): 2x MiG-23MLD "Floggers". Friendly forces: ROADKILL is a combat engineer team consisting of 4x LAV-25s and 2x HMMWVs with attached support from 2x Stryker ATGMs. CAP: 2x F-15Cs"UZI" are about to push from Senaki-Kolkhi to fly CAP. CAS/Strike: 2x A-10Cs ("SPRINGFIELD") are about to push from Sukhumi-Babushara to provide CAS to ROADKILL, to help secure the crash site and to interdict all enemy units meaneuvering south of the border. 2x A-10Cs (DODGE) are holding south of the AO and can be deployed as a striker flight. AWACS: OVERLORD is on station and transmitting on 255 VHF FM. SEAD: No dedicated SEAD/DEAD is available at this time. A-10C flights must perform SEAD/DEAD against local air defenses attached to enemy armor. ii. MANEUVER - Enemy: Recon: We believe that the Russian Recon formation will push south-east through the town of LESELIDZE in order to form a bridgehead at the east end of the town to screen/block ROADKILL's only access point to the crash site from the south. Assault: The enemy Assault group will either reinforce the recon units in LESELIDZE or will divert to the east after crossing REDBRIDGE, approaching the crash site from high ground to the north-east, working with the recon group in Leselidze to attempt a "pincer" maneuver against the objective. Air: The AO will *not* be a permissive environment for Blue CAS as long as a threat exists from the MiG-23 CAP and from SA-9 units embedded with Red ground forces. - Friendly: CAP: Blue F-15s will deploy to intercept Red CAP south of the border and to secure the AO for safe operation of CAS in zone. UZI will fly CAP in zone until the crash site has been secured and the UH-60 destroyed. CAS: Both CAS flights have flightplan holds and should hold or push at the discretion of flight leads according to their assessment of remaining threats from the Red CAP. OVERLORD will provide SITREPs to update CAS flights re. UZI's arrival in the AO and elimination of the enemy CAP threat ("GRAND SLAM") Operational references: The following Mission Steerpoints are available to all CAS flights: BLUEBRIDGE: This bridge is ROADKILL's only possible approach point to the crash site from the south/east and is therefore a chokepoint. REDBRIDGE: This bridge is the likely border crossing point for enemy ground forces and is therefore a chokepoint. LESELIDZE COASTAL ROAD: This steerpoint marks the coastal road likely to be taken by enemy ground forces approaching BLUEBRIDGE. BROKEN WING: This steerpoint marks the exact location of the crashed helo. Comms: All elements will use 255 VHF FM for tactical comms. ROE: All Russian military vehicles and personnel south of the border will be violating Georgian territorial sovreignty. Allied units are authorised to attack any such unit, pre-emptively if necessary. iii. Victory Conditions: All victory conditions will be calculated when ROADKILL has remounted and extracted from BROKEN WING across BLUEBRIDGE, so CAS flights should take care to cover this movement to prevent any further attacks on the group by remaining enemy units. Players will be notified of their level of success in this mission when ROADKILL's extraction is complete, as follows: Blue TOTAL VICTORY Blue will win a Total Victory when: - The downed helo is destroyed and ROADKILL has sustained no casualties. Blue VICTORY: Blue will win a Victory when: - The downed helo is destroyed and ROADKILL has sustained less than 25% casualties. Blue DEFEAT: Blue will lose the mission when: - The downed helo is destroyed and ROADKILL has sustained more than 50% casualties. OR - ROADKILL has been wiped out. IV. Mission Editor's notes: This mission is flyable in one of three roles, assuming the player has DCS World with both FC3 and A-10C modules installed. Two of these roles will spawn as AI flights with identical tasking if the player does not choose to fly them himself: F-15C CAP and A-10C CAS. The following secondary flight is also available to the player: A-10C Strike ("Dodge") This flight is equipped for an LGB stand-off strike to destroy REDBRIDGE if the situation allows. If this flight is chosen, the primary AI CAS and CAP flights will still spawn. There is no AI substitution for this flight if it is not chosen by the player. If the player wishes to see the mission play out with both CAS and CAP roles taken by AI, or to "pinch hit" in an undefined role, he should choose to fly as the A-10C squadron c/o ("Ford"), a two-ship on alert at Kobuleti. Big thanks to: Bruce P for custom radio comms (ROADKILL). Don H (Home Fries) for custom radio comms (OVERLORD), playtesting, refinement of triggers and wise counsel re. programming logic. Click here to download this file
  8. Version 1.0a

    35 downloads

    "Broken Wing" Multiplayer Mission for DCS World A-10C + FC3 (optional) by Bahger. Uploaded with permission. Two hours ago, a "black" SpecOps UH-60 ("BROKEN WING") crashed near the Russian border. A USMC combat engineer team, "ROADKILL", is en route to recover the helo but intel sources now indicate that the Russians are preparing to mount a raid across the border to steal the bird's classified avionics. ROADKILL has been re-tasked to push to the crash site at maximum speed and to use explosives to destroy the Blackhawk before the Russians get to it. Your task is to protect ROADKILL and to respond to the Russian incursion with decisive force. Briefing: i. SITUATION: Enemy forces: Likely enemy disposition: Ground: A task force consisting of a platoon-sized armored recon element and a reinforced platoon-sized assault force. Both enemy armor formations will deploy with attached mobile Shilka (SA-9) air defense units. Air (CAP): 2x MiG-23MLD "Floggers". Friendly forces: ROADKILL is a combat engineer team consisting of 4x LAV-25s and 2x HMMWVs with attached support from 2x Stryker ATGMs. CAP: 2x F-15Cs"UZI" are about to push from Senaki-Kolkhi to fly CAP. CAS/Strike: 2x A-10Cs ("SPRINGFIELD") are about to push from Sukhumi-Babushara to provide CAS to ROADKILL, to help secure the crash site and to interdict all enemy units meaneuvering south of the border. 2x A-10Cs (DODGE) are holding south of the AO and can be deployed as a striker flight. AWACS: OVERLORD is on station and transmitting on 255 VHF FM. SEAD: No dedicated SEAD/DEAD is available at this time. A-10C flights must perform SEAD/DEAD against local air defenses attached to enemy armor. ii. MANEUVER - Enemy: Recon: We believe that the Russian Recon formation will push south-east through the town of LESELIDZE in order to form a bridgehead at the east end of the town to screen/block ROADKILL's only access point to the crash site from the south. Assault: The enemy Assault group will either reinforce the recon units in LESELIDZE or will divert to the east after crossing REDBRIDGE, approaching the crash site from high ground to the north-east, working with the recon group in Leselidze to attempt a "pincer" maneuver against the objective. Air: The AO will *not* be a permissive environment for Blue CAS as long as a threat exists from the MiG-23 CAP and from SA-9 units embedded with Red ground forces. - Friendly: CAP: Blue F-15s will deploy to intercept Red CAP south of the border and to secure the AO for safe operation of CAS in zone. UZI will fly CAP in zone until the crash site has been secured and the UH-60 destroyed. CAS: Both CAS flights have flightplan holds and should hold or push at the discretion of flight leads according to their assessment of remaining threats from the Red CAP. OVERLORD will provide SITREPs to update CAS flights re. UZI's arrival in the AO and elimination of the enemy CAP threat ("GRAND SLAM") Operational references: The following Mission Steerpoints are available to all CAS flights: BLUEBRIDGE: This bridge is ROADKILL's only possible approach point to the crash site from the south/east and is therefore a chokepoint. REDBRIDGE: This bridge is the likely border crossing point for enemy ground forces and is therefore a chokepoint. LESELIDZE COASTAL ROAD: This steerpoint marks the coastal road likely to be taken by enemy ground forces approaching BLUEBRIDGE. BROKEN WING: This steerpoint marks the exact location of the crashed helo. Comms: All elements will use 255 VHF FM for tactical comms. ROE: All Russian military vehicles and personnel south of the border will be violating Georgian territorial sovreignty. Allied units are authorised to attack any such unit, pre-emptively if necessary. iii. Victory Conditions: All victory conditions will be calculated when ROADKILL has remounted and extracted from BROKEN WING across BLUEBRIDGE, so CAS flights should take care to cover this movement to prevent any further attacks on the group by remaining enemy units. Players will be notified of their level of success in this mission when ROADKILL's extraction is complete, as follows: Blue TOTAL VICTORY Blue will win a Total Victory when: - The downed helo is destroyed and ROADKILL has sustained no casualties. Blue VICTORY: Blue will win a Victory when: - The downed helo is destroyed and ROADKILL has sustained less than 25% casualties. Blue DEFEAT: Blue will lose the mission when: - The downed helo is destroyed and ROADKILL has sustained more than 50% casualties. OR - ROADKILL has been wiped out. IV. Mission Editor's notes: This mission is flyable in one of three roles, assuming the player has DCS World with both FC3 and A-10C modules installed. Two of these roles will spawn as AI flights with identical tasking if the player does not choose to fly them himself: F-15C CAP and A-10C CAS. The following secondary flight is also available to the player: A-10C Strike ("Dodge") This flight is equipped for an LGB stand-off strike to destroy REDBRIDGE if the situation allows. If this flight is chosen, the primary AI CAS and CAP flights will still spawn. There is no AI substitution for this flight if it is not chosen by the player. If the player wishes to see the mission play out with both CAS and CAP roles taken by AI, or to "pinch hit" in an undefined role, he should choose to fly as the A-10C squadron c/o ("Ford"), a two-ship on alert at Kobuleti. Big thanks to: Bruce P for custom radio comms (ROADKILL). Don H (Home Fries) for custom radio comms (OVERLORD), playtesting, refinement of triggers and wise counsel re. programming logic.
  9. Version 1.0a

    69 downloads

    "Broken Wing" Singleplayer Mission for DCS World A-10C + FC3 (optional) by Bahger. Uploaded with permission. Two hours ago, a "black" SpecOps UH-60 ("BROKEN WING") crashed near the Russian border. A USMC combat engineer team, "ROADKILL", is en route to recover the helo but intel sources now indicate that the Russians are preparing to mount a raid across the border to steal the bird's classified avionics. ROADKILL has been re-tasked to push to the crash site at maximum speed and to use explosives to destroy the Blackhawk before the Russians get to it. Your task is to protect ROADKILL and to respond to the Russian incursion with decisive force. Briefing: i. SITUATION: Enemy forces: Likely enemy disposition: Ground: A task force consisting of a platoon-sized armored recon element and a reinforced platoon-sized assault force. Both enemy armor formations will deploy with attached mobile Shilka (SA-9) air defense units. Air (CAP): 2x MiG-23MLD "Floggers". Friendly forces: ROADKILL is a combat engineer team consisting of 4x LAV-25s and 2x HMMWVs with attached support from 2x Stryker ATGMs. CAP: 2x F-15Cs"UZI" are about to push from Senaki-Kolkhi to fly CAP. CAS/Strike: 2x A-10Cs ("SPRINGFIELD") are about to push from Sukhumi-Babushara to provide CAS to ROADKILL, to help secure the crash site and to interdict all enemy units meaneuvering south of the border. 2x A-10Cs (DODGE) are holding south of the AO and can be deployed as a striker flight. AWACS: OVERLORD is on station and transmitting on 255 VHF FM. SEAD: No dedicated SEAD/DEAD is available at this time. A-10C flights must perform SEAD/DEAD against local air defenses attached to enemy armor. ii. MANEUVER - Enemy: Recon: We believe that the Russian Recon formation will push south-east through the town of LESELIDZE in order to form a bridgehead at the east end of the town to screen/block ROADKILL's only access point to the crash site from the south. Assault: The enemy Assault group will either reinforce the recon units in LESELIDZE or will divert to the east after crossing REDBRIDGE, approaching the crash site from high ground to the north-east, working with the recon group in Leselidze to attempt a "pincer" maneuver against the objective. Air: The AO will *not* be a permissive environment for Blue CAS as long as a threat exists from the MiG-23 CAP and from SA-9 units embedded with Red ground forces. - Friendly: CAP: Blue F-15s will deploy to intercept Red CAP south of the border and to secure the AO for safe operation of CAS in zone. UZI will fly CAP in zone until the crash site has been secured and the UH-60 destroyed. CAS: Both CAS flights have flightplan holds and should hold or push at the discretion of flight leads according to their assessment of remaining threats from the Red CAP. OVERLORD will provide SITREPs to update CAS flights re. UZI's arrival in the AO and elimination of the enemy CAP threat ("GRAND SLAM") Operational references: The following Mission Steerpoints are available to all CAS flights: BLUEBRIDGE: This bridge is ROADKILL's only possible approach point to the crash site from the south/east and is therefore a chokepoint. REDBRIDGE: This bridge is the likely border crossing point for enemy ground forces and is therefore a chokepoint. LESELIDZE COASTAL ROAD: This steerpoint marks the coastal road likely to be taken by enemy ground forces approaching BLUEBRIDGE. BROKEN WING: This steerpoint marks the exact location of the crashed helo. Comms: All elements will use 255 VHF FM for tactical comms. ROE: All Russian military vehicles and personnel south of the border will be violating Georgian territorial sovreignty. Allied units are authorised to attack any such unit, pre-emptively if necessary. iii. Victory Conditions: All victory conditions will be calculated when ROADKILL has remounted and extracted from BROKEN WING across BLUEBRIDGE, so CAS flights should take care to cover this movement to prevent any further attacks on the group by remaining enemy units. Players will be notified of their level of success in this mission when ROADKILL's extraction is complete, as follows: Blue TOTAL VICTORY Blue will win a Total Victory when: - The downed helo is destroyed and ROADKILL has sustained no casualties. Blue VICTORY: Blue will win a Victory when: - The downed helo is destroyed and ROADKILL has sustained less than 25% casualties. Blue DEFEAT: Blue will lose the mission when: - The downed helo is destroyed and ROADKILL has sustained more than 50% casualties. OR - ROADKILL has been wiped out. IV. Mission Editor's notes: This mission is flyable in one of three roles, assuming the player has DCS World with both FC3 and A-10C modules installed. Two of these roles will spawn as AI flights with identical tasking if the player does not choose to fly them himself: F-15C CAP and A-10C CAS. The following secondary flight is also available to the player: A-10C Strike ("Dodge") This flight is equipped for an LGB stand-off strike to destroy REDBRIDGE if the situation allows. If this flight is chosen, the primary AI CAS and CAP flights will still spawn. There is no AI substitution for this flight if it is not chosen by the player. If the player wishes to see the mission play out with both CAS and CAP roles taken by AI, or to "pinch hit" in an undefined role, he should choose to fly as the A-10C squadron c/o ("Ford"), a two-ship on alert at Kobuleti. Big thanks to: Bruce P for custom radio comms (ROADKILL). Don H (Home Fries) for custom radio comms (OVERLORD), playtesting, refinement of triggers and wise counsel re. programming logic.
  10. Somewhere off the northeastern coast of Florida, where Georgia can be seen off in the distance.... An approximate 1:40min short.
  11. File Name: F-15C/E Default Skin Enhancements File Submitter: HomeFries File Submitted: 07 December 2012 File Category: F-15C Skins Since at least Flaming Cliffs 3 Beta 1.2.2.7570, the left and right patches on the F-15C pilots are reversed (the squadron patch should be on the right shoulder and the organizational/aircraft patch should be on the left). Additionally, all F-15 pilots wear unit patches on their flightsuits except for the 19th Fighter Squadron out of Elmendorf AFB, AK. This mod places the patches on the appropriate shoulder in accordance with USAF uniform regulations, and provides the pilots of the 19th FS Fighting Gamecocks with accurate squadron and wing patches as well as an organizational F-15 patch for the left shoulder. Additionally, the mod adds squadron insignia to the crews in the default USAF F-15E skins, and adds and enhances Israeli Pilot/WSO textures for the IAF F-15C/E skins. Finally, the mod replaces the brown captain insignia on the USAF desert flightsuit with the proper black insignia. Installation (JSGME): This archive file is structured so that you need only create a folder in your JSGME Mods folder for the F-15 Enhancements, then copy this folder tree into that new folder. Then enable the mod using JSGME. Installation (Manual): Prior to extraction, back up all default F-15C/E liveries ( Bazar\Liveries\F-15C\ and Bazar\Liveries\F-15E\). Extract all files to your DCS World folder with the included folder structure intact. This will add the replacement graphics to the Bazar\TempTextures folder and overwrite the description.lua files in your folders. Removal (Manual): Remove the following files from Bazar\TempTextures: pilot_f15_00_b.bmp.ddspilot_f15_01_a.bmp.ddspilot_f15_01_b.bmp.ddspilot_f15_00_IDF_a.ddspilot_f15_01_IDF_a.ddspilot_f15_patch_58_sqdn.tga.ddspilot_f15_patch_65a_sqdn.tga.ddspilot_f15_patch_65b_sqdn.tga.ddspilot_f15_patch_106_sqdn.tga.ddspilot_f15_patch_390_sqdn.tga.ddspilot_f15_patch_493_sqdn.tga.dds Restore your backup description.lua files to the appropriate folders in Bazar\Liveries\F-15C and Bazar\Liveries\F-15E. If you did not back up your original description. lua, then for the F-15C you can delete the last line in the files (regarding the helmet), and delete the line referencing pilot_f15_patch_19_sqdn in the 19th Fighter SQN (AK) folder. For the F-15E you can delete all lines including and after the entry "--added by HF", then delete the pilot*.dds files in the folders. Custom Helmets (optional): One thing I discovered when making use of custom helmets: if you have a custom helmet on one skin, you need to add a helmet line to the description.lua of every skin of that aircraft type, else you will get corrupted textures when displaying different skins. To assist in this, I have placed a line in the 19th Fighter SQN (AK) description.ini (currently remmed out) that you can place in every one of your F-15C skins that is not using a custom helmet. I left the line remmed out because adding this line without adding it in other description.ini files will cause the same texture corruption. Enjoy! -Home Fries Click here to download this file
  12. Version 1.2

    50 downloads

    Since at least Flaming Cliffs 3 Beta 1.2.2.7570, the left and right patches on the F-15C pilots are reversed (the squadron patch should be on the right shoulder and the organizational/aircraft patch should be on the left). Additionally, all F-15 pilots wear unit patches on their flightsuits except for the 19th Fighter Squadron out of Elmendorf AFB, AK. This mod places the patches on the appropriate shoulder in accordance with USAF uniform regulations, and provides the pilots of the 19th FS Fighting Gamecocks with accurate squadron and wing patches as well as an organizational F-15 patch for the left shoulder. Additionally, the mod adds squadron insignia to the crews in the default USAF F-15E skins, and adds and enhances Israeli Pilot/WSO textures for the IAF F-15C/E skins. Finally, the mod replaces the brown captain insignia on the USAF desert flightsuit with the proper black insignia. Installation (JSGME): This archive file is structured so that you need only create a folder in your JSGME Mods folder for the F-15 Enhancements, then copy this folder tree into that new folder. Then enable the mod using JSGME. Installation (Manual): Prior to extraction, back up all default F-15C/E liveries ( Bazar\Liveries\F-15C\ and Bazar\Liveries\F-15E\). Extract all files to your DCS World folder with the included folder structure intact. This will add the replacement graphics to the Bazar\TempTextures folder and overwrite the description.lua files in your folders. Removal (Manual): Remove the following files from Bazar\TempTextures: pilot_f15_00_b.bmp.ddspilot_f15_01_a.bmp.ddspilot_f15_01_b.bmp.ddspilot_f15_00_IDF_a.ddspilot_f15_01_IDF_a.ddspilot_f15_patch_58_sqdn.tga.ddspilot_f15_patch_65a_sqdn.tga.ddspilot_f15_patch_65b_sqdn.tga.ddspilot_f15_patch_106_sqdn.tga.ddspilot_f15_patch_390_sqdn.tga.ddspilot_f15_patch_493_sqdn.tga.dds Restore your backup description.lua files to the appropriate folders in Bazar\Liveries\F-15C and Bazar\Liveries\F-15E. If you did not back up your original description. lua, then for the F-15C you can delete the last line in the files (regarding the helmet), and delete the line referencing pilot_f15_patch_19_sqdn in the 19th Fighter SQN (AK) folder. For the F-15E you can delete all lines including and after the entry "--added by HF", then delete the pilot*.dds files in the folders. Custom Helmets (optional): One thing I discovered when making use of custom helmets: if you have a custom helmet on one skin, you need to add a helmet line to the description.lua of every skin of that aircraft type, else you will get corrupted textures when displaying different skins. To assist in this, I have placed a line in the 19th Fighter SQN (AK) description.ini (currently remmed out) that you can place in every one of your F-15C skins that is not using a custom helmet. I left the line remmed out because adding this line without adding it in other description.ini files will cause the same texture corruption. Enjoy! -Home Fries
  13. I just finished a batch of F-15 personalizations using the f15_decol and pilot_f15_patch files. Both are TGAs converted to DDS, and both allow items such as canopy names, nose art, fuselage/tail art and unit patches to be displayed on the aircraft (decol) and pilot model (patch). I'm trying to find out if there's a way to do this with other aircraft such as the A-10A or A-10C, as this makes for a much easier time to make skins and updates for personalizations like these.
  14. File Name: 3GO-MW Su-27 Flanker model for DCS-World / FC3 File Submitter: HungaroJET File Submitted: 03 December 2012 File Category: DCS Aircraft Mods Su-27 Flanker for DCS-World (based on 3GO Su-27 v1.5 model) v.098e-7570 How to "install": (probaly you will need to "reinstall" if the Auto-updater touched your program) Put all files into DCS World folder and Please edit manually the following two files: Graphics.cfg and PlaneConst.lua (Step 2., 3., 4. is not essential) 1. Open graphics.cfg file with an editor in DCS World\Config folder and search for these rows: ... path = ".\\Bazar\\World\\textures\\WorldTexturesTGA3"; path = ".\\Bazar\\World\\textures\\WorldTexturesTGA2"; path = ".\\Bazar\\World\\textures\\WorldTexturesTGA"; ... copy and paste this row into graphics.cfg at VFSTexturePaths section near ...WorldTexturesTGA...rows path = ".\\Bazar\\World\\textures\\Su-27-3GO"; 2. Make a backup/copy of your original PlaneConst.lua file in DCS World\Scripts\Database folder 3. you will need to edit PlaneConst.lua file in DCS World\Scripts\Database folder ...search for row ~214 and edit gear position rows: it should be look like after you edited: -- main_gear_pos = {-0.537, -2.186, 2.168}, main_gear_pos = {-0.587, -2.16, 2.168}, radar_can_see_ground = true, -- nose_gear_pos = {5.221, -2.186, 0}, nose_gear_pos = {4.021, -2.175, 0}, (Nose Wheel and Main Wheel corrections - More real: "nose lowering" movement when braking, tyre "compression" and turning on ground)...known small bug: AI nose tyre touchdown 4. Delete original Su-27 liveries from ...Eagle Dynamics\DCS World\Bazar\Liveries\su-27 Backup folders and files included here...Backup-Old-CMD-Su-27 (original 3D model files will not overwritten, except broken wings and seperated canopy model but these files are also in "Backup-Old-CMD-Su-27" folder) ***************************************** That's all Cheers HungaroJET If you like this and my other addons/mods please donate me here: https://www.paypal.c...d=YXMCXZA3KTFY6 Thank You Please write comments, problems, ideas, suggestions here: http://forum.lockon....ead.php?t=98113 If you downloaded please read the "Read_Me.txt" file - if you are a skin maker Click here to download this file
  15. Version 0.98e

    305 downloads

    Su-27 Flanker for DCS-World (based on 3GO Su-27 v1.5 model) v.098e-7570 How to "install": (probaly you will need to "reinstall" if the Auto-updater touched your program) Put all files into DCS World folder and Please edit manually the following two files: Graphics.cfg and PlaneConst.lua (Step 2., 3., 4. is not essential) 1. Open graphics.cfg file with an editor in DCS World\Config folder and search for these rows: ... path = ".\\Bazar\\World\\textures\\WorldTexturesTGA3"; path = ".\\Bazar\\World\\textures\\WorldTexturesTGA2"; path = ".\\Bazar\\World\\textures\\WorldTexturesTGA"; ... copy and paste this row into graphics.cfg at VFSTexturePaths section near ...WorldTexturesTGA...rows path = ".\\Bazar\\World\\textures\\Su-27-3GO"; 2. Make a backup/copy of your original PlaneConst.lua file in DCS World\Scripts\Database folder 3. you will need to edit PlaneConst.lua file in DCS World\Scripts\Database folder ...search for row ~214 and edit gear position rows: it should be look like after you edited: -- main_gear_pos = {-0.537, -2.186, 2.168}, main_gear_pos = {-0.587, -2.16, 2.168}, radar_can_see_ground = true, -- nose_gear_pos = {5.221, -2.186, 0}, nose_gear_pos = {4.021, -2.175, 0}, (Nose Wheel and Main Wheel corrections - More real: "nose lowering" movement when braking, tyre "compression" and turning on ground)...known small bug: AI nose tyre touchdown 4. Delete original Su-27 liveries from ...Eagle Dynamics\DCS World\Bazar\Liveries\su-27 Backup folders and files included here...Backup-Old-CMD-Su-27 (original 3D model files will not overwritten, except broken wings and seperated canopy model but these files are also in "Backup-Old-CMD-Su-27" folder) ***************************************** That's all Cheers HungaroJET If you like this and my other addons/mods please donate me here: https://www.paypal.c...d=YXMCXZA3KTFY6 Thank You Please write comments, problems, ideas, suggestions here: http://forum.lockon....ead.php?t=98113 If you downloaded please read the "Read_Me.txt" file - if you are a skin maker
×

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