Leaderboard

In the next DCS update, George AI Copilot/Gunner (CPG) will be receiving a significant upgrade, along with some improvements to his existing logic and behavior, in an effort to make him more realistic, interactive, and capable. It is important to note that no changes have been made to any existing AI Interface commands or control functions. Rather, additional commands have been added to the AI Helper Controls (Left/Right/Up/Down) when the AI Interface is displayed and set to NO WPN, and the Consent To Fire command has been modified as a contextual, multi-purpose button. In the graphic below, the new AI Interface is shown, with the new commands identified. New search tasks (explained below the AI Interface graphic) may be configured using the Left-Long and Right-Long commands while the AI Interface is set to NO WPN. The function of the Consent To Fire command under the current conditions is displayed in the center of the AI Interface, with the short press (<0.5 seconds) function displayed above the long press (>0.5 seconds) function below it. It is worth noting that the Consent To Fire commands may still be used without displaying the AI Interface. For example, if the player wishes for George AI CPG to begin performing an Area search, a long press of the Consent To Fire button may be used without the AI Interface displayed. However, to select a different Area search, the AI Interface will need to be displayed and set to NO WPN. New Search Tasks Up until now, George AI CPG could only be commanded to perform a direct, momentary search for targets along the line-of-sight of the Pilot’s helmet or the TADS sensor turret, and would rank those targets based on threat priority (i.e., air defense units would be at the top of the list). The player may now choose from 7 additional methods for George to search for targets, facilitated by the new changes in the AI Interface. Direct Searches. These are two searches that George was already capable of performing up to this point. PHS SEARCH - George slaves the TADS to the line-of-sight of the Pilot Helmet Sight (PHS) and performs a momentary search for targets. Targets are ranked by threat priority. TADS LOS SEARCH - George performs a momentary search for targets along the current TADS line-of-sight. Targets are ranked by threat priority. Area Searches. These searches allow George to proactively search for targets in a designated area or based on FCR target locations, visually identify FCR targets prior to an engagement, or perform battle damage assessment of engaged FCR targets after an engagement. FWD AREA - George slews the TADS in a 90-degree search pattern directly in front of the helicopter and continuously searches for targets. George will verbally announce when targets are detected but will not generate a Target List unless the AI Interface is displayed. Targets are ranked by threat priority. PHS AREA - George slaves the TADS to the line-of-sight of the Pilot Helmet Sight (PHS) and then slews the TADS in a 45-degree search pattern centered on the PHS-directed azimuth in relation to the helicopter nose and continuously searches for targets. George will verbally announce when targets are detected but will not generate a Target List unless the AI Interface is displayed. Targets are ranked by threat priority. FCR TGTS - George generates a Target List based on FCR target data obtained by the onboard FCR scans performed by the player or received across the datalink via FCR TGT Report or RFHO. George will enable C-Scope and attempt to identify the FCR targets highlighted in the Target List. If the target cannot be seen due to visual obstructions, George will verbally announce it. If the target is destroyed, George will verbally announce it and remove the target from the Target List. OWN PFZ - George slaves the TADS to the PFZ assigned to the ownship and continuously searches for targets within the geographical boundaries of the zone. George will verbally announce when targets are detected but will not generate a Target List unless the AI Interface is displayed. Targets are ranked by threat priority. ACTV PFZ - George slaves the TADS to the activated PFZ and generates a Target List based on FCR target data obtained by the onboard FCR scans performed by the player or received across the datalink via FCR TGT Report or RFHO. George will enable C-Scope and attempt to identify the FCR targets within the geographical boundaries of the zone and highlighted in the Target List. If the target cannot be seen due to visual obstructions, George will verbally announce it. If the target is destroyed, George will verbally announce it and remove the target from the Target List. Point Searches. These searches allow George to search for targets in the vicinity of a TSD point or the FCR Next-To-Shoot (NTS) target after the Player has Linked the TADS to the FCR in the Pilot seat. POINT - George slaves the TADS to the selected TSD point to perform an indirect rocket attack from behind cover; or may be commanded to adjust the TADS field-of-view setting, toggle the selected sensor (FLIR or DTV), or fire the laser, to assist with performing reconnaissance. If subsequently commanded to search for targets, George performs a momentary search for targets. Targets are ranked by geographic proximity to the TSD point, regardless of unit type. LINKED - George may be commanded to adjust the TADS field-of-view setting or toggle the selected sensor (FLIR or DTV), to assist with performing visual identification or battle damage assessment of the FCR NTS target. If subsequently commanded to search for targets, George performs a momentary search for targets. The closest target that matches the classification of the FCR NTS target is ranked as the first target in the Target List, and all remaining targets are ranked by geographic proximity to the NTS target symbol, regardless of unit type. New capabilities and procedures George must be commanded to perform start-up procedures if spawning into a cold start AH-64D. However, George will assist with more of the start-up checklist items such as powering on the FCR and RLWR, and will verbally announce to the player as he completes major items such as boresighting his helmet or when the FCR has finished its power-on sequence. George may also be commanded to perform the relevant shutdown procedures. George is now capable of engaging multiple targets in sequence. When presented with a Target List, the player can select multiple targets from the list, as shown below. In this image, the player has selected 4 targets from the list by pressing the Consent To Fire button as each target is highlighted in the list. If the player presses Right-Short to command George to begin tracking a target that has been added to George's "shoot list", George will slew to the first target in the list (tagged as 1). If the player presses Right-Short to command George to begin tracking a target that is not added to the shoot list, the shoot list is canceled and George will only track/engage that single target. As before, George will still wait for a Consent To Fire command before engaging the target if set to HOLD FIRE. However, once his current target is destroyed, he will automatically slew the TADS to the next target on the shoot list and wait for another Consent To Fire command before engaging the next target. If set to FREE FIRE, George will begin engaging if engagement parameters are met, and then automatically slew to the next target once the first target is destroyed, and immediately engage the next target (again, assuming engagement parameters are met). When tracking a target and GUN or MSL is selected, a short press (<0.5 seconds) of the Consent To Fire command will direct George to fire his assigned weapon as before. If the Consent To Fire command is pressed and held (as signified by the ADJ+ label in the center of the interface), George will adjust the crosshairs onto the center of the target to prevent laser overspill beyond the target itself, and then re-establish an auto-track on the target when Consent To Fire is released. However, the player should fly in a stable manner while George is commanded to refine his aim using this function, which is why the player has been given a command to coordinate the timing of such actions. Improvements to existing logic and more verbal communication The existing logic of George AI CPG has been improved, with more realistic behavior and procedures. For example, if the player has set the RF MSL PWR to OFF, and the player subsequently commands George to use RF missiles, George will set the MSL PWR back to AUTO. George will also verbally communicate to the player what is required for him to perform a command or provide verbal feedback if he is unable to perform a command. For example, if George needs the player to maneuver the helicopter into launch constraints before he can fire a missile, George will verbally request the pilot do so: "Get me in constraints". Previously, George would not fire an AGM-114 missile if any Performance Inhibits or Safety Inhibits were displayed, even if the Player pressed the Consent To Fire button. This would lead to confusion as to why George was announcing "Engaging" but did not actually fire a missile. Safety Inhibits cannot be overridden, but a Performance Inhibit may be overridden if George pulls the weapons trigger to the 2nd detent, which he will now do if ordered to do so. If any inhibit, Performance or Safety, is displayed when George is ready to fire a missile on his current target, George will announce "Constraints" to request that the pilot maneuver the helicopter into appropriate launch constraints. When and if this occurs, the player may now order George to override a Performance Inhibit by pressing the Consent To Fire button (except BAL LIMIT if the target is out of range). However, it is important to note that the presence of a Performance Inhibit increases the possibility the missile may not hit the target, either due to failure to acquire a laser or not being able to maneuver to the target. Therefore, the player (as the "pilot-in-command" of the helicopter) must be judicious with this command when a Performance Inhibit is displayed. This gives the player the freedom to make tactical decisions regarding when it is appropriate to override an inhibit, at the risk of expending a missile without striking the intended target. An updated DCS AH-64D Early Access Guide will be included in the next DCS update to fully describe these new functions and features in detail. We hope that these new features to George AI CPG will provide a much more engaging gameplay experience in the DCS: AH-64D.

