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 112 results

  1. 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
  2. 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
  3. 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.
  4. Version 1.0a

    68 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.
  5. The List of Modules in Development are the F/A-18C, SU-27SM, F-15C, FW-190, MIG-21, F-86F, L-29, UH-1H, MI-8MTV2, AH-1G, Mi-24, OH-58 http://www.youtube.com/watch?feature=player_detailpage&v=WBGLb98zkFQ And now you know why the SU-27 and F-15C from FC3 both have 6DoFF Pits.
  6. File Name: A-10 & F/A-18C Pilot Photoshop Template (2048x2048) File Submitter: HomeFries File Submitted: 09 January 2013 File Category: A-10A/C Skins This is the template I used to create the pilot skins for default A-10 aircraft. The template is 2048x2048 to accommodate the higher resolution F-15C pilot skin, though the original A-10 skin is available as background. Since the F/A-18C pilot skins use the same texture (albeit shaded), I have added USN/USMC units as well. The template includes green, desert, and black flightsuits, the SRU-21P survival vest, different unit patches, morale patches, A-10 type patches, and pencil patches. In addition, there is a modular nametag set that allows different colored nametags, different types of warfare badges (e.g. USN Pilot & NFO wings, Jump wings, etc.), and a place to add your name. Click here to download this file
  7. Version 1.62

    91 downloads

    This is the template I used to create the pilot skins for default A-10 aircraft. The template is 2048x2048 to accommodate the higher resolution F-15C pilot skin, though the original A-10 skin is available as background. Since the F/A-18C pilot skins use the same texture (albeit shaded), I have added USN/USMC units as well. The template includes green, desert, and black flightsuits, the SRU-21P survival vest, different unit patches, morale patches, A-10 type patches, and pencil patches. In addition, there is a modular nametag set that allows different colored nametags, different types of warfare badges (e.g. USN Pilot & NFO wings, Jump wings, etc.), and a place to add your name.
  8. File Name: A-10A/C High Resolution Pilot Skins for Default Aircraft File Submitter: HomeFries File Submitted: 08 January 2013 File Category: A-10A/C Skins ModMan 7.3 with the November 2012 update is required to use this mod. If you arent using ModMan 7.3 (Nov 2012), then see the bottom of this file for manual installation instructions. This mod replaces the default 1024x1024 pilot texture with 2048x2048 pilot textures based on the pilot texture for the F-15C. The high resolution textures were ported over and adjusted where required to maintain compatibility with the slight differences in the A-10 pilot texture. On top of this, I have added unit patches to each of the default USAF squadrons included with DCS World. This also includes unit morale patches on the right shoulder where applicable and the proper Major Command (MAJCOM) on the chest. I have also tweaked the description.lua files to apply the F-15 helmet (the Kevlar grey helmet), replacing the default white helmet that is better served for USN aircraft. I did not replace the helmet texture to ensure compatibility with other aircraft; should you wish to apply the kevlar helmet to other 3rd party A-10 skins you can analyze the description.lua files for the proper lines to add to your other files. Finally, I added a default pilot_a10.dds file to TempTextures, which ensures that the high resolution skin is available for 3rd party A-10 skins. Since there is no designated squadron for a generic skin, I used a "Hawgsmoke 2012" patch on the right shoulder to add color. If you do not wish to use this for the default A-10 pilot skin, just remove pilot_a10.dds from the Bazar\TempTextures folder, and the original A-10 pilot will be restored for all other skins. Manual Installation: If you wish to manually install this mod, then back up your Bazar\Liveries\A-10A and Bazar\Liveries\A-10C folders. Once you have done this, then just unzip the files to your DCS World folder, ensuring that the recursive folder structure is intact. Manual Removal: 1. Restore your original Liveries folders (you did back them up, right?) 2. Delete "pilot_a10.dds" from the Bazar\TempTextures folder 3. Delete the folder Bazar\World\Textures\A-10 (don't worry; the original files are in the A-10.zip file in the Textures folder) Enjoy! -Home Fries Click here to download this file
  9. Version 1.3

    112 downloads

    ModMan 7.3 with the November 2012 update is required to use this mod. If you arent using ModMan 7.3 (Nov 2012), then see the bottom of this file for manual installation instructions. This mod replaces the default 1024x1024 pilot texture with 2048x2048 pilot textures based on the pilot texture for the F-15C. The high resolution textures were ported over and adjusted where required to maintain compatibility with the slight differences in the A-10 pilot texture. On top of this, I have added unit patches to each of the default USAF squadrons included with DCS World. This also includes unit morale patches on the right shoulder where applicable and the proper Major Command (MAJCOM) on the chest. I have also tweaked the description.lua files to apply the F-15 helmet (the Kevlar grey helmet), replacing the default white helmet that is better served for USN aircraft. I did not replace the helmet texture to ensure compatibility with other aircraft; should you wish to apply the kevlar helmet to other 3rd party A-10 skins you can analyze the description.lua files for the proper lines to add to your other files. Finally, I added a default pilot_a10.dds file to TempTextures, which ensures that the high resolution skin is available for 3rd party A-10 skins. Since there is no designated squadron for a generic skin, I used a "Hawgsmoke 2012" patch on the right shoulder to add color. If you do not wish to use this for the default A-10 pilot skin, just remove pilot_a10.dds from the Bazar\TempTextures folder, and the original A-10 pilot will be restored for all other skins. Manual Installation: If you wish to manually install this mod, then back up your Bazar\Liveries\A-10A and Bazar\Liveries\A-10C folders. Once you have done this, then just unzip the files to your DCS World folder, ensuring that the recursive folder structure is intact. Manual Removal: 1. Restore your original Liveries folders (you did back them up, right?) 2. Delete "pilot_a10.dds" from the Bazar\TempTextures folder 3. Delete the folder Bazar\World\Textures\A-10 (don't worry; the original files are in the A-10.zip file in the Textures folder) Enjoy! -Home Fries
  10. Somewhere off the northeastern coast of Florida, where Georgia can be seen off in the distance.... An approximate 1:40min short.
  11. I think I've figured out the basics of skinning the F-15, including the TGA files vs. BMP to create "decals" similar to those in SF2. This opens the possibility of creating custom nose art and canopy names for myself and other friends. However, doing so on skins other than default skins (already zipped and in path) will require a huge amount of storage (liveries) or manual entries into graphics.cfg (common files to a zip). The most elegant solution is the zipfile for the skin (the tga dds files go into the livery), but I can't figure out how to get modman to make dynamic entries into cfg files. I know there are cfg and misc options in the mod maker, but there are no instructions or tutorials that I could find. The closest thing, the CDDS tutorial, seems to be obsolete with DCSW which now does the same thing with conventional zip files and native use of DDS. Does anybody know how to use the cfg/misc features of modman, or if not is it still a feasible solution to bundle files in a CDDS? Thanks in advance.
  12. With the release of DCS World and the recent pre-order/beta acces to FC3, it appears that the LOMAC lifecycle has come full circle. With the transition of the franchise to DCSW and the modularity of the DCSW engine, I humbly propose a separate DCS forum and file section, separated along parallel lines from LOMAC much like Strike Fighters 1 vs SF2. Along the same lines of the SF1/SF2 Knowledge Bases, I would also love to see a DCS Knowledge Base. Topics of which I have interest include: Which BS1/FC2 mods are compatible with DCSW? Are A-10C/BS2 standalone mods compatible with DCSW? If not, what needs to be done to convert them? Which legacy skins are compatible with DCSW? This includes LOMAC/FC1 as well as FC2/BS1. What needs to be done to convert them to the Livery? Mission Editor tips and techniques. How to add LODs, and are there multiplayer issues? How to convert BS1/FC2 missions to DCSW (FC2 missions are bugged in FC3, but this should be fixed for release). Basic LUA scripting techniques (i.e. How do I fix a controller config file without having to clear category ) I would argue that a DCS Knowledge Base would be even more valuable than the SF series knowledge bases, since the community seems to be migrating in this direction, and because of limited activations the importance of not screwing up ones' install has become that much more prominent. Your thoughts?
×

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