Leaderboard

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.

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.

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?

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.

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.

With Great Contribution of @flanker78. good advance on W IP ASM, big work Comrade ...

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

25 July 2025 Dear Fighter Pilots, Partners and Friends, In light of the very successful recent sale, we have launched a mid week special with deals for many of our most popular aircraft, terrains, campaigns and add-ons, so if you haven’t already taken advantage of the summer sale, head over to our Shop and Steam and get the last of our summer deals. Thank you! Enjoy! On Wednesday, we rolled out the update we previewed in last week’s newsletter, and your feedback on highly anticipated items including the new F-16C Advanced Targeting Pod, F/A-18 Terrain Avoidance mode, and new AH-64D “George” AI commands has been greatly appreciated. Please make sure you update your DCS installation to benefit from all the recent fixes and enhancements. Read the full changelog. Among the many flight demonstration teams, few capture the imagination as well as the United States Navy’s Blue Angels. This week, we’re saluting the Digital Blue Angels; a dedicated troupe of DCS aviators who mirror the precision, pride, and discipline of the real demonstration team. If you’ve ever felt a surge of adrenaline watching blue-and-gold F/A-18s carve perfect diamonds overhead, then join their Discord now! In response to recent comments and questions made by Razbam Simulations, its proxies and/or external developers, Eagle Dynamics confirms that it signed a settlement agreement with Razbam at the end of 2024 to put an end to the existing disputes and that such agreement also provides for a strict confidentiality requirement that prevents Eagle Dynamics from disclosing further information. Eagle Dynamics can, however, confirm that Razbam instructed Eagle Dynamics to cease selling the modules developed by Razbam and its independent developers. All modules continue to function ‘as is’ and despite not receiving any access to source codes or cooperation from Razbam and its external developers, Eagle Dynamics will do its best to ensure that these modules continue to function in 2.9.X. We are still hoping to be able to implement the settlement agreement and to find a satisfactory outcome to the current situation, in the best interests of our valued community. Thank you for your passion and support. Yours sincerely, Eagle Dynamics MidWeek Deals Even more savings! For just a few more days, take advantage of our great deals! The DCS MidWeek Sale will end on the 28th of July at 15:00 GMT, so don’t miss, and check out what’s up for grabs below: Modules at 50% off Fixed Wing DCS: A-10A Warthog DCS: A-10C II Tank Killer DCS: C-101 Aviojet DCS: Christen Eagle II DCS: Bf 109 K-4 Kurfurst DCS: F-86F Sabre DCS: I-16 DCS: Fw 190 A-8 DCS: Fw 190 D-9 Dora DCS: L-39 Albatros DCS: MB-339 DCS: MiG-15bis DCS: Mosquito DCS: MiG-21bis DCS: P-47D Thunderbolt DCS: P-51D Mustang DCS: Spitfire LF Mk. IX DCS: Yak-52 F-15C Flaming Cliffs MiG-29 Flaming Cliffs Su-25 Flaming Cliffs Su-27 Flaming Cliffs Su-33 Flaming Cliffs Helicopters DCS: AH-64D DCS: Black Shark 3 DCS: Mi-24P Hind DCS: Mi-8MTV2 Magnificent Eight DCS: SA342 Gazelle DCS: UH-1H Huey Terrains DCS: Nevada DCS: Persian Gulf DCS: The Channel Other DCS: Combined Arms DCS: NS 430 Navigation System for SA432 Cockpit DCS: NS 430 Navigation System DCS: NS 430 Navigation System for C-101EB DCS: NS 430 Navigation System for C-101СС DCS: NS 430 Navigation System for L-39С Cockpit DCS: NS 430 Navigation System for Mi-8MTV2 Cockpit DCS: WWII Assets Pack Campaigns DCS: A-10C 16-2 Red Flag Campaign DCS: A-10C Advanced Aircraft Training Qualification Campaign DCS: A-10C Basic Flight Training Campaign DCS: A-10C Tactical Training Qualification Campaign DCS: A-10C Stone Shield Campaign DCS: AH-64D MAD campaign DCS: AV-8B Hormuz Freedom Campaign DCS: Black Shark 2 Republic Campaign DCS: Combined Arms: Frontlines Georgia Campaign DCS: F-15C Aggressors Air Combat Maneuvering Campaign DCS: F-15C Aggressors BFM Campaign DCS: F-15C 16-2 Red Flag Campaign DCS: F-16C Dragon's Fury Campaign DCS: F-16C Red Flag 21-1 Campaign DCS: F-5E Aggressors Air Combat Maneuver Campaign DCS: F-5E Aggressors Basic Fighter Maneuvers Campaign DCS: F-5E Black Sea Resolve '79 Campaign DCS: F/A-18C Aggressors BFM Campaign DCS: F/A-18C Hornet Inherent Resolve Campaign DCS: JF-17 MAD campaign DCS: Ka-50 2 Pandemic Campaign DCS: L-39 Albatros: Kursant Campaign DCS: MAD Black Shark Campaign DCS: MAD Campaign DCS: Mi-8MTV2 and Ka-50: Memory of a Hero Campaign DCS: Mi-8MTV2 Crew Part 1 Campaign DCS: Mi-8MTV2 Oilfield Campaign DCS: Mi-8MTV2 The Border Campaign DCS: Mig-21bis Battle of Krasnodar Campaign DCS: Mig-21bis Constant Peg DCS: P-51D Charnwood Campaign DCS: P-51D High Stakes Campaign DCS: Spitfire LF Mk. IX Operation Epsom Campaign DCS: The Museum Relic Campaign DCS: Su-27 The Ultimate Argument Campaign DCS: UH-1H The Last Show DCS: UH-1H Worlds Apart - Spring 2025 Campaign Modules at 40% off Fixed Wing DCS: F-16C Viper DCS: F/A-18C Hornet Other DCS: Supercarrier Modules at 30% off Fixed Wing DCS: AJS-37 Viggen DCS: F-86F FC DCS: JF-17 Thunder DCS: Mig-15bis FC Terrains DCS: Kola DCS: Syria Campaigns DCS: AH-64D Outpost Campaign DCS: AV-8B Sky Warrior Campaign DCS: F/A-18C Operation Pontus Campaign DCS: Mi-24P Outpost Campaign DCS: Mi-24P The Border Prequel Campaign DCS: UH-1H Argo Campaign DCS: UH-1H Worlds Apart Stormfront Campaign Modules at 25% off Fixed Wing DCS: F-14 Tomcat DCS: F-4E Phantom II Campaigns DCS: A-10C Iron Flag Part 1 Campaign DCS: A-10C Operation Persian Freedom Campaign DCS: AV-8B Kerman Campaign DCS: Bf 109 K-4 Jagdflieger Campaign DCS: F-14 Speed & Angels Campaign DCS: F-14A Fear the Bones Campaign DCS: F-14A Zone 5 Campaign DCS: F-14B Operation Sandworm DCS: F-15C The Georgian War Сampaign DCS: F-16C Arctic Thunder Campaign DCS: F-16C First In Weasels Over Syria Campaign DCS: F-16C Last Out Weasels over Syria II Campaign DCS: F-16C The Gamblers Campaign DCS: F-4 MIG Killers Campaign DCS: F-86F Hunters over the Yalu Campaign DCS: F/A-18C Arctic Thunder Campaign DCS: F/A-18C Flaming Sunrise DCS: F/A-18C Hornet - The Serpent's Head 2 Campaign DCS: F/A-18C Operation Cerberus North Campaign DCS: F/A-18C Operation Green Line DCS: F/A-18C Operation Mountain Breeze DCS: F/A-18C Persian Lion Campaign DCS: F/A-18C Persian Lion II Campaign DCS: F/A-18C Raven One Сampaign DCS: F/A-18C Raven One: Dominant Fury Campaign DCS: Fw 190 A-8 Horrido! Campaign DCS: M-2000C Red Flag Campaign DCS: Mosquito FB VI - V for Victory DCS: P-47D Wolfpack Campaign DCS: P-51D Debden Eagles Campaign DCS: P-51D: The Blue Nosed Bastards of Bodney Campaign DCS: Spitfire Beware! Beware! DCS: Spitfire IX The Big Show Campaign DCS: The Enemy Within 3.0 Campaign DCS: UH-1 Paradise Lost DCS: UH-1H Peacekeeper Lebanon Campaign Modules not on sale Fixed Wing DCS: F-5E FC DCS: F-5E Remastered DCS: F4U-1D Corsair Flaming Cliffs 2024 Helicopters DCS: CH-47F DCS: OH-58D Kiowa Warrior Terrains DCS: Afghanistan DCS: Afghanistan Southwest DCS: Cold War Germany DCS: Iraq DCS: Iraq North DCS: Marianas WWII DCS: Normandy 2.0 DCS: Sinai DCS: South Atlantic Campaigns DCS: A-10C Operation Agile Spear DCS: AH-64D The Four Horsemen Campaign DCS: F-4E Northern Defenders DCS: F-4E Red Flag 81-2 Campaign DCS: F/A-18C Rising Squall Campaign DCS: F/A-18C The Rampagers DCS: Mosquito FB IV Freeman's Folly DCS: P-47D Wolfpack II Overlord Upgrades DCS: Normandy 2.0 Upgrades DCS: A-10C II Tank Killer Upgrade DCS: Black Shark 3 Upgrade DCS: F-5E Remastered Upgrade DCS Update Summary DCS Core Some AI flight models such as the B-1B saw improved taxi and takeoff rotation characteristics, and both the B-1B and B-52H received more realistic long-range strike mission payloads. Mission builders may notice new and improved tool-tips and stability fixes, while mission creators receive enhanced a_do_script and a_do_file calls that pass arguments and return values. Spotting dots have been improved, voice-chat crashes have been stamped out, and we corrected warhead modelling for Mk-80 (and related GBUs) and M117 series of bombs that deliver a greater punch. Eagle Dynamics modules The DCS: F-16C Viper now features our first iteration of the AN/AAQ-33 Advanced Targeting Pod (ATP), and will exit early access following the end of the sale. Based on its roadmap, all planned early access features have now been delivered, but it will continue to be supported with additional features; the towed decoy, improved data modem, radar warning receiver handoff mode, and continued data transfer cartridge work. This is in parallel with continued bug fixing and tuning. We also recognize that there are some additional features that some customers desire, but those fall outside the stated scope of the product or would be inaccurate. The DCS: F/A-18C boasts the new Terrain Avoidance (TA) radar mode. For our helicopter buffs, the DCS: AH-64D now offers more advanced George AI Co-Pilot Gunner Commands! The DCS: Black Shark 3 includes new Instant Action missions for the Iraq map. Third Party modules The recently launched DCS: F4U-1D Corsair by Magnitude has received an impressive follow up with new art and Mission Editor functionality. The DCS: OH-58D Kiowa Warrior by Polychop received attention too and the DCS: JF-17 Thunder by Deka Ironworks got some needed fixes as well. Additionally, the DCS: Cold War Germany map by Ugra got its long awaited improved destruction models and Phase 1 enhancements! This update is now live so if you haven’t downloaded please do so and let us know how the changes feel in your cockpit. For a list of all changes, read the full changelog. Digital Blue Angels Community Spotlight Formed by flight-sim enthusiasts scattered across the United States, the Digital Blue Angels pour hundreds of practice hours into reproducing every break, roll, and formation change you’d see at a real-world airshow. Their goal is simple: Inspire our community by showcasing naval aviation at its finest. In the process, they honor the professionalism of the US Navy’s demonstration squadron. Flying the F/A-18C in DCS gives them the fidelity they need to nail the Blue Angels team’s graceful “Diamond 360” and the heart-stopping “Opposing Knife-Edge Pass” trademark maneuvers. If you’re a budding naval aviator, a Blue Angels super-fan, or just hunting for your next dose of inspiration, then you’ve been invited to join the Digital Blue Angels Discord! Thank you again for your passion and support, Yours sincerely,

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.