https://www.digitalcombatsimulator.com/en/news/changelog/release/2.9.18.12722/ DCS Core Weapons. Work in progress fixes for the following bombs explosive mass: M117, Mk-80 series, and WWII AN-M GP series. This also applies to Guided Bomb Units (GBU) that use the Mk-80 series of warheads. This is connected to the changes for SAMP bombs that we did in the previous patch and will be evaluated and finalized in future patches. Most rocket warhead families (at least Hydra/Zuni/FFAR, S-5/8/13/25, and SNEB-68) are already set up with parameters that match our available sources. Actual effect on targets is subject to change along with implementation of the fragmentation model. (We missed mentioning this in June 18’s update). AI aircraft. AV-8B NA, after taking off from the Tarawa's deck, the planes crash into the water - fixed AI aircraft. Added new B-1B loadouts. AI aircraft. B-52H. Added HSAB and TGP pylon. Added new loadouts. AI aircraft. B-1B. Lead aircraft overshoots end of runway - fixed. AI aircraft. AI collision after landing at some airfields - fixed. AI aircraft. Added possibility for piston engine planes to land on stationary aircraft carriers. AI ships. Samuel Chase. Flak guns unable to engage targets - fixed. AI ships. La Combattante 2 is unknown on RWR - fixed. AI ground units. Fixed a crash if a player's plane assigned to a ground group as a target crashes. AI ground units. RPG infantry rocket visible graphical bug - fixed. (Graphic Issue - Hovering Rocket - RPG Infantry - 2D Video Bugs - ED Forums) Scripting API. Added ability to pass args and return values from mission scripting “a_do_script()” and “a_do_file()” APIs. Scripting API. Changes to the behaviour of net.dostring_in(). This API can be used only with trusted scripts/missions! More details here: Changes to the behaviour of net.dostring_in() - ED Team - ED Forums Mission Editor. GUI Error when using the Draw tool in some cases - fixed. Mission Editor. Added tooltips for Multiselect tool. Spotting Dots. Refactor of spotting dots rendering to tackle issue with their disappearance (Ground units remove air spotting dots entirely in certain circumstances. - View and Spotting Bugs - ED Forums) VORTAC is not transmitting both VOR and DME IDs - fixed. Quick Action Generator: Fixed Units are placed outside Marianas WWII map. Fixed Mission Anti-Ship is generated incorrectly on the Afghanistan map. Voice chat: Fixed. Crash on exit from a server while another client is transmitting. Fixed. Сrash when changing aircraft type while another client is transmitting. DCS: F-16C Viper by Eaglе Dynamics Added AN/AAQ-33 Advanced Targeting Pod (ATP). DCS: F-16C Viper AN/AAQ-33 Part 1 DCS: F-16C Viper ATP Part 2 Fixed: Crash to Desktop HARM POS with HTS Pod installed. Fixed: Missing MPD AG Radar/Maverick/ATP font outlines. This will make mission computer-driven texts and symbols more visible against a very light background. Fixed: Radar scan freezes and weird behaviour after exiting to TWS from ACM STT. Added: AAQ-33 Advanced Targeting Pod chapter in DCS: F-16C Viper Guide. With the addition of the ATP, all listed early access items on the Viper roadmap have been delivered, and the Viper has exited early access (20% discount removed). However, work will continue on several items like the towed decoy, IDM, radar warning receive handoff mode, bug fixes, and tuning. DCS: F/A-18C by Eagle Dynamics Added Terrain Avoidance (TA) Radar Mode. DCS: F/A-18C | Terrain Avoidance Radar Mode Fixed: Fixed: Player IR missiles can see through player aircraft prior to launch. Fixed: Emergency Jettison does not drop all loadouts. Fixed: AIM-7 FLOOD option disappears after momentary track loss. Tracks update in FLOOD mode. Improve the GBU-24 CLAR procedures GBU-24 CLAR max range - Bugs and Problems - ED Forums Fixed: A/G weapons still show up on top SMS push buttons after jettison and/or firing. Fixed: CBU-99 with FMU-140 slightly short in AUTO in another pass. Fixed: ARC-210 COMMS modulation issues. DCS: AH-64D by Eagle Dynamics Added: New George AI CPG commands. Left-Long selects a different Area search when assigned weapon is NO WPN. Right-Long selects a different TSD point when assigned weapon is NO WPN. Consent To Fire is now a contextual, multi-purpose command. Consent To Fire functions for current conditions displayed in center of AI Interface, with the function corresponding with a short press (<0.5 sec) displayed above and the function corresponding with a long press (>0.5 sec) displayed below. Added: New George AI CPG features and abilities. 7 additional methods for searching for targets to George AI CPG. Added 5 Area search methods. Added 2 Point search methods. Search for targets based on geographic proximity to the selected TSD point or FCR Next-To-Shoot (NTS) target, rather than by threat priority. Increase/decrease TADS field-of-view and toggle sensor (FLIR/DTV) when slaved to TSD point or Linked to FCR Next-To-Shoot (NTS) target. Toggle TADS field-of-view (Narrow/Zoom) when tracking a target and NO WPN or RKT is assigned. Toggle sensor (FLIR/DTV) when tracking a target and NO WPN is assigned. Adjust TADS crosshairs aimpoint on target when tracking a target and GUN, MSL, or RKT is assigned. Player should only use this when able to fly in a stable manner. Perform start-up and shutdown procedures when commanded. NOTE: This must be actively commanded by the player now. Engage multiple targets in sequence, as selected by the player from AI Target List. Added: New DCS units to George AI CPG unit labels in Target List. Improved: George AI CPG missile engagement behavior. George will announce “Constraints” if a Safety Inhibit or Performance Inhibit is present to prompt the player to maneuver the helicopter into acceptable launch constraints. George may be commanded to override a Performance Inhibit by pressing Consent To Fire. NOTE: This allows the player to decide when it is appropriate to fire under certain conditions, but risks the missile missing the target if not used appropriately. If missile launchers are in SAFE status, George will press LNCHR ARM if commanded to action SAL2 or RF missiles. If RF MSL PWR is set to OFF, George will set it to AUTO if commanded to action RF missiles. Improved: George AI CPG rocket engagement behavior. George will not fire rockets when in COOP rocket mode. The Pilot (player) is intended to fire rockets in COOP rocket mode. George will announce “Match and shoot” at further range (7000 meters). When in COOP rocket mode, changing rocket settings on the WPN page in Pilot seat will also change George’s rocket settings in AI Interface. Improved: George AI CPG Interface logic when landed (weight-on-wheels). Improved: George AI CPG verbal feedback. George will now tell the player when he cannot perform the commanded action. Will reply with “not ready to engage”, “not ready to fire”, or “standby” if the player presses Consent To Fire and the target is in range but George is not actually ready to engage. This may occur if George is shifting aim to the target or if still lasing for an RF missile handover. Fixed: George AI CPG not firing gun when commanded with ROE HOLD FIRE until previous gun burst impacts. Fixed: George AI CPG time-of-flight estimation when employing AGM-114L. Will now accurately wait for missile impact on target, before firing another missile if target is not destroyed. Updated: DCS: AH-64D Early Access Guide. See Latest Changes section for additional content. Added Helicopter Fundamentals of Flight chapter. Revised/updated George AI chapter with new logic and functions of George as AI CPG. Known Issue: George will not action rockets to enter COOP rocket mode after setting AI Interface to “RKT”. DCS: Data Transfer Cartridge (DTC) by Eagle Dynamics Added Currenthill radars to CMDS tables (Units to follow in future update): added "Project 22160 Patrol Ship [CH]", "Project 22160 Patrol Ship with Tor M2KM [CH]" to NAVAL group (row 22) added "SAM SA-15 Tor M2 Gauntlet [CH]" to already existed "SAM SA-15 'Gauntlet'" added "SAM SA-22 Pantsir-S1 Greyhound [CH]" to GROUND group (row 35) added "SAM IRIS-T SLM STR [CH]" to GROUND group (row 14) Fixed: DTC page ignores hidden on planner and allies only mission setting. Add hotkey for DTC in ME : added Ctrl + D Much of the DTC work is now focused on the Navation/Waypoint elements that allow such items as creating routes, setting target points, pre-briefed points, pre-planned points, lines, offsets, and more based on the aircraft type. DCS: CH-47F by Eagle Dynamics Leg Data: Implemented default weather params initialization based on mission start point Applied default weather params to newly added FPPs Included OAT in Leg Data calculation Added OAT indication on MFD LEG DATA page Implemented predictive calculation for FPPs at mission start Added A/B Fuel, A/B Time, and ΔGWT fields on MFD LEG DATA page Implemented indication for leg parameters exceeding limits Implemented synchronization of FPP Leg Data HSI: Implemented HDG/TRK parking at the end of compass rose on HSI DCTR when angle exceeds 60 degrees from lubber line DIGITAL MAP: Fixed. Map is no longer rendered when not active on any MFD Fixed. Can embark only 24 troops instead of 44 DCS: Mi-24P Hind by Eagle Dynamics ATGM aiming sight external doors are not synced in multiplayer and other clients do not see them opening if sight is used - fixed DCS: Mi-8MTV2 Magnificent Eight by Eagle Dynamics DISS-15 control panel number rolls correction DCS: F-86F by Eagle Dynamics Remove or change default LCtrl+LAlt+T key combo because it intersects with debug key combo - changed default combo to 5 + LAlt + LCtrl DCS: MiG-21bis by Magnitude 3 Updated AI flight model DCS: F4U-1D Corsair by Magnitude 3 Flight Model & Systems: Tuned the oil cooling system Introduced the auto-rich fuel setting. Fixed the drag coefficients for all weapons, drop tanks and pylons Implemented pressure effects on the landing gear while deploying them when flying too fast. Improved the FM on damage modeling. Improved the AI’s engine description & flight model Reversed the AN/ARC-5’s C-38 control unit’s CW/Voice switch operation. Fixed the RPM lever’s mouse control from exceeding 2800 RPM. Fixed the radar signal and gunsight reticle from detaching out of place. Fixed & Updated numerous clickable controls. Fixed the canopy position commands. Added a ‘trim reset’ command. Added axis inputs for the cockpit & gunsight lights. Added the ground crew’s wheel chocks command. Art: Essex Class Carrier: Fixed the damage model and elevators from falling. Adjusted some geometry around the elevators and general ambient occlusion errors. Corrected the weapons’ animations and rotation limits from shooting through the island. Fixed the liveries’ folder structure to allow custom liveries. Corsair Airframe Model: Added the missing right wing fold aileron animations & damage elements. Fixed some rear tail damage elements’ visibility issues. Fixed the flap control rods from poking through the wing. Fixed the gun flames’ visibility with missing wings. Implemented antenna and wing vibrations. Adjusted the fire effects when damage is taken. Corsair Cockpit Model: Increased FoV limit to 140 degrees. Adjusted the textures to be more PBR friendly.(default only, the rest coming later) Fixed the floating UV glowing ‘M’ixture control animation. Fixed the missing shadows when the mirrors are enabled. Adjusted the hydraulic hand pump animation. Implemented cockpit vibrations. Miscellaneous: Adjusted the engine and propeller sounds. (WIP) Adjusted the in-cockpit flap and wing folding sounds. Enabled the AI to deploy the ASM-2-N Bat Bomb Fixed net arg animation code for the landing gear during multiplayer sessions. Added the ability to change the gun convergence during rearm. Mission Editor: Added the ability to change the Mk.IV build numbers. Added the draft values for the Essex class carrier affecting minimum water depth. Added a gun convergence unit of measure label. Missions: Tora! Tora! Tora! – Deleted due to WWII asset pack dependency. Engine Start – Procedural changes. Rocket Attack – Procedural changes & added the missing Tiny Tim 11.75″ rockets. Fixed all Mk.IV livery assignments. DCS: OH-58D Kiowa Warrior by Polychop Simulation Fixed: All digital data on dash detaching from dash on NAV SETUP page Fixed: Perf Page CALC button requiring two button presses Fixed: Hog menu CLASSIFICATION, PRECEDENCE, ACKNOWLEDGE lead to an endless loop DCS: JF-17 by Deka Ironwork Simulations Fixed. Axis cannot move TDC up/down in AA Radar TWS EXP mode Fixed. Time Of Day digit display could show hour number greater than 24 on HUD/UFCP Fixed. TD box on HUD always on horizon Fixed. Some memory leaks of timer Added. More input binding for keyboard and devices TODO. AA radar resolution for close targets DCS Mirage F1 by Aerges "Miscellaneous instrument lighting switch" animation is now cycled. Previously LMB and RMB only clicked it in one respective direction. Added code provisions for correct fuel display in TacView (information passed to TacView developers). Fixed not operating 'Canopy handle - OPEN/CLOSE' input command. Added BAP-100 and BAT-120 bombs. Added IR guided missiles in external underwing stations for F1M (AI only for the time being). Known issue: Jettisoning panel guards in F1BE are not working (clickability and input). It will be fixed in a forthcoming update. Meanwhile, the corresponding correct lua files will be provided in a DCS forum post. DCS: C-101 Aviojet by AvioDev Fixed armament config error when more than one station with rockets is selected. Added code provisions for correct fuel display in TacView (information passed to TacView developers). Fixed basic visual flight training lessons: One of the triggers didn't proceed when setting the speed bug. DCS: Black Shark 3 by Eagle Dynamics Ka-50 and Ka-50 III. Iraq instant action missions. Flaming Cliffs 2024 by Eagle Dynamics F-5E FC: Restored missing Sidewinder Cage/Uncage mode (Missing Sidewinder Cage/Uncage Mode In F-5 - DCS: Flaming Cliffs - ED Forums) DCS: Cold War Germany by Ugra Media Fixed an issue with the geometry of the 3d model collision, which caused the collision to cover a huge area of the map. The name of vortac Frankfurt has been corrected. The call sign of the airfield Northeim has been changed from Albstadt Degerfeld to Northeim. The Walldorf airfield's call sign has been changed from Albstadt Degerfeld to Walldorf. Corrected the names of the cities Weissenfels, Giessen. Changed the location and size of the icons of air defense, radar and hospitals on the map. Improved destruction models of industrial facilities with tall pipes and thermal power plants. Improved field assets, added haystacks and tractors in yellow fields. The height of the typical church has been increased. Added a destruction model of the stadium. Campaigns DCS: F-16C Last Out: Weasels Over Syria II by Ground Pounder Sims Mission 13. Altered position of aircraft incorrectly spawning in front of player at mission start. DCS: F-14B Operation Sandworm Campaign by Sandman Simulations Mission 12. Kneeboard and briefing documentation fixed DCS: F/A-18C Rise of the Persian Lion by Badger633 Mission 3 both versions: F4 timing adjusted to prevent launch. DCS: F/A-18C Operation Mountain Breeze Campaign by Sandman Simulations Missions 3, 8, 13 and 15: AI AAR changed for better reliability DCS: P-51D Debden Eagles Campaign by Reflected Simulations Mission 3: Scripting error fixes DCS: P-47D Wolfpack II: Overlord Campaign by Reflected Simulations Missions 6-12: Survival triggers revised Mission 4: briefing map and doc timings fixed DCS: F-16C Arctic Thunder Campaign by Reflected Simulations Campaign doc updated All Missions: Sniper pod upgrade Mission 9: Manpad callouts fine tuned DCS: F-4E Northern Defenders 'Phantoms Rising' Campaign by Flying Cyking Mission 02 "First Sortie". Fixed incorrect voice-over in food small talk dialogue. Mission 05 "Convoy Hunt". Fixed radio presets. Mission 10 "Finland CAS". Fixed decorative infantry walking on taxiway. Mission 11 "Sam Hunt". Fixed decorative infantry walking on taxiway. Fixed active Game Master slot. Fixed "Skip Briefing" function not stopping briefing voice-over. Fixed floating elevated platform at roadbase. Fixed cryptic ATIS subtitle. Changed wingman skin. Mission 12 "Alakourtti". Fixed decorative infantry walking on taxiway. Mission 13 "Greyhound". Fixed decorative infantry walking on taxiway. DCS: F-16C Last Out: Weasels over Syria II Campaign by Ground Pounder Sims Mission 2 - Updated mission to allow for new bomb blast pattern. DCS: AV-8B Kerman Campaign by Ground Pounder Sims Mission 4 - Updated mission to allow for new bomb blast radius. Mission 10 Part 1 - Updated mission to allow for new bomb blast radius. DCS: UH-1H Peacekeeper Lebanon Campaign by Flying Cyking Mission 05 - "Refugees". Fixed an issue where the helicopter hover trigger did not activate correctly, preventing completion of the rescue task.

DCS Core SA-11 Buk does not trigger RWR warning for launch or tracking - fixed Weapons. AGM-45 all seeker models able to track 052B/054A and HQ7 radar - fixed AI aircraft. AI cannot taxi properly at Rovaniemi (Kola map) if AI group has human taxi with them at the same time - fixed QAG. Units are placed outside Marianas WWII map bounds - fixed QAG. Anti-Ship mission is generated incorrectly on Afghanistan map - fixed AI aircraft. AI F4U will not engage shipping with BAT bomb - fixed Flaming Cliffs by Eagle Dynamics MiG-29. Exported displays not respecting brightness DCS: F-16C Viper by Eaglе Dynamics Fixed: HOTAS commands missing for the HARM WPN page. Fixed: Crash to Desktop when switching to A-A after shooting HARM POS. Fixed: AGM-88 is not able to be fired in POS modes. AGM-88 is not able to be fired in POS modes: fixed wrong 1st threat selection when enter POS mode. fixed threat not deselect using second OSB press. DCS: Data Transfer Cartridge (DTC) by Eagle Dynamics Fixed: Opening DTCs created in versions prior to 2.9.17 causes issues with auto program tables - Added compatibility of DTC auto programs on F18 with older missions. Fixed: Add currenthill radars to CMDS tables - fixed error when after adding new string to the middle of the list, an existing cartridge may be filled incorrectly. DCS: CH-47F by Eaglе Dynamics Fixed. Overlapping text on the Model aircraft CDU page Added. Option to use lower resolution textures for cockpit and cargo hold (via Special options menu) DCS: Yak-52 by Eaglе Dynamics Fixed. Engine parameters for AI bots Fixed. Duplicated commands in the Controls menu DCS: Mosquito FB VI by Eaglе Dynamics Fixed. Undercarriage warning horn sound in improper conditions DCS: Sinai Map by OnReTech Added medium detail zones: Northern Israel, Lebanon, part of Syria. Added terrain textures - color, normal map at new medium detail zones. Added airfields: Ramat David, Damascus Intl, Mezzeh Air Base, Rafic Hariri Intl, Tabuk. Added unique scenes, including on new airfields, 2 unique hangars at Ramat David airfield. Improved Saudi Arabia region. Color correction of terrain textures (entire territory). New normal map (entire territory). Added military bases throughout the terrain, added icons to them in ME. Various bug fixes. Campaigns DCS: AH-64D The Four Horsemen Campaign by Fight's On Simulations M10. Fixed CH-47 not landing issue. Fixed Ground troop now continuing route post contact. All missions resaved in latest release build 2.9.16.10973 DCS: UH-1H Peacekeeper Lebanon Campaign by Flying Cyking Mission 01 "The Ferry Flight". Fixed parking position of AI Mi8 overlapping with player aircraft. DCS: F/A-18C Operation Cerberus North Campaign by Ground Pounder Sims Mission 5 - Fixed trigger that incorrectly detects a hit on the mosque. DCS: A-10C Operation Operation Persian Freedom Campaign by Ground Pounder Sims All missions updated with temporary fix to bypass issues with radio triggers. DCS: F-4E Northern Defenders 'Phantoms Rising' by Flying Cyking Mission 02 "First Sortie". Corrected naming of departure map kneeboard. Mission 04 "Fleet Defender". Temporary fix for Crash to Desktop while engaging the bombers, still under investigation what has caused this. DCS: F-16C Arctic Thunder Campaign by Reflected Simulations Parking spots revised DCS: F/A-18C Rise of the Persian Lion 2 by Badger633 Mission 3: Combat help from your Wing adjusted. F/A-18C Serpent’s Head 2 by Badger633 Mission 10 all variants: Mig attack adjusted.

Su-22M4 got Intake Covers and Ladders, for added imersion during cold start. Of course they are detachable. Also, big thanks to Robsonek - he made over 50 Polish AF Liveries as well as dozen of other - Now we have almost 90 liveries from Azerbaijan, Bulgaria, Czech Republic, East Germany, Hungary, Iran, Libya, Germany, Peru, Russian Air Force, Russian Navy, Slovakia, Syria, Ukraine and Vietnam.