We have always had lots of sales, you are reading to much into it or to much reddit. DCS continues to grow and we continue to develop. thanks

Vietnam War Vessels 2.0.0 This release is a major update of the Vietnam War Vessels mod. With VWV 2.0.0 comes a new directory structure, where all assets have a [VWV] prefix in the folder name. This makes it necessary that you first uninstall the old Vietnam War Vessels 1.x.y completely. We welcome the USS Enterprise, CVAN-65, in its 1966 configuration, to the fleet. The first nuclear driven carrier has been derived from the modern USS Enterprise, and takes a place of its own now. The complete launch and parking system has been overhauled, leading to a hopefully more immersive experience. The second new addition to the mod is the A-37 Dragonfly. This iconic aircraft of the Vietnam War is now available for AI use within the virtual DCS sky. Please take a look at the Known Limitations below! Updates, Ships Knox class - FF icons are used instead of DD BB-62 New Jersey - CC map icon in use, better helicopter landing on the deck, new custom shell for main armament CVA Essex and Bon Homme Richard - model improvements, nick name as short display name for Bonnie Dick Many ships - sound updates to gun fire Updates, Planes A-1 Skyraider - split into A-1H (with bridle cat support) and AD-4 (without), add Napalm bombs from A-4E-C mod, add toilet bombs to all pylons, rework flight model to take off from Essex ‘44 with 70% loadout H-2 Seasprite - use of a new model, split into SH-2F, UH-2A, UH-2B, UH-2C classes MiG-21MF overhauled nose gear, support for RATO take-offs O-1 Bird Dog, add engine nozzle definition, Flight Model change for more realistic take-off RA-5C Vigilante - Flight Mode change, more lift at low speed Known Limitations CVA-31 Bon Homme Richard - Player controlled helicopters slightly move forward on the flight deck F-8 Crusader - Aircraft is intended as static and for limited AI operations - Player control is experimental at best, but largely untested and unsupported - Carrier launch and landing operations are not supported for player aircraft, only AI - Unknown how to drop bombs as player aircraft - Variable incidence wing is not enabled - Collision shell not reliable under player control - Nose wheel rotation disabled MiG-17F "Fresco-C" - Player control is almost untested and unsupported - Collision shell not reliable under player control - Damage susceptible when placed as static H-2 Seasprite - Wheels don't touch the ship deck - Landing gear is deployed multiple kilometers away from landing spot Fletcher Class Destroyers with FRAM II upgrade - Bridge and mast are WWII style RA-5C Vigilante - The plane is too large for regular parking spots, best to use as single plane on the runway MiG-21MF "Fishbed-C" - Textures are work in progress - Gear up location is pretty bad A-1 Skyraider - The new bridle disappears during launch - The precision of dropping Napalm is abysmal - Takes off like a spaceship from land - Tiny Tim rockets seem never to be launched A-37 Dragonfly - Flight model is raw and has not been tested much - Only one pilot ejects, ejection somewhat broken O-1 Bird Dog - The propeller blur is static CVAN-65 Enterprise - Catapult hookup spotty, sometimes planes start to drift - Parking spotty, some planes start to drift - Probable inability to sync INS when taking off cold - RA-5C and F-14 Tomcat slightly too large for safe aircraft operations when taxiing - The shoot power of the catapults seems insufficient at times - No support for night operations, e.g. no lights Download (Github): https://github.com/tspindler-cms/tetet-vwv/releases Alternative download (Google Drive): https://drive.google.com/drive/folders/16pUuupD08L36KnD6vDel5VRlmwwftX5o?usp=drive_link Enjoy, The Vietnam War Vessels team