18 July 2025 Dear Fighter Pilots, Partners and Friends, Due to high demand, the DCS Summer Sale 2025 has been extended until the 21st of July at 15:00 GMT. Get up to 50% off aircraft, terrains, campaigns, and important add-ons. Taxi over to our EShop and enjoy. Thank you! We’re putting the finishing touches on our next update, which will add new features to our top of the line aircraft such as the F-16C Viper, F/A-18C, and AH-64D, CH-47F, F4U-1D as well as improving AI behaviour, improved mission-building tools, and solving core system instabilities. Once it clears final tests, we’ll push it live. Stay tuned for the release notes and be ready to download it the moment it lands. Thank you for your passion and support. Yours sincerely, Eagle Dynamics Summer Sale Extension The DCS Summer Sale 2025 has been extended, but only until the afternoon of the 21st of July, 15:00 GMT. Many flagship modules are half-price or heavily discounted. If you have room for only one more fixed-wing icon, let the A-10C II Tank Killer tempt you with its 30mm “Brrrrrrt” cannon and JDAM power at 50% off. If you prefer a modern multi-role fighter, the F/A-18C and F-16C Viper both shed 40% and offer HARM, JDAM, and AMRAAM destruction! Heatblur’s F-14 Tomcat purrs at 30% off, complete with Jester AI and carrier traps that never get old. Their latest F-4E Phantom II also has a very reasonable 25% off! Rotor-heads can claim the AH-64D at 50% off. If you’re into prowling low and fast then the Mi-24P Hind is also half price with Petrovich AI already waiting in the cockpit for you. Deck ops are sweeter with the Supercarrier module at 40% off, pairing perfectly with the sale-price F/A-18C and F-14A/B. Globe-trotters can pick up the Syria map at 30% off and the Nevada Test and Training Range at a scorching 50% off. These prices depart in just a few days, so strap in, whip out your wish-list and get in your next favourite module. Hurry! Offer lasts till the 21st of July at 15:00 GMT. DCS Update Work-in-progress DCS Core The upcoming update will bring improvements to several AI behaviors, Mission Editor tools, and core systems. Various AI aircraft issues will be resolved, as well as new loadouts introduced for the B-1B and B-52H. AI ship and ground unit behaviours are being refined that address engagement issues and graphical bugs. Enhancements to the mission scripting API will allow passing arguments and returning values. The Mission Editor will receive quality-of-life updates like tooltip and GUI fixes. Spotting dot rendering is being reworked to change the maximum number of dots that can be rendered simultaneously. Scripting API changes will require script users and creators to adjust some of their scripts accordingly. The Quick Action Generator will see fixes to unit placement and mission generation on specific maps. Voice Chat stability is to be improved with crash fixes. Additionally, we missed mentioning this change in the last update: The warhead power of the Mk-80 series and M117 bombs was corrected to reflect realistic explosive blast radii. F-16C Viper We are preparing to roll out the AN/AAQ-33 Advanced Targeting Pod (ATP) with a new ATP User Guide chapter. The Viper update will also include a fix for HTS-related crashes and radar freezes. With the addition of the ATP for the Viper, all planned early access features have now been delivered, and the Viper has exited early access! Despite being out of early access, support will continue with planned features like the towed decoy, IDM datalink, and the radar warning receiver handoff mode. F/A-18C Terrain-Avoidance (TA) radar mode will debut, alongside corrections to HARM PB search logic, GBU-24 CLAR procedure corrections, corrected jettison logic, radar FLOOD-mode fixes, and several A/G Stores Management System (SMS) quirks. AH-64D George will soon become far more capable: Seven new search methods, contextual Consent-to-Fire logic, rocket-mode refinements, startup/shutdown on command, multi-target sequencing and richer voice feedback are all heading to your cockpits. An expanded early access guide is queued to cover the new features. Data Transfer Cartridge New Currenthill SAM and naval assets are being pre-populated in Countermeasures Dispenser System (CMDS) tables, legacy-mission compatibility is being restored, hidden-unit filtering will be respected, and a handy Ctrl + D shortcut will open the DTC in the Mission Editor. CH-47F Leg-Data pages will soon auto-populate OAT, ΔGWT and predictive fuel numbers, while HSI/TRK parking logic and digital-map draw calls are being polished. Troop-embark limits and troop-controls are also being repaired. Mi-24P Hind & Mi-8MTV2 Multiplayer sync for the Mi-24P sight-door animations and the Mi-8’s DISS-15 number rolls are being brought up to spec. F-86F Sabre The default LCtrl + LAlt + T debug conflict is being replaced with a safer binding. MiG-21bis (Magnitude 3) An updated AI flight model will sharpen bandit behaviour in aerial combat. F4U-1D Corsair (Magnitude 3) Expect tuned cooling, auto-rich mixture, refined drag, gear-over-speed damage, Bat-bomb AI employment, and a slew of clickable-pit fixes. Essex-class aircraft carrier elevators and carrier damage, antenna vibrations, PBR cockpit textures, and Mission Editor build numbers are all on the way. OH-58D Kiowa Warrior NAV-setup data, PERF CALC logic, and HOG-menu flows are being tidied to eliminate double-presses and endless loops. JF-17 Thunder Radar-TDC axis control, HUD TD-box behaviour, 24-hour TOD wrap-arounds, and several memory leaks will be cured, while new input binds will broaden HOTAS support. Black Shark 3 & Flaming Cliffs 2024 New Iraq instant-action missions for the Ka-50 series and a restored Sidewinder Cage/Uncage mode for the F-5E FC are queued. Cold War Germany Map by Ugra Media The next update will repair an oversized collision hull, correct city and VORTAC names, resize defence and hospital icons, enhance destruction models, new haystacks and tractors across summer fields, raise church spires, and an improved stadium damage model. All items above are in active testing and will ship together once internal tests are completed. Please stay tuned for the incoming update. Important New Features See What’s Coming Soon Prior to the next DCS update, treat yourself to this week’s video instruction previews and forum deep-dive. Each topic prepares you for significant enhancements to the F-16C, F/A-18C, and AH-64D. AN/AAQ-33 ATP – Part 1 (YouTube, 9 min) A first look at the Advanced Targeting Pod’s basic features, procedures, and use examples like camera selection, field of view settings, and explanations of symbology. This will be a significant addition to the Viper and supplement the existing targeting pod. AN/AAQ-33 ATP – Part 2 (YouTube, 12 min) This second instruction video covers more advanced ATP features like Multi-Track, Picture-in-Picture, XR processing, and other interesting features. The ATP will offer new features never seen before in a DCS targeting pod. F/A-18C Terrain-Avoidance Radar (YouTube, 7 min) Follow Matt “Wags” Wagner over Iraq at low-level as he explains the radar Terrain Avoidance (TA) radar mode to safely fly at night or bad weather through mountainous terrain. AH-64D – New George Commands (Forum mini-update) The next DCS update will add huge improvements to commanding “George AI” as the Co-Pilot Gunner to search for and engage enemy forces. The post explains how to use the interface and explains the command logic. Each link is a fast hands-on primer to prepare you for the next update. These will be in parallel to updates to the F-16C and AH-64D manuals that go into even greater detail. Dive in, leave your comments, and be ready when the next update is released. Thank you again for your passion and support, Yours sincerely,

11 July 2025 Dear Fighter Pilots, Partners and Friends, The clock is ticking on our 2025 Summer Sale, which ends on the 13th of July at 15:00 GMT. Fill your hangars with new aircraft, terrains, campaigns, and important add ons at great savings! For the upcoming launch of the MiG-29A, we are finalising the completely re-engineered SPO-15LM Radar-Warning Receiver (RWR) that is built on a new physics-based approach resulting in true blind-zones, side-lobe interference, power-based detection range, and all the quirky threat-sorting that Soviet pilots had to master. With altitude-dependent priority, separate elevation channels, and mode-aware warnings, the SPO-15LM will demand the same mastery its real-world crews required. Please note that time is running out to get a 30% discount during pre-order on the DCS: MiG-29A Fulcrum! We are pleased to inform you that the Early Access launch is planned for September, 2025! The upcoming update will contain vast improvements to the Germany Cold War terrain. We are delighted to share a preview of these improvements that give you a clear sense of where the terrain stands and where it’s heading. Thank you for your passion and support, Yours sincerely, Eagle Dynamics Summer Sale Last chance to save Now is the time to secure hallmark modules like the F-16C Viper, F/A-18C, A-10C II Tank Killer, AH-64D, F-14 Tomcat, and the Supercarrier at up to 50% off. Please enjoy these amazing savings whilst you still can. The DCS Summer Sale 2025 ends on the 13th of July, 2025 at 15:00 GMT. Shop now! SPO-15 Beryoza For the MiG-29A Fulcrum The SPO-15LM for the DCS: MiG-29A Fulcrum module is built using a new physics-based approach. The system simulates a more realistic signal environment in order to ensure the most realistic behavior, algorithms, and limitations of the modelled SPO-15LM RWR system. The new system comes with a radar database containing signatures and behaviors for each radar system in the game, including details like carrier frequency, waveform type and (if applicable) pulse train pattern for different operational modes, antenna and transmitter properties, search strategy depending on range and altitude of the target, signal variability, and CCM used etc. All of this information is used in two ways: to calculate accurate power density at the receiving antenna at each time step, taking into account the physical properties of the signal and the directivity pattern of the transmitter antenna, and to permit realistic modelling of the RWR system itself. On the receiving end, the antenna and receiver properties are similarly taken into account in order to obtain a physically accurate estimate of received power. Each antenna and receiver channel is processed independently. This is critical for accurate modelling of the Soviet systems as they do not use amplitude comparison to estimate emitter azimuth; instead, each of the azimuth channels on the display corresponds to its own set of an antenna, a receiver, and initial processing hardware. As a result the coverage isn’t always 360 degrees. The antenna beamwidth varies with frequency and the antenna gain varies with azimuth and elevation, which causes the detection range and signal power for each emitter to vary not just with radar type and work mode (with the radar transmitter power and antenna gain being the deciding factor rather than its target detection performance) but also with orientation of the aircraft. The emitting antenna directivity pattern is also simulated, which means that, at low distance and high transmitting power, side lobes will be picked up and head-on emissions will bleed into receiving antenna side and back lobes blinding the device. Conversely at low signal power, the system develops blind zones all around the aircraft, and the RWR might fail to pick up the main lobe unless it passes directly over it. The unusual antenna coverage of SPO-15LM in particular requires the pilot to be aware of these blind zones during combat. The improved simulation of signal propagation, together with attached signal signature (PRF, pulse width etc.) allow for accurate modelling of the signal processing algorithms used by the system. The SPO-15LM, while being an analog system, performs many tasks that are normally relegated to digital systems, and some of these analog systems use vastly different approaches compared even to early western systems, which leads to numerous quirks and limitations that are now accurately replicated. The most obvious, as already described, is how the threat azimuth is determined: The airspace around the aircraft is divided into eight azimuth channels covered by 10 azimuth antennas (with, notably, the two forward-facing antennas furthest off-nose on each side merged into a single processing channel), and two elevation channels covered by two elevation antennas. Each of these channels is processed separately with a fixed signal power threshold to activate each channel. The only time the signals are combined is to measure the signal power for the power level display (which now shows the actual signal power in 2 dB increments from threshold, rather than a simple function of range) and for the target priority algorithm. Lack of combined processing also means that coverage of each channel will vary with emitter power and frequency. The system features compensation systems, but they are crude and their effectiveness varies with signal power. The identification and target priority circuits also process each channel separately, meaning that in rare cases the same threat might even be interpreted differently in two neighboring channels, and two threats on opposite azimuths might both be interpreted as a single, main threat if the signals sync up. The identification process involves measuring the repetition time and pulse width of the signal and sorting it into very broad PRF/PW bins. The measurement of PRT can fail if it’s not stable (e.g. due to jitter) making some radars impossible to identify. The presence of multiple emitters in the same sector will also interfere with this process. Even if this part succeeds, the low number of signal parameter bins means that the system might still assign the wrong type to the threat if the signal parameters are close enough. The system is also able to separate Continuous Wave (CW) signals from pulsed signals, and to interpret colocated CW and pulsed emitters as a single emitter in Semi-Active Radar Homing (SARH) guidance mode; it cannot however distinguish between different CW radar types, meaning this feature is susceptible to false alarm. Pilots thus need to be weary of the fact that the system will not always be able to accurately identify the threat type. To improve usability of the system, the threat program is generated automatically based on known threats present in the mission and is provided in the kneeboard for every flight - in reality, the threat program cartridge was issued to units based on the threats present in the combat theatre, and was not designed to be field reprogrammable. The friendly emitters are not included in the program, but they might still be falsely identified as hostile for reasons described above. The system also has an ability to sort the signals into 2 bins by carrier frequency, however in the MiG-29 this feature is permanently disabled, as it requires each sub-band to be scanned separately, reducing probability of detection against radars in search mode (the MiG-29 lacks the full control panel which would allow this function to be switched on and off). The target priority circuit is similarly modelled with its limitations. For instance, the system takes flight altitude into account for the priority algorithm, but it has to be entered manually. In the MiG-29 in particular it is forced to a high setting (8-16 km) without any way to adjust it, meaning, Short Range Air Defense (SHORAD) systems are always treated as low priority. The system will also prioritize radars in track mode over search mode. But again, track mode is recognized entirely by the length of the illumination event being above a certain threshold, so at high signal power emitter side lobes might falsely trigger the track warning. For the priority threat, the system displays the signal power (as well as the highest estimate of weapon range for the given type in terms of equivalent signal power) and the elevation - the latter only being available at high signal power due to much lower sensitivity of the elevation channels. Pre-order today! Don’t miss the exclusive 30% discount. Hurry! This offer only lasts until launch. Once launched into early access, the discount will be reduced to 20% off. Cold War Germany Updates coming soon Ugra-Media’s upcoming update will focus on polish and immersion. Several navigation aids will have corrected identifiers like the Frankfurt VORTAC and Northeim and Walldorf airfields broadcasting their proper callsigns. City names for Weißenfels and Gießen have been corrected, and the F10 map sports resized/repositioned prepared SAM sites, radar, and hospital map icons for faster mission creation and planning. You will notice more realistic destruction effects for industrial plants and power stations, a new damage model for stadiums, and improved fields with hay bales and tractors. Typical village churches will have more accurate heights to improve visual low-level navigation. These refinements move the terrain one step closer to Phase 2 in which it will be expanded further. Please stay tuned for the next update to enjoy these updates. Thank you again for your passion and support, Yours sincerely,