By leaving out the fact that Razbam stopped development due to ED no longer paying them, you are being extremely misleading. Your conspiracy theory makes no sense at all anyway, since what would Razbam even be able to gain by blackmailing ED? It makes no sense. Do you really think that trying to deceive people is somehow helping your cause? And no, just because you write Factual Truth in bold and underlined, does not magically make that true. It just makes you seem like a crazy homeless person that thinks that the key to having their beliefs accepted is by putting it on a very big sign, rather than it actually making any sense.

They obviously can't say what they agreed to. Have people not seen legal agreements like this before? They generally severely restrict what anyone is legally able to say without blowing up the entire agreement, which would be a very stupid thing for ED to do.

nullnull

hi guys , With the precious help of HAGEN and holydays starting , the pit is on good tracks ! here are some pics !

The only thing we should focus on is that we gonna lose 200/250€ worth of modules because of their issues. All the people here talking about contracts, agreements, and guilt are just wasting their time.

They are quite easy to understand and you have described it fully. …which is still more than it should be and which creates insecurities that didn't exist and shouldn't exist. It's that simple. This is a bad solution, implemented hastily with no warning and seemingly no testing of value. The number of things it breaks for no gain is ridiculous. The workarounds create bigger problems than what initially existed and does the exact opposite of what was intended with this whole idea. Hell, even the OP gives a big red warning sign. The reason I say that you didn't do any testing is because you've managed to break SLmod for a number of people — probably other common and crucial mods that are used all over the place. This should have been an immediate discovery and show-stopper. I would suggest a two-step process: Hotfix-patch rollback. Do any of the things cfrag has suggested. Or see two posts above. This may seem drastic and contrary to how ED does anything, but trust me, the alterative is much much worse. That alternative would require them to, first thing tomorrow morning… At the top of the forums, the DCS website, the launcher, in the game main menu, and on every reddit, discord, and My Little Pony Online chatroom where they have any kind of social media presence, put out a warning sign in huge blinking letters that they have changed the security model in such a way that users may now be tricked into allowing remote code execution. In a very public post — not hidden away in this obscure “mission editor” corner of a forum that not many visit to begin with — document, in full, what the function does, how the different scopes work and what they affect, and under what circumstances each scope might allow for ACE. List and publicly endorse the minimalist exception rules for the 12 most common scenarios where you might want to allow dostring_in to work, from an end user perspective (eg if you want to use some of the products ED sells, or use userfiles of some kind), from a server perspective (how do you still allow common server mods to function, what are the caveats, how does it minimalisticly mesh with eg. shared moderation roles), from a coder perspective (what are the most common uses, what do these require in terms of exceptions, what are other more secure ways of doing the same thing). 36 cases in total, full documentation, full transparency of where, when, and how code (and in particular remote code) can be executed. Determine and clearly communicate which scopes and combinations should pretty much never be used because of what they open up. And in doing so, maybe just not allow that to begin with. Again, anything that creeps towards “remote…” should probably be stomped hard. Implement some kind of code signing so the end user can differentiate between trusted developers and random junk they find on the intenet. Congratulations, you are now Microsoft. Oh, it's just text files and there is no way to sign those…? You don't say… It's almost as if it has caused new problems. Implement a security tab in the game settings where this and related settings are made. Too many things are affected by this to just leave it as an obscure text file code injection — that just leaves option the ability to trick people into putting harmful code in there. If kept, the model need to be extended to not just be “these scopes are allowed use; these scopes are allowed access” but rather make it a proper model where you can decide, scope by scope, what is allowed. A full set of access control lists — congratulations, you're Microsoft again. This, once more, requires something a lot more complex than can be safely relegated to code in a cfg file. Rather, in the Security tab, these options can be explained to the user and particularly bad combinations can trigger warnings our outright blocks (here, at this level, is where it might be appropriate to allow overrides via cfg file edits). All that to make sure we don't get a slew of malicious code out there, combined with malicious suggestions for “solutions” that leave the client wide open. Again, the problem here, as others have mentioned, is that users will just be faced with an error box and go search for the first available solution. This will not be your clean three-line autoexec addition, but rather something far more malicious. ED's official answer and suggestion needs to be the first hit on every search engine, and anything that deviates from that should come with a huge warning that the player will notice. The information campaign needed to combat malicious use of this new security hole is immense. Let's just be kind and say that huge information campaigns are… not ED's forte.

Speculation presented as fact. Apparently they did sign a settlement agreement, so this is a lie. Very misleading statement given that ED doesn't seem to have paid Razbam, while you are insinuating that they did get the money and owe something in return. Hard to imagine a less deceiving way to write this. Again speculation. We don't know the contents of the contract. Given that Razbam have explicitly said that they will not do this, it seems very irresponsible to claim that this is fact. So there doesn't seem to be any factual truth to your entire post. It is just one big heap of misinformation.

I don't get it. We've got one side saying it's completely over, giving heads up on the situation throughout the conflict and giving a full on explanation to most important details of the agreements both past and the most recent one mentioned yesterday, being open to community questions and literally showing receipts for being ready to cooperate instantly and share the updates and escrow. The other side is hiding behind supposed confidentiality, dodging every single in-depth question and even deleting their own statements from social media, sharing messages that contradict each other and dropping their main claim which I don't think anyone believe by now with all that IP infringement trouble.

After what happened to VEAO this was the solution that ED gave at the time. For me this is not a opition, I'm not going to buy a single module again. I'm telling my friends not to buy from ED and to play another game. Find a better solution, I don't care who is responsible for this mess.

Today’s newsletter update is truly unbelievable. To say an agreement was reached but hasn’t been implemented, while saying “we can’t say any more”, with the context being that multiple forums say it hasn’t been implemented because ED hasn’t paid, is simply unreal.