I was quite excited by the new F4U but have heard some criticism of the flight model and engine power. So, I wanted to take a closer look to see how it compares to both the quantitative and qualitative metrics published in the wonderful article entitled “Ending the Argument” by John M. Ellis III and Christopher A. Wheal, published in EAA Sport Aviation, June 1990. Now, for the caveats… The article was a pseudo-controlled experimental flight-test designed to evaluate performance differences between the FG-1D Corsair, P-47D Thunderbolt, F6F-5 Hellcat, and P-51D Mustang. I know we do not have a true representation of the FG-1D, however the engine (R-2800-8) and airframes are close enough for my lackluster piloting skills. Interestingly, it also had two stores pylon installed for the flight tests. Airframe and engine stresses were limited owing to the age of the airframes and using 100LL fuel. This effectively limited the Corsair to Maximum Except for Takeoff (METO). I used 55” of manifold pressure, which is likely too high, but at least my assumptions have been documented. The engine was officially rated for 2000 BHP as in the DCS model. Superchargers were limited to low-blower, and altitudes to 10,000 ft. This makes a difference as I will demonstrate. CG was located at ¾ aft, and there was no mention of fuel load. I selected ½ tanks but will likely revisit my data with another series of tests at full fuel. I removed all ammunition weight as the test aircraft had dummy 50 cals, but no ballast ammo (near as I can tell). My controls setup uses a curve of 25 on all axes, and a 70% saturation on the rudder deflection. I performed some tests multiple times when I suspected higher variance due to my shoddy pilot skills. That being said, I did not perform detailed error analysis on the data presented herein. I welcome others to try the tests and post your results. On to the data… Test 1: Takeoff distance: As per the manual, takeoff distance for the aircraft at 11,000 lbs is approximately 900 ft at sea level, and 1,300 ft over a 50 ft obstacle in no-wind conditions. I won’t say much here other than my takeoffs were all around 1,200-1,300 ft, which I am certain is dominated by inferior pilot skill on my part. The test pilots note a takeoff roll of 1,200 ft at METO power, which is more or less in line with my tests. Test 2: Climb Performance: I will not reprint the graphs from the article as I want to ensure full credit to the original authors and not run afoul of copyright concerns. However, I have used plot digitizer to extract relevant FG-1D data for comparison to our DCS model. The first test is a time-to-climb test, started from the runway up to 10,000 ft. The flight was conducted at full METO power with a climb speed of 135 kts, takeoff weight of 11,055 lbs, and surface temperature of 77 F (as per Table 1 in the article). The figure below shows the time history of MSL altitude for the FG-1D, DCS F4U, and two data points from the F4U-1D manual corresponding to full Mil-Power climbs to 5,000 and 10,000 ft. How I did it: I started on the runway with 50% fuel and executed a standard takeoff. I reduced power to full METO power which was giving ~55 in of manifold pressure @ 2700 RPM. I trimmed the aircraft for 135 kts which required substantial trimming on all axes. The remainder of the flight was relatively hands off, only requiring small corrections to attitude to maintain airspeed. I put the mixture into auto-lean as per the flight manual, and did not engage the blower. Discussion: First off, the flight data presented in the report starts at ~1,000 ft MSL with no discussion of initial conditions. I time aligned my data to overlap the altitude at ~2,000 ft MSL to discount the takeoff and trim transients. After this point, there is a slight climb-gradient difference between the DCS and FG-1D aircraft, however it may be within the test margin of error with time-to-climb difference of 15 seconds. In the article, the Corsair, Thunderbolt, and Mustang were all tightly grouped, with the Hellcat outperforming all by nearly 30 seconds. So, in this case our data would group more closely with the F4U/P47/P51 as it should. The flight test and DCS data align well with the manual to 5,000 ft, however the 10,000 ft mark is quite offset, requiring another 50 seconds of climb. I suspect this is related to the weight of the aircraft and will repeat the tests with full fuel when able. Test 3: Level Accelerations: This is one of my favorite flight test maneuvers as it requires some pilot skill (yikes) and tells you quite a bit about the power and drag characteristics of the aircraft. In brief, the test starts at 10,000 ft and pattern speed, which is ~100 kts in the Corsair in the clean configuration. Full METO power is smoothly applied, and every attempt is made to maintain a constant altitude. The time history of airspeed is logged and is an indicator of excess power from the engine. Flying this test in the Corsair is a real challenge owing to the massive change in trim and quick dance on the rudder pedals necessary to maintain straight, coordinated flight during the maneuver. How I did it: I matched the flight test OAT at 50 F, and started straight and level at 10,000 ft. (I actually began the flight at closer to 150 kts and decelerated to 100 kts without retrimming, which makes the initial acceleration easier to deal with as you only need relieve pressure on the controls to maintain straight and level flight.) I repeated the test three times, once with the blower in neutral, another with the blower in low, and the final test with the manifold pressure limited to 40 in. Discussion: The plot below shows the time history of indicated airspeed for the FG-1D, and three tests corresponding to METO neutral, METO low blower, and 40 in. of manifold pressure settings. The low blower allowed for close to 60 in. of manifold pressure at 10,000 ft, whereas the neutral blower case was closer to ~45 in. Clearly none of the test cases capture the flight test data of the FG-1D, indicating a mismatch in the excess power (Thrust*V_inf-Drag*V_inf). I cannot comment on the sea-level max airspeed debate, but as far as this test confirms, the engine thrust (I said thrust, not power) seems to overpredict the measured performance data of the FG-1D. I.E. the velocity scaling seems to be off, allowing for higher accelerations that would otherwise be possible while still achieving roughly the same top-end speed. I suspect this is due to incorrectly predicting the slope of the C_T vs advance ratio curve at low – medium advance ratios or perhaps a lower induced drag from the airframe. Test 4: Stalls Power on and off stall characteristics were evaluated at 10,000 ft in the clean and dirty configurations (gear, 40 deg flaps). Slow deceleration rates on the order of 3 kts/s were used, though the flight tests were conducted with an even lower gradient of 1 kt/s. Test data in the table below indicates reasonable agreement except for the power-off, clean configuration. In this case, repeated tests were conducted to verify that the aircraft does stall repeatably at a much lower airspeed than the flight test aircraft. This could be due to a mismatch in vehicle weights, but similar tests conducted with full fuel will need to be performed to comment further. Stall performance FG-1D DCS F4U Power off (clean) 85 kts 74 kts Power on (clean) 76 kts 74 kts Power off (dirty) 69 kts 75 kts Power on (dirty) 55 kts 55 kts Qualitatively, the test pilots noted that the FG-1D had no propensity to drop a wing in either direction, favoring instead any turn towards the uncoordinated slip direction (slow wing). In my testing, I attempted to initiate stalls to either side and was unsuccessful in getting the right wing to drop. Asymmetric stall is a complicated aerodynamic phenomenon, but it appears the propeller torque dominates for the DCS module. Test pilots noted that there was little stall warning, perhaps only a few knots with light buffet. In a simulator this can be the best indication of impending stall, even if it’s slightly overdone (Tomcat anyone?). They did note a peculiarity with the Corsair in that the stick force gradient gets very light approaching stall, which would/will be fun when we all get force feedback joysticks! Test 5: Static Lateral-Directional Stability This test sheds light on the rudder authority in a steady, wings-level sideslip. The test pilots noted that the Corsair’s rudder control was extremely heavy compared to the other aircraft tested. Between 180-190 kts, the aircraft required ~50-60% aileron deflection to maintain level flight. In the landing configuration with full flaps and gear, ~20-50%. This wide margin corresponds to the increased influence of the engine torque and spiraling slipstream from the propeller at lower airspeeds. The test pilots noted a peculiarity with the Corsair in that, “The Corsair's only response to left rudder in either configuration as to drop its nose, suggesting weak or non-existent dihedral effect with right sideslip.” How I did it: This one is pretty straight forward. Trim for 180-190 kts at 10,000 ft, then smoothly apply full rudder control. Estimate aileron deflection necessary to maintain zero turn rate as measured by the slip/skid indicator. I repeated this several times in both the left/right directions and at lower airspeeds ~100 kts with full flaps and landing gear extended. Again, all flights were at 50% fuel and no ordinance. Discussion: At airspeeds between 180-190 kts, the aileron deflection is on par with the 50-60% noted by the test pilots, indicating that the rudder authority at higher airspeed is about correct with the 70% saturation limit (first figure below). At lower airspeeds, the aircraft requires almost the same level of aileron control (second figure below), indicating that the rudder control derivatives do not have the correct velocity scaling or the influence of the prop slipstream is not correctly captured. This is certainly an area where the flight model could be improved. Additionally, I think there’s an opportunity to add in the Corsair quirk of little roll with left rudder and nose drop as the current model is quite symmetric (albeit maybe somewhat visible in the bottom left plot). Figure: Full left rudder (left) and right rudder (right) with ~50-60% aileron deflection. High-speed condition, 190 kts, 10,000 ft, 50% fuel. Figure: Full left rudder (left) and right rudder (right) with ~50-60% aileron deflection. Landing configuration (gear + flaps 40), 110 kts, 10,000 ft, 50% fuel. Test 6: Roll Performance Full left/right aileron deflections were used to assess roll rates for a 1-G, full 360 deg roll. As with most other tests, this one was flown at 10,000 ft, and ~200-220 kts indicated. This test was also repeated in the landing configuration at ~100 kts with full flaps and landing gear deployed. Obviously, a full 360 deg roll would be inappropriate with full flaps and gear, so the test was terminated at 90 deg of bank. At high speed, the aircraft needed full continuous power, and only ~28” manifold pressure in the landing configuration. A follow-on test of “rolling under G” was performed by executing the same high-speed maneuver with a steady 3-G load on the airframe (sort of a barrel roll I guess). The pilot reports indicate a significant reduction in roll performance under load with the Corsair giving up ~26-38% of its 1-G roll rate. Of note, these tests involved a 180 deg roll, not the full 360 used for 1-G testing. Data for all tests used the time to perform the complete roll in lieu of instantaneous roll rate data which is often much higher. Discussion: The table below highlights the difference in roll rates at high and low speed for the FG-1D and DCS F4U. Measured roll rates for the DCS F4U align reasonably well at high speed for the left-hand rolls. However, as is obvious from the data, the right-hand turning capability is off the mark. Low speed performance is symmetric, but slow. This again is a straightforward fix in the flight model, and I hope it makes its way into the next update. The accelerated data should be taken with a massive grain of salt as it is quite pilot dependent and holding a 3G turn without using your bottom as a G-indicator is difficult to say the least. I would appreciate community feedback on your numbers for this maneuver. Roll Performance FG-1D DCS F4U Right (high speed) 4.5 s (81 deg/s) 5.4 s (66 deg/s) Left (high speed) 4.9 s (73 deg/s) 5.1 s (70 deg/s) Right (low speed) 2.3-4 s (38 deg/s) 2.9 s (31 deg/s) Left (low speed) 2.3-4 s (38 deg/s) 2.8 s (32 deg/s) Right 180 deg (3G high speed) 3.1 s (58 deg/s) 6.1s (30 deg/s) Left 180 deg (3G high speed) 3.7 s (49 deg/s) 5.4s (33 deg/s) Test 7: Dynamic Stability I’ve seen quite a bit of chatter about the rudder authority and “wagging” (aka Dutch roll) of the F4U online, so I was particularly interested in assessing the directional dynamic response. Pilot reports indicate that all aircraft were deadbeat (aka, no overshoot) in the roll and pitch axes, and that the Corsair was notable for its pronounced Dutch roll. How I did it: Dynamic stability tests should be made with relatively small control inputs so as not to significantly alter the aircraft’s speed or altitude. I used either singlets (rapid fore/aft or side) motions to induce oscillations and noted any overshoot in the short-period, or oscillation in the long-period modes. Discussion: The pitch and roll axes were well behaved with little overshoot and no noticeable oscillation. The pitch axis is quite sensitive, but pilot reports indicate that it had the lightest control force gradient (stick force per G) of all aircraft tested. I cannot really say for sure, but it’s plausible that we need to fly it more like an Extra 300 and less like a P-47, so go light on the controls. Perhaps. The rudder control, on the other hand, does show substantially lower damping than indicated by the test pilots. They noted the worst case was three overshoots before the oscillation was damped. In my tests, I was routinely experiencing 6-8 (see plot below) with corresponding lower amplitude, but higher damping oscillations in roll. Again, from a flight model perspective this is a relatively easy fix (C_N_β anyone?), so I hope it too is incorporated in future updates. Test 8: Dive Test This test can also give some indication of the excess power/drag behavior of the aircraft, and how much trim control is necessary to compensate for speed buildup. This test is initiated at 10,000 ft MSL and ~100 kts, followed by a -1G pushover to a 30 deg dive and applying full METO power. Recovery is initiated at 5,000 ft noting the max speed at pullout. The pilot reports indicate that the Corsair had high rudder forces requiring retrimming during the dive. Discussion: From the table below, the DCS F4U is not far off the mark in the dive test. Starting at 100 kts, it matched the test aircraft to within 7 kts passing through 5,000 ft. Of note, my dive angle was slightly higher with an average of ~34 deg. I used the gunsight to estimate the angle, but precise control is tricky without some sort of digital readout. Of note, the aircraft does require increased rudder deflection as the speed builds and is relatively easy to trim as indicated by the pilot reports. This indicates again that the excess power and drag characteristics of the airframe are mismatched as the dive time is significantly faster than the measured data. As with the level acceleration, this seems to point to a mischaracterization of the thrust and/or drag at low to medium speeds. That being said, the required rudder trim at different airspeeds is probably correctly modeled. Dive Test FG-1D DCS F4U Start Speed 100 kts 100 kts Max Speed 348 kts 341 kts Time 32 sec 23 sec Conclusion: In summary, I think we have a wonderful start at one of my favorite aircraft. I hope Magnitude 3 will continue to develop the module and address some of the flight model issues that make the Corsair unique and a challenge to extract maximum performance. Specifically, I see the following issues that could use a bit of tweaking: Takeoff: Find a better pilot . Climbs: Reasonable agreement, engine power may be slightly overpredicted Level Accelerations: Tune the low-medium speed thrust and drag model to better approximate measured accelerations. Stalls: Uncoordinated stalls seem to always break left; this should not happen. Clean, power-off stall is too slow. Static Directional Stability: Low-speed rudder sensitivity too high, high-speed just about right with 70% saturation. Incorporate Corsair pitch quirk with left rudder and tune roll coupling. Roll: Resolve the left/right disparity in roll performance. Dynamic Stability: Directional damping needs to be increased to match the three-overshoot oscillation noted in flight test. Dive Test: As noted with the level accelerations, tuning of the thrust and drag models are needed to better match available data. I would like to repeat many of these tests with full fuel to further explore the flight model and ascertain if any of the noted discrepancies persist in a heavier configuration. I am also exploring sustained and instantaneous turn data, but it is somewhat complicated by scatter and self-imposed structural limits in the flight test data. I would greatly appreciate any constructive feedback and additional references that may have been used in developing the flight model to augment this analysis.