Yeah, we are weighing what it will do for those that want optics simulated more accurately for the older TGPs, and others that want to keep the older TGPs the way they are. An option would be nice, but it could then snowball from there. So, we will weigh options. However, the optics of the AAQ-33 are accurate, and have no plans or need to adjust those. The most common issue we see with customer use of the AAQ-33 is not taking advantage of the NARO field of views, remembering to first stabilize in Point, Area, or INR, and then using XR processing.

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.

Wenn ich nichts übersehe, haben wir hier im deutschen Teil des Forums noch keinen Thread für allgemein wissenswerte Schnipsel, die nicht direkt mit DCS oder Luftfahrt zu tun haben, dabei zu interessant sind, um gänzlich unerwähnt zu bleiben, aber nicht interessant genug für einen eigenen Thread. Zum Auftakt gibt es die Empfehlung, die Nvidia-Treiber zu aktualisieren. https://www.heise.de/news/Sicherheitsupdates-Schadcode-Luecken-in-GPU-Treibern-von-Nvidia-geschlossen-10501190.html Nvidia hat in den neuesten Treibern teils kritische Sicherheitslücken geschlossen. Falls ihr eure Treiber von Hand aktualisiert, wäre jetzt ein guter Zeitpunkt für ein Update.

What logic is this? If you worked for a company and they stopped paying, would you keep working without pay until you lost your house, or would you try to find another job to prevent you from losing your house? And you ignore that there is supposed to be a settlement, that supposedly says that RB would work on the modules, but for some reason that agreement is no longer being accepted as valid. Yet we do not know all terms of the contract and to what extent each side followed it, so it is impossible to judge it on fact, although clearly, many people think that their bias is as good as facts. Pretending that you speak for others is another tick on the bingo card for someone who writes irrational things.

If true this is sad. Im a member of a virtual squad flying DCS since LOMAC times, most of us had 25 years flying this simulator and never have seen the reaction most of us are having. More than half of us are not buying anything else, part are just not flying anymore or moving to the "never said the name" simulator. People remaining still enjoy flying DCS together but loosing AGAIN valued modules that we fly on a daily basis is killing us as a Squad. Most people are not reading the forums here or playing MP, imagine when suddenly they lost 4 modules in a row. The magnitude of this cant be ignored. Someone need to do something.

Maybe its me but whoever at ED thinks about 3 DCS versions to be able to fly the Hawk, Razbam Modules and keep having updates beyond 2.9 is a fair solution... This is absurd at a biblical dimension. "Hey dear costumers, not a problem here, you can fly your favourite modules. Just keep 2.5.3 DCS, 2.9 DCS and 3.0 DCS version in your computer" Thanks for you passion and support. If this situation wasnt advertised false by ED years ago, i didnt believe it. Remember: This is still an oficial statement not changed yet " To avoid such issues in the future all 3d party are now required to make the game files available in case they are no longer able to support their products"

They've yet to agree to enact the agreement. I know, it's like something out of the minds of Monty Python. It's great and all, but honestly? Some assurances in a worst case going beyond "It'll work in 2.9.x" would be REALLY appreciated. I don't think a legacy version is going to cut it in the event of 4 modules going the way of the dodo. This wasn't a small install base like the Hawk was. ED's going to have to do something very, very big for consumers in that worst case scenario. I'd be a lot more gunshy about DCS in that case. I would not be alone. That's money I can put into cycling or flying.

Modules working for version XXX, no refunds. This is starting to sound like the Hawk's course of action. An agreement was reached at the end of 2024 but no announcement about it then? Why? You agreed on what? To disagree? Guys, you are opening the doors of speculation and frustration even wider. Stop listening to lawyers and start using more common sense.

Allow me to vent for a moment: I'm a long-time customer of Eagle Dynamics. I've played the game since it's inception with the Ka-50 and A-10. I own nearly every module and terrain, including the Razbam AV-8B, M2K, and F-15E. Regardless of how we got here, who is at fault, etc, I find it pretty disappointing that ED hasn't made any progress on exactly how they ensure the continuity of 3rd party modules, and it really, really irks me. This isn't the first time a 3rd party has created noise, and ultimately, it is ED's "ecosystem" to maintain. What is ED's plan for if (when?) an update breaks the Razbam modules? Will there be a refund? How should I be reassured before buying 3rd party modules in the future? What a disappointing situation. I'm pretty well to the point that future purchases are on hold. This exactly. "We're holding up our end of the deal" is apparently too much to ask? The alternative of no statement looks pretty bad.

Dear all, my inclination to contribute to DCS has reached an inflection point, and I have decided to withdraw from public contribution for the time being. I thank you all for your kind encouragement and friendship in the past decade, and wish you only the best for the future. -ch

The point of this thread imho is to give people one place to express their concerns, anger, ideas, speculations, hope,... until there is an end of the issue. Maybe this prevents other threads from beeing used for that purpose. You're obviously right with this Hydra thing, but it still has a use for many.