Heatblur Discord.

https://www.digitalcombatsimulator.com/en/news/changelog/release/2.9.18.12899/ DCS Core Fixed: CTD when landing on a carrier with no radio communication. Scripting API. dostring_in default behaviour has been returned to the state before last patch, after initial feedback and issues with single player campaigns. We are evaluating feedback for future change. DCS: F-16C Viper by Eaglе Dynamics Fixed: F16C Crash F16C.dll. DCS: AH-64D by Eagle Dynamics Fixed: Crash when using George CPG.

Well, as I wrote in my post which @Wing linked to (I really appreciate all the positive attention my post has gotten from the DCS community), there are so many systems which are either bugged or completely missing, which are not mentioned in the roadmap. 95% of all the things I mentioned in my post are not DCS core features, but rather specific to the F-16C. Just to pick the most glaring example in my post, which I put at the top for that exact reason: we do not have a damage model. Detaching wings and control surfaces, fuel leaks, and pilot death. That's pretty much the only damage which is simulated in the DCS F-16C. This is in stark contrast to other DCS products where almost every individual subsystem can actually fail due to combat damage, but for some reason, this was never implemented in the DCS F-16C, even though it was advertised as a feature on the product page. In fact, here are the 3 top listed "Key Features" on the DCS F-16C product page: Authentic fly-by-wire Flight Control System (FCS). The most realistic model of the F-16C imaginable, down to each bolt and flake of paint, animated controls surfaces, lights, damage model, and landing gear. Detailed simulation of the Viper’s engines, fuel, electrical, hydraulic, comms, lighting and emergency systems and many more. None of these bullet points have been fulfilled, and they are not mentioned in the roadmap. Does this mean that the items mentioned on the DCS product page are not what customers can actually expect at full release? Because that looks a lot like false advertising in my eyes. And if ED intends on rectifying many of the issues I listed in my post, plus many of the issues I didn't mention in my post, why are they not mentioned in the DCS F-16C roadmap? And why can't these issues be fixed without forcing the DCS F-16C out of early access prematurely? Having the DCS F-16C pushed out of early access kind of implies that all the "Key Features" on the product page are included in the product, does it not? It will be extremely misleading to potential customers who read the product page and believe that they will get all the listed "Key Features" as the DCS F-16C would, at least in name, be out of early access? Not to mention all the people who bought the DCS F-16C over the last 5 years in good faith, assuming that the "Key Features" listed on the product page would actually be featured in the final product. As I finished off my linked post by asking, is this the new baseline we can expect from ED products, if the DCS F-16C is released in its current state + Sniper ATP? I don't know if you actually fly the DCS F-16C anything in your spare time, but to be completely honest with you, it really is in a sorry state, and progress has been moving at a snails pace for years now. Out of all the issues which I mentioned in my over a year old post now, pretty much nothing has been rectified. I don't know why I'd believe any of that would change after early access is over for this product?

Gulf Guardian Part I Download: https://www.digitalcombatsimulator.com/en/files/3345527/ Hello! I've finally released Gulf Guardian Part I into the User Files. Experience the full spectrum F-4E operations, from high-altitude Combat Air Patrols (CAP) to daring low-level bomb runs. You'll face intense challenges, including defending civilian tanker traffic whilst under restrictive rules of engagement to executing precise low-level navigation to hit your time over target. Do you have what it takes to master the mighty Phantom? Prepare for unparalleled immersion with hundreds of custom voice-overs, dozens of unique voice actors, and meticulously crafted scripts and scenarios that bring each of the 5 missions to life. ************** There is extensive documentation included in the .zip file, so make sure you read it carefully. Most frequently asked questions can be answered in the README pdf. Having said that, please feel free to "@" me here with any questions or comments, I'll be happy to answer them.

COMING SOON In this DCS: F-16C Viper video, we’ll discuss the basic operation of the AN/AAQ-33 Advanced Targeting Pod, or ATP in this video. While we’ve had a targeting pod for our Viper for quite some time, it has inaccuracies and was more a mash-up of LANTIRN and Litening pods that we’ll continue to offer with our Viper. The ATP, however, is quite accurate and based on a US Viper circa 2007. While much of the ATP will have commonality with the existing targeting pod, it has distinct differences like Multi-Target Track, TV and infrared camera picture in picture, extended range image processing, an infrared pointer, and more advanced air-to-air features. In later videos, we’ll review these more advanced features. Please note that all HOTAS commands can be found using the SEARCH command in the Input Manager based on the input names used in the video. NOTE 1: Upon completing a couple more Viper and F/A-18C videos, general DCS update videos will continue. NOTE 2: This targeting pod has a much common name, but it is trademarked. NOTE 3: Point track doesn't require a long press of TMS Forward, rather I find it works best for me. When you press TMS Forward, it will enter AREA track while held; and then upon release of TMS Forward, regardless of duration of press, the pod will attempt to establish a POINT track but may stay in AREA if POINT isn't possible. NOTE 4: Until recently, there was an issue where if MIDS was enabled before the GPS had fully initialized and gained timing signals (GPS SYSTEM displayed on the TIME DED page), the MIDS wouldn't select GPS time automatically for its timing reference so it could achieve FINE sync. However, we have changed it so that the DLNK selects GPS by default now as soon as GPS time is available, so it doesn't matter. So, you can now enable GPS and MIDS immediately after getting on engine power, and the MIDS will self-initialize as needed when the INS is aligned and GPS timing is achieved. NOTE 5: DTOS is not valid for Snowplow, only CCRP and LADD for the bombing modes. Full video Text:

Baltic Dragon, as above, started developing training missions for C-130J module. btw.

Dont get me wrong, I still have a blast with the module. But I believe its fair to keep in mind all that we are still missing for the DCS F-16C. A great summary was posted back in 2024, then this topic was locked: TLDR Version: Major Missing/Incomplete Systems Damage Model – Basically nonexistent beyond wings/fuel leaks. No combat system damage., Pilot Fault List (PFL) / Maintenance Fault List (MFL) – No proper fault reporting or error messages., Steerpoints & Navigation – Missing SEAD steerpoints, threat points, proper CRUS TOS behavior., airspace navaids ect. Digital Terrain System (DTS) – Entirely absent. No PGCAS, TRN, or digital terrain awareness., ECM – Ineffective jamming. No control over bands, poor logic, no realistic jamming effects., Combat Capability Gaps SEAD – Broken ECM, no HARM DL/TI/GS modes, no emitter memory, bad HAD integration., RWR (AN/ALR-56M) – Incorrect symbology. No threat priority, no missile distance cues., A/A Radar – No COAST mode, over-sensitive to notching, STT is unreliable, broken HAFUs., ect A/G Radar & Weapons – Broken radar mapping. JDAM/JSOW/GBU-24 logic still incomplete or missing. CCIP bombing is off. Some weapons not implemented at all., Other Major Issues Lighting – Poor NVG compatibility. Flood lights weak or missing. Night ops are frustrating., Textures – Cockpit (behind ejection seat not modelled) and external textures are low quality. Custom liveries have had to pick up the slack... Missing panels, details, etc., Tankers/Refueling – No boom physics. Poor lighting. No feedback from boom ops. TACAN logic is wrong., Documentation – Manual is outdated, often incorrect. Leads to confusion and misinformation., "Jealousy" Issues (Things Other Modules Have) No ARC-210 radio, HSD Expanded Data, IFF, or HAVE QUICK — all of which are present in the F/A-18C, A-10C, F-15E, etc., No L16 Mission Assignment, which is present in M-2000C and applicable to this jet., Many of these are simple DED page updates and already exist in other modules.

Hi, I have been working to finish this bad boy here. It's working, basic systems, cockpit, most instruments, and basic weaponary It does an EFM and curves adjusted to be close to the Vampire, work in progress Download link soon

Very true. From an outsider's perspective is seems that for both companies the best outcome would be to continue working together, sell more products, keep customers happy. Yet here we are. Razbam needs to go find other business venues, while ED is only starting to feel the brunt of customer dissatisfaction. Just imagine what will happen when they'll actually have to remove those modules from the game going forward. What that initially presented itself as gross miscommunication between the two parties, has spiralled to a point when the best outcome we can realistically hope for is that one company leaves DCS ecosystem and ED takes over barely maintaining the existing modules? Something that Chizh and other ED developers on the Russian side of the forum initially dismissed? Yay. Well done ED & Razbam, you've killed most of my "passion and support" for the game. Gone are the days of me buying more modules just to support DCS as a whole. Ah well, more time and money left to spend on other things.