With the recent 2.9.18.12722 patch, the Iron Flag Campaign received a bit of an overhaul. It wasn't mentioned in the patch notes, so let me give you an overview. Subtitles Last year I tested some Iron Flag missions and noticed a few discrepancies between what the voice actors said and what was shown in the subtitles. With Baltic Dragon's permission, I thought "Let's quickly correct that". Well. Iron Flag has a lot of voice-overs. I mean a lot. Clicking through the Mission Editor turned out to be unfeasible, so I extracted the dictionary file from each mission archive. But that has everything in seemingly random order, so for every voice-over sound file I listened to, I then had to find the correct line in a file of 2000+ lines, which made the process unnecessarily slow. With a bit of bodging a couple of scripts together, I got all the lines ordered by their index so from DCS's point of view, everything was correctly identified, while for me it was in the proper order, making the process a lot smoother. Along the way, some common typos showed up, and for the most part it turns out that the voice actors just loved to go off script and change a little "We'll go ahead and" into "We're gonna", and a lot of stuff like that. Same meaning, different words. The campaign's instructors, BIFF and LOTUS, have particularly long lines of dialog, reaching from a simple "Two" or "Gotcha" up to around 40 seconds of dialog in a single transmission. For improved readability, these were split into paragraphs where applicable. In a lot of cases, these long lines of dialog were then repeated in the so called "action text" that prompts players to take a certain action. These are now split into much shorter chunks, omitting a lot of the free text around the actionable items, and were formatted as lists that, I hope, will be easier for players to follow than those super long lines. At this stage, if you find any typos, spelling or grammar mistakes in the subtitles, they're 100% mine (if I didn't introduce them myself, then I missed them. Well, except for some freestyle English that the voice actors spoke - the subtitles only reflect what they say ). BIFF's datalink For a long while, the instructor's aircraft (BIFF in most missions, and LOTUS in mission 9) have been AWOL from the datalink. Somewhere along changes to the whole datalink system and the introduction of new Advanced Waypoint Actions, it just stopped working. Adding new AI controlled aircraft worked fine, but with dozens or hundreds of triggers bound to the existing jets, replacing them with fresh ones just wasn't an option. The issue had been reported to ED, but with a fix still not in sight, I decided to dig into it, trying every Advanced Waypoint Action I could think of, but it just wouldn't work - BIFF and LOTUS just never showed up on TAD and HMCS. Well, if new aircraft do and some old aircraft don't, there's got to be some difference, right? And if the Mission Editor doesn't allow to edit the difference out, then maybe looking at the raw mission file might? So, long story short, I just copied the entire Advanced (Waypoint Actions) block from a fresh A-10C aircraft over to BIFF's and LOTUS' jets respectively in each of the 12 missions (10 regular ones, plus two shortened versions of the otherwise very long Mission 06), and voila: they're back! Additional fixes In some missions, the position of radio transmitters was changed to improve the quality of radio transmissions. There may still be a few cases where the radio quality of other transmitters degrades a lot and makes them much harder to understand. If you come across any of those, please let us know! In a few cases, changes and upgrades to the A-10C II module invalidated some voice-overs for what was a completed and finished A-10C campaign before the A-10C II was released. Where this makes an actual difference, NOTEs were added to subtitles and/or action texts. Small QoL improvements A bunch of smaller Quality of Life improvements were snuck in as well. The briefing images showing the flight plan have been slightly changed to make the waypoint numbers a bit easier to read in all missions. The datalink, now that it's working again, was updated and both player and instructor aircraft should have the correct GRP ID and OWN ID data from the briefing already set, as well as a sensible CALL sign, which is now the first and last letter of the flight call sign plus number in flight, so Tusk 1-1 would have TK11 preset for instance. A dialog about radio presets that appeared twice (once in M01, once in M06) was removed from the second occurrence. The weather in one of the missions was changed and should now be within legal limits for the assigned approach while still offering a challenging flight through thick clouds, with Nellis Runway 21L only becoming visible roughly 300 feet above minimums. The short versions of Mission 06 were updated to have plausible fuel values (these airstart missions used to begin with 100% fuel). There used to be kneeboard images showing the entire HOTAS tables for throttle and stick. These are now part of the module's default kneeboard, so they were removed from the missions. Credit where credit is due I want to thank Baltic Dragon for trusting me not to break these missions. Of course a huge shout-out goes out to Doughboy - I learned so much from this campaign! New members in the tester team who ran many of the missions countless times are Jakes, MadDog and Nexonix01, thanks for all the help! tl;dr Datalink is working again for the Instructor Pilot jet; a few kinks were ironed out; most subtitles were updated. Thanks for reading.