No discussion here. DCS needs good, scalable and easy to maintain security. In the past, I have recommended a couple of approaches in these forums how, for example, DCS could easily sandbox (better: sidestep) the lfs 'sanitize' issue by allowing a controlled, sandboxed 'writeString()' method that saves a string to a mission without having to 'de-sanitize' DCS (and compromise security). It was never followed up on. Pity. Instead we got the 'save mission' system that simply doesn't work, solves no problem at all, lfs still needs to be de-sanitized using a really, really bad 'unlock this for everyone' approach, just like this approach for dostring_in(). And to truly underscore how bad things are, the two approaches to resolving related issues (security) aren't harmonized. To me this is indicative of deeper troubling issues at ED than merely a bad IT security design team. The problem is that this new 'enhanced security' is, as implemented now, utter garbage; an inept, heavy-handed approach that will lead to LESS security. Why? Because soon (if they haven't already) videos and article will appear that tell you how to 'fix DCS' when all these "attempt to call field dostring_in" errors pop up in-mission. Invariably they will tell you to 'simply place this autoexec.cfg here, and you are done'. Because of the hare-brained one-size-fits-all approach, now the entirety of DCS is open, for every mission (not to mention providing a new attack vector through a malicious autoexec.cfg that is provided by the attacker in the video). Anyone with merely passing working experience in security can tell you: this approach is bad, much worse than not doing anything. So my opinion: this 'security' design is utterly inept, and it results in REDUCING security because everyone will bypass this 'security' for their comfort. Its like putting a fantastically complicated lock on your front door. Because it inconveniences everyone, they just keep it unlocked, opening the door for anyone. Is that improved security? A better design would allow per-mission sandboxing. There a billions of possible approaches: put the mission in a folder /insecure, and if it is in there, use the settings screen in DCS to regulate what is allowed (and yeah, lfs and io should be in there too). Better yet: have a GUI for that allows players to drag missions/directories into. Any mission in there is allowed risky stuff (configured by the GUI). Simple, and it does not take a lot of talent to implement. I'm not saying that above is good security design. Far from it. I'm merely saying that it's better by orders of magnitude than the current, inept design. What deeply troubles me is the fact that something this badly designed has made it past the design stage. What angers me is that it made made it into production. ED - you have a serious quality issue. Cheap, badly thought out code like this should never make it to the customer. This is really, really bad, ED. Please fix it. And please, if you don't have the talent, I'm sure there is ample talent in the community to help you out. Just ask.

This is atrocious -- I am severely disappointed and aghast. I feel that you (ED and their community managers) could have announced this change more than 24 hours in advance (6 months would have been a better time frame), and perhaps solicited feedback from the community -- because the way that you (ED) chose to implement this sandbox protection scheme is a 1980's design. "autexec.cfg" - are you frigging kidding me? Doesn't anyone at ED understand modern UX and or UI design? Why use such an obsolete and user hostile one-size-fits-all scheme when it would be so much better to build a "sandbox on/off" switch into DCS proper, and then add a simple UI that allow users to add folders to an 'allow unsafe' box that automatically allows unsafe invocations for any mission inside? Users could drag folders/directories and/or missions into the box and - boom! - they allow unsafe invocations. Designing this is (or should be to your talent) near-trivial (I did interface stuff like that in 2 hours -- 2002, on a Mac in XCode!), and a so much better approach for users who grew up with a Mouse. I feel that this new 'design' of yours is unworthy of you, and it feels like such a blatant slap into all of your content creators' face that I am deeply saddened to see how you simply (and callously) implement a far-reaching change like this without ever feeling the need to consult your community and contributors. Are we that worthless to you? That new 'feature' of yours kills any mission that uses net.dostringIn(). You do realise that mission scripters resort to doscript_in because DCS's mission scripting environment requires this to circumvent a bad flaw in MSE's design, do you? This means that any mission today that is sufficiently advanced will stop to work and require that unsafe patch, which will probably result in most DCS installs being unsafe. The exact opposite of security - likely a complete failure of what you set out to do. Why, why, why did you not try to sound out this change with those who spent lots of time creating missions for your product? I would have expected more from you, ED. For the record, can I request that you. or someone from ED, elaborate if you agree that this is merely a coarse stop-gap and that you do have a real, user-accessible and well thought-out future version waiting in the wings? Because this? This is bad design. Will we get a real 'sandbox' security interface for DCS? I don's feel like updating the 50 (?) missions I put on Userfiles, so maybe they run, maybe not. 9 out of the last 10 missions I published there no longer work and now require unsafe invocations. So be it. I cannot be bothered to care if you, dear ED, can't be bothered to engage with your community either. What a mess. I hope that you will fix it soon. Will you, ED?

Mi-28N/E for DCS World! Codename : Night Hunter Mod development thread Hello folks, earlier version of Mi-28N/E Mod for DCS: Requirement : DCS Ka-50 3 Module Work in Progress Full inside 3D cockpit EFM and ASM INSTALLATION: Unzip in to into "...\Saved Games\DCS\Mods\aircraft". “Saved Games” folder is usually found inside “C:\Users\[[USERNAME]]\”. If "mods" & "aircraft" folders are missing, make them. NB: For now the MOD use Ka-50 Cockpit and EFM. Any Contributions is welcome. Release : https://drive.google.com/file/d/1dYk6yVulthlYc9vntPohFE746r1XkJyc/view?usp=sharing https://drive.google.com/file/d/19VgRDe42Au8ZdoFjP4nho94r6yLK-hFQ/view?usp=sharing https://drive.google.com/file/d/1N2BDIedBURAPG16IDFxEic4HTWCL4ICQ/view?usp=sharing Screenshots : null

Thanks! So, yeah, the F-4E Phantom II guide is now live! https://chucksguides.com/aircraft/dcs/f-4e/

This is very disturbing. An agreement was reached last year and this is the first time it has been mentioned? But there are no details of the agreement, and clearly work has not resumed on any of the Razbam modules and ED still does not have the source code so they cannot promise how long they will be able to support them. So this "agreement" clearly did the end users no good whatsoever. ED is just continuing to string us along? We get the crappy end of the stick because ED is taking care of ED, Razbam is taking care of RazBam, and no one is representing the consumer. This is the Hawk situation all over, after ED promised us it would never happen again. I guess they are counting on us all having only short term memory. This started in Spring of 2024. Normally I buy almost every module that comes out, especially helicopters. Because of this cluster, I have not purchased the Kiowa, the Chinook, or the Corsair. The only thing I have bought is the Germany Map. And its probably going to stay that way. This is not good business. There is a saying in business that if you take care of your customers they will take care of you. And if you don't......I have supported ED for many years, since the LOMAC days, and I have bought many modules and packs that I wasn't really interested in just to support the continued development of DCS. I'm not feeling that generous anymore if this is the way we will be treated.

More work on simple system implementation. I found a workaround for RWR and avionics power. Also, I finally figured out the sound system.

Hi all, Completed my 3000 mile move and got my sim rig back in business. Time for some updates! 7/1/2025 - Updated to version 17 -NEW: Modded cirrus shader to use a texture array. This increased the number of unique cirrus cloud types from 4 to 16. You will notice many new variations of cirrus while flying your missions now. All cirrus textures were created by me from hi resolution photos of real cirrus clouds. -Tweaked several cloud presets, improving the look of Low level stratus, Altostratus and Altocumulus cloud presets - Included 4 new presets for heavy broken cumulus clouds. These are the Scattered Showers presets with no rain.

No burnouts for me mate, just very limited time to deal with the daily life chores and even more limited for DCS modding, RL keeps getting in the way, meanwhile i have @Petr005 working on the long awaited changes for the 3D model, extensive cockpit object modeling, to bring the details to a higher level.

This all is really strange. All the time i thought this "There was a settlement signed by everyone" thing was just the "normal" trash talk by Razbam. Now it's confirmed to be true. Ok, that doesn't mean anything. I'm just a bit worried about the fact that it was already signed at least 7 or maybe even 8 month ago and nothing changed. One might think that a settlement means that both parties agree to something and stick to it.... How can you sign a settlement and then.... what? Pull back and just don't stick to the conditions? And how can you still call it a settlement? Already signed end of 2024? Was it by coincidence at the same time when Kate Perederko wrote these "MiG-23 will be a thing" and "Don't worry about your F-15. The Strike Eagle will see developement - this way or the other..." stuff? But what really, really disappoints me is the fact that we went from: "We will do our best to keep the RB modules working as they are" through: "We will do our best to keep the RB modules working until DCS 2.9x to: "we will keep an older version of DCS available for those that still want to use those IF this dispute is not solved." It also pi**es me off that we went from: "We set up a new contract with the third party devs in order to avoid another disaster like with the Hawk." through: "What happened to the Hawk will not happen to the RB modules except from the SE since the other modules are already out of EA." to: ....yeah - same as above - keeping an older version for the RB modules availabe.... so in the future we might need a third DCS install to play with all our modules we have paid for? I was always hoping for a post in this thread about a settlement and the continuation of the cooperation between ED and RB. But now i think there will be the day when the announcement is just like: "We are pleased to announce that we will release DCS 3.0 with the next update. All RB users please make sure to make a copy of the current version in order to keep your RB modules working...." That's all weird - really weird. To me it is obvious that ED expects to loose all 4 RB modules in DCS. Great, well done guys, well done (both parties). Get your stuff together!!

So resuming. The VEAO issue that will not happen again is hapenning again multiplied 4 times. No refunds for anything except F-15E in ED credits ( no steam refunds at all ). Double DCS Installation to be able to fly RB modules. From 2.10.X-3.X RB modules are out of DCS All assets from RB gone. No Tarawa. No more basket refuel for any module except the S-3B Viking or the IL-78 ( DCS Core doesnt have any blue basket tanker apart from the Viking if RB assets are removed ) Missing anything else? Ahh ,yes, we can still wait and hope for a positive outcome.

In this DCS: F-16C Viper video, we’ll continue from the earlier basic functionality video of the AN/AAQ-33 Advanced Targeting Pod to discuss some of the more advanced and unique capabilities of the ATP like Extended Range (XR), Maverick handoff, Multi-Track (MT), Laser, Infrared Pointer (PTR), Laser Spot Track (LST), and air-to-air mode. NOTE 1: Later, we plan to add the MENU function that includes other PTR options and Fragmentation Ellipse settings. NOTE 2: This targeting pod has a much common name, but it is trademarked. NOTE 3: The ATP is not planned for the F/A-18C (USN/USMC) and A-10C II Suite 3 basis as it would be inaccurate for the versions of these aircraft we simulate. NOTE 4: At 13:53, I misspoke. Use Cage/Uncage to enable/disable LST via the HOTAS. Not the Enable button. NOTE 5: ATP MT detection range of aerial targets will greatly depend on the target type. For lower signature/small sized targets, NARO mode will work best compared to WIDE for larger targets/large signatures.

null

Hello, I finally finished the ACM. I used TS90MD servos to avoid screens as much as possible. ACM.mp4

Hi guys Here we go ! MSA GALLET LA-100 Helmet - Entirely made from 3D scans

@Ronin_Gaijin I have spoken to the team, we are planning the use of mobile RSBN beacons that can be placed on any terrain. thank you

Frustration among customers is growing, and it’s not hard to see why. For months now, all we’ve heard are vague reassurances: “We’re doing our best,” “We hope it works out,” “The modules still function.” But those words are starting to ring hollow. People aren’t looking for vague promises anymore ... they’re asking for real action. Empty hope doesn’t fix the situation, and every day that passes without a resolution further damages the community’s trust in Eagle Dynamics. This isn’t about drama... it’s about accountability. We’re not just going to quietly accept being left in this mess. If ED truly values its players, it’s time to step up and deal with this properly. Hope is not a solution. Silence is not support. The longer this drags on, the harder it becomes to believe that anything will actually be done.

After the drama with the Hawk you promised that from now on you would own the source code of all third-party modules so that this can never happen again. Obviously that was a lie.

I have no problem with the changes in terms of security for the general DCS user. I have a HUGE problem with this being just dropped on all of us who run or help manage servers with no notice. This should have been a preview build weeks (preferably months) in advance for us to be able to make changes and be ready for. Instead we're stuck with our players going "why isn't the server updated" and we have to tell them "ED broke stuff again, we will get to it when we can."

We now have built a first release candidate for Vietnam War Vessels 2.0.0. The renaming of all the folders to start with [VWV] primarily mandated the change in version numbers. But we also have two exciting new assets: USS Enterprise '66 from James - the first nuclear driven carrier will join the fleet in 2.0.0 A-37 Dragonfly from Hawkeye60, an iconic US and South Vietnamese aircraft of the war We also have improved a few other assets and completely swapped the H-2 Seasprite model. There's also a bunch of items we would have loved to push to 2.0.0, but they are not ready yet. Namely the MiG-21PFM and the RF-101B Voodoo. Stay tuned for them at a later date!

Hey there. We have just completed Combat-Tree, it will be available with the next build of the Phantom. Cheers https://f4.manuals.heatblur.se/systems/identification_systems.html#interrogator-systems

Good morning pilots! Continuing our long-standing tradition of long overdue news updates, we invite you to read our latest post! https://magnitude-3.com/2025/07/04/2025-summer-update/

Hey Jack, My back is recovering pretty good. However, I'm careful not to bend over a certain way or lift heavy objects. I'm not there yet. Thanks for asking. I have to use comfortable seat cushions and a heated vest to help me get through the day. Of course, meds help as well. It's been life-changing. Thanks Jack.

My friends. It just must be said, so I'll say it: DCS has never looked more beautiful and run so well on my modest (by DCS standards) system! Well done to the whole team! With so many modules and features, both current and upcoming, it's easy to miss the incredible progress they've made over the past several years. Seriously, I was flying around the Iraq map on a mission at sunset the other day... Absolutely stunning! Thanks for all the work, team! You are the golden age of military flight sim, PERIOD.

TBH, the fact that I purchased a number of modules (Harrier, Mirage, Mudhen, South America Map) from ED (yes, I purchased from ED - I know that because that's what the bill tells me who collected my payment) seem to have fallen out of service (some even before fulfilling their "Early Access" promise) has left a very bitter taste in my mouth. It's not as if this is the first time; ED has left me holding the bag before when I purchased the Hawk from them. I don't give a rat's behind for lame excuses or sob stories about some contractor acting up. If a company can't keep their suppliers in line, maybe they should take a good, hard look at their processes and they way they conduct business . Please, ED, get your house in order and provide relief for your customers.

Good Morning, everyone, I'm sorry I've been away for so long. I've been working in the background on random mods, but nothing really serious. I'm healing well, but i haven't gotten my mind back into full-time modeling. Just taking it slow and easy. Life has taken over with family, so if you have kids, then you know what I mean. Thanks for all your concerns. Sierra99, it's funny you ask about the AN/SPS-52 Radar. I was just working on that radar for the Adams-class destroyer. ---Yes, it is possible. I say that because vehicle and ship scripting are interchangeable. Looks like they used vehicle code for the static object. Just looking at it. The radar code can probably be swapped out with the radar code from the Tarawa or any other ship's radar. --Sorry for the late response. The latest mod I was working on was the USNS John Lewis Class Support ship. She's almost done. Once finished i will release her but now sure how at the moment. Please read below!!! ***** One thing I wanted to bring to your attention is that I have taken down my Admiral189 DCS World Mods website because the mods are being downloaded, ripped, and sold online. I honestly don't think there's a way around this as long as EDs .edm mod file is not secure. I will keep you all posted. Thanks for your patience. **************

Yeah, this is bugging me. We were assured something like the Hawk wouldn't occur again, and now we're staring at something far worse. FAR worse.

Such a great document, congrats Chuck! We are very happy to promote the content in the Phantom. It has been added to the frontpage of the official manual, to the modules Doc folder and to the Virtual Browser (RCTRL+V) for viewing it in-game as well. Available with the next Phantom build