Thank you to everyone who gave constructive feedback. After initial feedback made it clear we need to rethink our approach we will with todays hot fix patch temporarily revert net.allow_dostring_in changes. We are considering a GUI toggle option for a future update.

You know what’s truly frustrating about this whole situation? That everything still seems to rely on just hoping things work out. People have asked repeatedly: what happens if the four modules stop functioning? Will ED simply say, “Well, go reinstall an old version where it still works”? That’s not a solution... it’s a shrug. The constant “for now the modules still work” and “we hope for a resolution” messaging isn’t enough. At some point, hope runs out... and customers deserve to know: what is the actual plan if that happens? Is there even one? Will you prevent the fire from breaking out, or will you try to put it out once it breaks out? Let’s not forget... the VEAO Hawk was one module. This time, it’s four, and the proposed “solution” seems even weaker. That won't be progress... it’ll regression.

First, at this point everything you are all debating is just noise. What is ED's plan to keep this from happening going forward? What is their way to fix it for their customers now that it has happened? I have three Razbam modules that are already degrading in terms of functionality, have never received promised features, and it sounds like they'll stop working soon. How is ED going to fix this? Refunds? I'm not interested in "store credits", if that is the solution. I already own the modules I want. Second, what should my expectation be in regards to 3rd parties? The modules I purchase could just stop receiving support at any time? Polychop had some well-publicized issues right after the release of the Kiowa... another reminder of how "fragile" ED's current business model is. Which brings me to the third point: Is there any belief that this business model is sustainable? It takes years, sometimes 7 or 8 years, for these modules to be developed and released between actual development time and time spent in "early access". Does ED believe it is a sound business model to have to maintain an ever-growing portfolio of modules with no revenue stream beyond their initial purchase? Over time, it would become an exponential amount of work to maintain these modules while developing the core game, with the only source of revenue being new "early access" releases that take years to develop. I believe that is why the CH-47 was released in such a bare-bones state, has seen such slow progress, etc. I think the model is bad, and if not already in trouble, eventually will be in trouble without some ongoing source of revenue to sustain the existing modules, terrains, and core game (subscription?). I know it isn't a popular view, but it is real.

Some screenshots by Whiplash for celebrating the Vietnam War Vessels 2.0.0 release:

I don’t care about the legal shenanigans between ED and RazBam. What concerns me is the idea that any of my beloved modules — which I paid for — could stop working at any moment. If that’s the case, I won’t be buying anything else. Thanks for your passion & support.

So, the clear thing we all get to understand is that, after all the Hawk mess, ED promised us that something like that will never happen again, and it is going to happen again unless a "positive outcome". So, ED plainly lied to all of us. GG ED.

this was the one thing irritating me like a pair of wet tighty whities on a hot summer day: "To avoid such issues in the future, all 3rd party agreements are now required to make the game files available to support their product..." What they didnt say was "for 3rd party creators who have signed contracts from here on out. Those currently in work cannot be enforced because of existing contracts; our attorneys dont want to open that can of worms for some reason or another because amending contracts is too hard big frowny face." FML for me not being able to read between the lines 7 years ago.

It was one thing when it was VEAO's Hawk, but now it's 4 aircraft and their solution (at the present) is keep a legacy version installed. I cannot underline how absurd that is when we're looking at 200+ gig installs. This is an absolutely untenable position for ED to give us. Granted, there's a lot that can change in this timeframe since we're talking quite a bit of time in the future, but it's still there. ED will have to bite the bullet, some how, if it wants to maintain positive customer will. It needs to also reconsider how it on boards third parties. This requirement to make game files available seems awfully wishy-washy. Is that the case for ALL third parties or was Razbam afforded special treatment because of how long they've been here? Quite a few uncomfortable questions need to be answered.

While ED and RAZBAM throw their tantrums, the rest of us are watching the sim fall apart piece by piece. This isn’t drama—it’s sabotage. No more modules for me — I'm done watching ED and RAZBAM wreck this sim. I believe this company would benefit from new ownership or leadership that could provide the care and direction it currently lacks, won't be long looking at the desperate daily sales.

The level of naivete displayed in some of these comments is sad but not surprising. Gamers arguing on the Internet aren't always the smartest collective bunch.

Your solution is unsafe and does the exact opposite of what this change is meant to accomplish.

Blame us, blame RB, blame both of us, but be nice to each other even if your opinion differs from someone else. I can't speak for RB (but I hope they feel the same) but we just want to see this resolved and if it were easy it would have been by now.