Leaderboard

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,

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.

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.

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?

The issue with your list here is that some of these things are core issues, such as refueling, which has nothing to do with the F-16, but 100% a core game issue, as well as Wishlist items that were never promised and tuning/bug fixing. As has been advertised in the Roadmap for a long time, all planned, primary features of the early access version will be available following the next DCS update. While the F-16C is leaving early access, there are still several items being added that are listed in the Roadmap, as well it is a premier title for us, and will continue to be tuned, improved and such. As an example, there is a large Manual update coming next release.

And it isn't new. RazBam have been making similar posts on and off from the start of this mess.

... unless it's a (IMHO rather lame) attempt at influencing the proceedings. Looking at the US's current administration it seems a very common (if clumsy and ineffective) attempt at bargaining. Anyone can change their mind, and 'never' can turn 'now' in a heartbeat. I've seen this happen in my own negotiations often enough. It's annoying, and it can tarnish the reputation of the people involved, but it hasn't stopped people from trying this approach.

If Razbam chose to make random postings on X or discord, that's their choice, The have nothing to do with the formal negotiations the two parties should be engaging in, and ED will achieve nothing by responding to them.

Ограничения это самое интересное что есть в системах, они показывают как система работает. Другое дело что ЕД подогревает онлайнщиков тем что стремиться одной стороне прорабатывать ограничения а другой крипить фичи. СПО это в принципе не инструмент для построения противоракетных маневров, даже самая новая цифровая, потому что физика это физика а лепестки радаров и АРГСН это не лазеры. Если реализовать ботов боевого управления и авакса как они работают в жизни, а не просто отчет где что, СПО будет глубоко вторичной системой даже на F-35. Чтобы реализм онлайн миссии дотягивал до реализма реализации аппаратов в DCS нужен человек-командир стороны, а миссия должна быть objective driven.

♪ He liked Razbam, she loved ED, ♫ Could it be any more obvious? ♪ He loved the Mirage, she flew Mi-8, ♫ What more can be said?

I think this news letter is perfect. It highlights on what's coming, instead of regurgitating what's been released. I hope ED keeps the same cadence going forward!

Maybe the next time you see someone with a MAGA hat on, you can ask them to pay the tax. They voted for it.

Летают. Только там есть очень и очень ошеломляющие эффекты, такие как автоматическое «приведение в горизонт», как только джойстик окажется в нейтральном положении. То есть, игра сама решает, когда летательный аппарат надо отбирать у игрока и проводить к горизонту. И это, насколько я понял, не отключается. Не говоря уже о тонких материях отклика на управление и поведения в воздухе. Примерно год назад пробовал, мне потребовалось нескорое время для психологической реабилитации после проб.

Although an "official statement" in a sense that this is a statement uttered from one of the principals, and it was done in a "public forum", it does not represent what I would accept as an "official announcement" for this matter. That would be either a common statement from both parties, or a statement from a common arbiter (e.g. judge) of both parties. Anything else has the bad aftertaste of someone trying to sway the court of public opinion and being wholly self-serving (especially if a communique is phrased as badly and amateurishly (intentionally?) inflammatory as the one in question). I recommend that we disregard anything unilateral and wait for a "real" communication that can be taken serious.

AN/AAQ-28 LITENING G4: Thermal Imaging Camera (FLIR): Resolution: 640×512 pixels (average for the G4 version) In newer versions (LITENING NEXT GEN): 1280×1024 pixels (HD) CCD Camera (Daylight/Visible): Resolution: Typically High Definition (HD), meaning at least 1280×720 or 1920×1080 (Full HD) in newer versions. AN/AAQ-33 Sniper: Sniper XR / ATP-SE FLIR: Resolution: 640×512 pixels Sniper Advanced (Gen 3): Estimated: 1280×1024 pixels, similar to the competing LITENING Next Gen. CCD TV camera: HD 1280×720 (most common in older and base versions) Possible: 1920×1080 (Full HD) in newer and export versions of Sniper SE That's right, and in my opinion, the image shouldn't have such blur in the basic mode. I know of a pilot who told me he could read the headline of a newspaper read by a human, but in the videos presented, it's likely even difficult to see a human because the image is blurry. As you can also see above, the resolution of the matrices is similar, I would not suggest downgrading Lightning now, because we will again deviate from reality. Sniper's advantage is the quality of its zoom and software (multitargeting, PiP etc); as you can see, the resolution itself is quite similar. It's also worth remembering that the image in the cockpit is meant to simulate reality, but we're sitting in a digital cockpit generated by DCS, which is a distinct disadvantage compared to the real thing and significantly reduces visibility. Let's not go down that route. Lightning image reception is okay, and the image from the Sniper pod should be just as good, but now someone here is trying to make things a bit more complicated. This creates a blurry effect (no focus, like in cameras). Please take a closer look. Thank you. Do you see the quality of the moon? This video is not a good example and should not be relied on - it is stretched, was recorded 11 years ago, and has probably been edited to a lower quality. Other Sniper's examples: https://www.lockheedmartin.com/content/dam/lockheed-martin/mfc/pc/sniper-pod/mfc-sniper-atp-pc-01.pdf https://www.military.com/video/4321763059001

I have not heard anything official yet, so nothing new on our end at the moment.

Looks like my mirage will break and I won't be getting my Harrier or Eagle, or Fulcrum, or Hellcat.

As we have stated in a number of places now, the Sniper pod and supported software was done for only the Viper; you could not just simply copy and paste it onto another aircraft. Why isn't it going to be on the A-10C? 1) For the above reason, it was always planned for the F-16C and only that. I know most of you guys do your research and even if you look at the implementation of the same pod on two different aircraft, they can work, function or operate very differently. 2) We do not have the information for the pod within the cockpit of the A-10C. We do not have legal accessible documentation on how the pod functions within the cockpit of the A-10C, its possible its identical or close to the Viper, but even if we found out it was, the information is neither available or legal to use at this point in time. I know this doesnt always make sense, especially when we are working on even new aircraft, but it is an issue here. 3) Lets say we resolved 1 and 2, there is a matter of resources and time alloted for such additions, most certainly it would take away from new developments, current projects, etc. While all the A-10C pilots might rejoice, others might be upset to find their favorite project was held up by giving the A-10C another pod that maybe it doesnt really need right now besides being cool to have. But But you guys did a suite update to add new items for the A-10C II update. While we added some cool new items, we did not update the suite software, and the A-10C remains mostly a Suite 3 aircraft. Yes it has newer suite items but we did not do a complete and total suite update on it, the information is simple not available for us to do so. And as most of you know, we have a special relationship with the military and the A-10C and will not step on or risk issues by using things we should not be using. Now, with the news that the A-10Cs might be retired sooner rather than later, maybe we will see more info come to the public, and then maybe down the road we could do more with the aircraft, but right now we just cannot do this to the level we would want to be able to do it. PS the Pilot model is getting close, so that is still coming.

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!

Whenever one side in (legal) proceedings uses public channels to 'contact' the other side -- instead of using the very, very defined channels set out for legal proceedings, they are behaving unprofessional: they are deviating from the protocol laid out by law), and it is likely that such communication has other intents as trying to resolve the dispute between the two parties. If they really want to contact the other side, they contact the other side's legal representation, or, failing that, file with the legally appointed arbiter/court. There is no way that either side does not know this, so a post on a public forum is an immediate red flag. So, to answer your question: if RZ want to contact ED there are ample proper and defined ways to do so. A public forum or "social app" is usually not among them. I find it inconceivable that the post from RZ was out of desperation because they could not reach ED. There are likely other reasons to go the public way, and I can think of no good, innocent ones. We - the customers and general public - have no say in this dispute, and we will not be consulted for the resolution. We might after. This is how legal proceedings work. They are eating the shoes! They are eating the socks! Oh my...

Part two of our first flight over the CW Germany map. AI_ATC Spangdahlem AB is available early to Patreon supporters. https://www.patreon.com/c/Avalanche110

Folks please dont go off topic. Please note that we will be making adjustments in future updates. So please continue to be patient. thank you

On a risk of sounding very salty, yeah, takes two to tango but only one to infringe on the IP...

installed today the 590.26 previev to enable fluid motion which is now available as well for RTX40xx cards in expectation that it will improove FPS in VR. In VR -> no changes at all, like mentioned by speed-of-heat. Made some testing with screen 2d setup as well, Fluid Motion enabled, experienced ~15-20 fps LESS in the same scene (quick mission, syria, free flight the first 30 seconds) For ME, after really QUICK tests, result will be better leave it off. All maxed out in DCS launcher; 3440 x 1440 DLAA !!NO DLSS!! Specs: 9800X3d RTX 4080 @ ~ 3000 MHZ

The final action we can, or likely to, expect is for Razbam's modules to be fully deprecated for the DCS website. What will also give us closure and resolution is when we hear something official from ED.

Need patches and development just like before, but still just as "great" as before.

That's not very GUCCI of you.

When do we get the currenthill assetpack

Воевать с бессмертными и не испытывающим боли страха противником - тоже удовольствие такое себе. Когда смотришь реальный кадры БД, невольно ловишь себя на мысли что Боты в играх еще довольно дерзко себя ведут в сравнении. Реальные люди порой кажется что вообще не оказывают сопротивление и просто гибнут, все действия очень скованные, реакция заторможенная. Какой то фатализм. В оффлайн уничтожение противника не является главной целью. Основное - это совершить сам факт полета и, по возможности, отработать в тех рамках и задачах которые есть. Результат сильно вторичен. И страх есть - ведь если погибнешь, не перейдешь к следующей миссии. По большому счету , если есть смыслы, есть ради чего совершить полет - то абсолютно неважно онлайн это или оффлайн.

Thx for the update but .... "Spotting dot rendering is being reworked" - just promise me the BIG DOT BOX won't come back in VR. What we have now works very well for the auto option in VR. I hope it's some other fix.

18 июля 2025 года Дорогие друзья, Распродажа DCS Summer Sale 2025 оказалась очень востребованной и мы продлеваем срок действия акции до 15:00 21 июля 2025 года. Покупайте летательные аппараты, карты, кампании и расширения со скидкой до 50%. Заруливайте на стоянки нашего электронного магазина и выбирайте то, что вам по душе! Мы проводим работу по подготовке следующего обновления, которое добавит новые фичи к нашим самым популярным летательным аппаратам, включая F-16C Viper, F/A-18C, AH-64D, CH-47D и F4U-1D. Вы получите улучшенное поведение ИИ, доработки редактора и генератора, исправления нестабильностей. Обновление выйдет сразу, как только мы будем уверены в его готовности. Оставайтесь с нами и следите за новостями. Благодарим за энтузиазм и поддержку. Искренне, Команда Eagle Dynamics Летние скидки Продление Мы продлеваем действие Летней Распродажи 2025, но только до середины дня 21-го июля по Гринвичу. Распродажа закончится ровно в 15:00. Многие из самых востребованных модулей продаются с большой скидкой. Если у вас есть возможность приобрести только один модуль, то рекомендуем обратить внимание на знаковый и легко узнаваемый A-10C II Tank Killer с его смертоносной 30-мм пушкой издающей непередаваемый “Брр-р-р-р-т” и планирующими JDAM в комплекте за 50% стоимости. Если вам по душе многоцелевые самолёты, то F/A-18C или F-16C Viper станут отличным выбором со скидкой 40% и HARM, JDAM и AMRAAM на борту! Нестареющий F-14 Tomcat от Heatblur продается со скидкой 30%, с уникальными ИИ-помощником Джестер и возможностями работы с авианосца. Ну, и обратите внимание на относительно недавно вышедший модуль самолёта F-4E Phantom II, который продается по очень резонной цене с 25% скидкой! Вертолётчики могут порадовать себя 50% скидкой на AH-64D, а также на быстрый Hind с искусственным интеллектом Петровича - вашего напарника в экипаже. Вместе с модулем авианосца Supercarrier палубные операции в DCS стали дешевле на 40%, и с ними отлично стыкуются самолеты F/A-18C и F-14A/B. Исследователи и любители дальних перелётов могут взять карту Сирии с дисконтом в 30%, а уникальная карта обширного Невадского Испытательного Полигона ВВС США предлагается за 50%. Эти цены продержатся всего несколько дней, поэтому поспешите! Предложение утратит силу 21-го июля в 15:00 GMT. Обновление DCS Отчёт о разработке Игровое ядро Целый ряд обновлений готовится по линии ИИ юнитов, редактора миссий и генератора, а также улучшений ядра. Будут устранены замеченные баги и неточности, а бомбардировщики B-1B и B-52H получат новые варианты боевой нагрузки. Наземные и морские юниты получат улучшения по части графики и реагирования при боестолкновениях. Некоторые функции скриптового языка будут расширены возможностью получать входные параметры и возвращать новые значения. Это может потребовать от авторов и разработчиков миссии переработки существующих миссий для получения максимального эффекта. Редактор миссий получит недостающие в некоторых случаях, всплывающие подсказки и графические исправления. Улучшен будет и рендер точек контактов на дистанции - уточнено количество точек, которые могут рассчитываться за один проход одновременно. Генератор миссий получит улучшения в алгоритмах размещения юнитов на разных картах. Будут исправлены ошибки, замеченные при использовании голосового чата. Также сообщаем о уже произведенном изменении, но не нашедшем отражения в списке изменений к предыдущему обновлению: мощность БЧ авиабомб Mk-80 и M117 была уточнена, чтобы соответствовать реалистичным показателям эффективного радиуса поражения. F-16C Viper Мы готовим к выпуску ATP контейнер AN/AAQ-33 с соответствующим изменением руководства пользователя самолёта. Будет исправлен крэш, возникающий при использовании HARM некоторых случаях, а также фризы на экране радара. Выпуск ATP контейнера для Viper завершает развитие модуля по планам Раннего доступа и модуль будет переведён в релиз. Однако мы продолжим доработки и расширение функционала. В частности мы планируем буксируемую ложную цель, модем для межсамолётного обмена данными (IDM) и работу RWR в режиме handoff. F/A-18C Самолёт получит радиолокационный режим полёта с огибанием поверхности, уточнения в алгоритмах HARM PB и GBU-24 CLAR, исправления логики аварийного сброса подвесок и РЛС FLOOD-mode, а также некоторые другие доработки СУВ во взаимодействии с оружием воздух-поверхность. AH-64D Возможности Джоржа, виртуального члена экипажа, будут расширены семью новыми режимами поиска целей, улучшенными алгоритмами принятия решений на открытие огня, уточнениями в использовании НАР, запуску/остановке двигателей по команде, сопровождению множественных целей и улучшенными голосовыми сообщениями. Будет доработано руководство пользователя. DTC Вновь добавленные объекты ЗРК и морские юниты из комплекта CurrentHill найдут отражение в таблицах CMDS, будет улучшена совместимость с оригинальными миссиями и фильтрация скрытых в редакторе юнитов. Вызов панелей DTC из редактора станет возможным по комбинации Ctrl + D. CH-47F Данные участка пути (страница Leg-Data) будут автоматически обновляться информацией о температуре воздуха, потребному топливу и т.д. Исправлена индикация на HSI и отрисовка цифровой карты на МФД. Уточнены возможности по транспортировке количества личного состава в грузовой кабине. Mi-24P Hind & Mi-8MTV2 Положение наружных створок прицельного оборудования теперь синхронизируются в мультиплеере, а на Mi-8 исправлена работа счётчиков на панели управления ДИСС-15. F-86F Sabre Используемая по умолчанию для отладки комбинация LCtrl + LAlt + T заменена на другую. МиГ-21бис (Magnitude 3) Скорректированы ЛТХ самолета под управлением ИИ. F4U-1D Corsair (Magnitude 3) Улучшена модель системы охлаждения, автоматический режим обогащения топливной смеси, уточнены показатели коэффициентов сопротивления и допустимой скорости выпуска шасси. Боты теперь смогут применять планирующую бомбу Bat. Уточнена анимация некоторых органов управления в кабине при использовании мыши. На авианосцах Ессекс заработали лифтовые подъемники, смоделированы повреждения палубы, вибрации антенного оборудования, уточнены текстуры, бортовые номера в редакторе. OH-58D Kiowa Warrior Уточнена страница NAV-SETUP, PERF CALC и меню HOG. Исключены двойные срабатывания и зацикливание на элементах меню. JF-17 Thunder Исправлено управление стробом захвата (TDC) на экране радара посредством осей джойстика, уточнено положение TDC на ИЛС, утечки памяти при работе модуля. Добавлены некоторые новые команды HOTAS. Черная Акула 3 & Горячие Скалы 2024 Добавлены новые миссии на карту Ирака для Ка-50. Восстановлен режим Sidewinder Cage/Uncage для модуля F-5E ГС. Карта Холодная Война Германия от Югра-Медиа Будет исправлена проблема с чрезмерным размером модели повреждений, уточнены названия городов и маяков VORTAC. Уточняются размеры иконок для больниц и площадок ПВО, будет добавлено большее количество стогов сена для сельхозугодий и тракторы. Внешний вид и высота куполов церквей будут исправлены, как и модели повреждений стадионов. Дополнительная информация Изучайте возможности и учитесь Мы подобрали для вас несколько познавательных ссылок на видео и материалы по новым возможностям, которые станут доступны после обновления. AN/AAQ-33 ATP – Part 1 (YouTube, 9 мин.) Первая часть. Перечисляет основные функции, процедуры, с примерами использования ATP, таких как выбор камеры, настройка FOV и пояснения к символике. Этот контейнер станет важным дополнением к Viper и расширит номенклатуру используемых прицельных контейнеров. AN/AAQ-33 ATP – Part 2 (YouTube, 12 мин) Вторая часть инструктивного видео дает представление о продвинутых функциях ПКЦ, таких как: Multi-Track, Picture-in-Picture, XR processing, и др. Контейнер ATP даст игрокам новый опыт, который ранее не был доступен в DCS. F/A-18C Terrain-Avoidance Radar (YouTube, 7 мин) Летайте вместе Matt “Wags” Wagner над самыми интересными зонами карты Ирака, и учитесь применению радиолокационного режима Terrain Avoidance (TA) - низковысотного режима полёта с огибанием земной поверхности. AH-64D – New George Commands (Обновление форумной темы) Предстоящее обновление заметно расширит возможности Джорджа в качестве оператора по поиску и уничтожению целей. В обновленной информации содержатся особенности интерфейса и логика передачи команд Джорджу. Каждая данная выше ссылка – это краткое практическое руководство, которое даст возможность подготовиться к предстоящему обновлению. Информация готовилась параллельно с обновлениями руководств по F-16C и AH-64D, которые содержат ещё более подробную информацию. Заходите, оставляйте комментарии и оставайтесь с нами! Удачных полётов, друзья!

If anyone comes down to Boscombe Down Aviation Collection (from VR Guys video) on a Tuesday, please say hi to the guides and I will happily show you around. (ask for the crazy Helicopter Navy lady) TJ

Signing off with “it takes two to tango” sounds like he still wants to dance. Bust out the Maracas, let’s see some flamenco

Until the dispute is resolved we do not know and can not say. We all continue to hope for a good outcome. thank you

Hi folks, we have no new information to share. Once the dispute is resolved we will know more, until then we have to continue to wait. thank you

Already planned:

https://www.digitalcombatsimulator.com/en/files/3318337/

Great module... was.

DCS Ka-52 [MOD] LiveStream с разработчиками мода

Stream Stream Stream

Клоунада

Любитель точного моделирования. Школу восемь классов оканчивали, полагаю?

The GPS and INS are 2 disconnected systems operating concurrently. The Mission Computer will initially just output a position estimate based on the INS alone, but it is observing the position errors between it and the GPS. When it recognizes that the INS exceeds 300 feet of error it will then introduce the GPS data into the kalman filter and correct the blended positiong estimate in the MMC. There is no actual automatic fixing going on in the INS like you would see with EGI. For the kalman filter, the GPS is just there to be a reference (a noisy one) that it uses to corral the blended position estimate to under 300 feet. When running a FIX it should then correct the INS back to an accurate error state. The kalman filter will at that point stop blending the position estimates and go back to trusting the INS alone again, until the error accumulates back up to above 300 feet and the cycle repeats. I have not flown the F-16 in quite a long time, but that is my recollection of how the FIX function should operate.

Last weekend, I flew the AH-64 using a dynamic slot on my squadron's server. The aircraft went down and while the pilot was killed I must have switched to the CPG just before exploding into a fiery hole in the ground. Afterwards, I spawned in a few more time as the pilot in different Apaches. One thing remained constant: The TEDAC display was ON any time I jumped into the cockpit. Can this problem be addressed? It's been on the books for a very long time with no updates (1yr 9mo+) from the ED Team. Here is a screenshot of my cockpit setup with multi-monitor configured (Main monitor plus 3 Cubesim MFDs). The main viewport is on the left, the TADS Page is on my Left MFD, the Weapons Page is on my Right MFD, and the errant TEDAC display is on my Center MFD.

Some castles have been implemented

In order not to drag this out too much, as this post is quite lengthy as it is, I'll get straight to the point. The DCS F-16C is not ready for full release. This thread is in response to a post by BIGNEWY saying that the Sniper XR is the last major item before the DCS F-16C is ready for full release. Below I've listed some of the reasons why the DCS F-16C is not ready to leave early access, even with the Sniper XR added, by describing the current state of this product. This post was written with the help and contributions of several community members, who I want to send my deepest thanks to; you know who you are. Lastly, this is not an all-inclusive list, but rather a summary of the major aspects which are currently missing or unfinished in the DCS F-16C (there are A LOT of smaller items remaining in addition to this, including quite a few bugs). It's quite lengthy though, so go get a bag of crisps, crack a beer, and lets get on with it: - Damage model: Practically nonexistent, with no real damage being simulated except fuel leaks and your wings getting blown off. I put this at the top of the list because I cannot see how you can have a digital combat simulator without combat damage being simulated. - Maintainance / Pilot Fault List: Practically nonexistent, still only shows a single message which is the "FLCS BIT FAIL" if the FLCS bit fails. This is the entire error reporting system of the F-16C and is therefore an essential system in order to keep tabs on the status of your aircraft, even when you haven't taken any combat damage. For example, if your L16 time isn't set, you should get a "LK16 TIME REQD" message to tell this to the pilot. At the moment, you will eventually notice that something is wrong with datalink, and then you have to figure out what the issue is on your own through troubleshooting, rather than just checking the PFLD and immediately knowing what's wrong. This is just one example of many where proper MFL and PFL messages would be incredibly helpful, and the reason why those systems exist in real life. - Steerpoints: Exists in a very limited state. Only supports regular steerpoints, markpoints, and a partial implementation of D/L steerpoints. Many types of steerpoints are completely missing, like pre-planned threats, geographical lines, SEAD steerpoints, a plethora of LINK 16 steerpoint types, etc. We're also still missing different CRUS TOS functionality, like having DES TOS reference HACK time instead of SYSTEM time, and also the ability to blank DES TOS times and have the CRUS TOS required velocity be calculated for a steerpoint without a DES TOS, based on the DES TOS of a later steerpoint; an incredibly useful feature for improved timekeeping. - Digital Terrain System: Completely missing including its subsystems like PGCAS, TRN, OW/C, DBTC & PR. An essential system from the earliest tapes of the F-16CM-50 where you load the terrain data of a 480x480 nautical mile area wherein the DTS has features both to avoid CFIT (controlled flight into terrain) which was the biggest cause of death in the USAF at the time, to providing various subsystems to facilitate safer low altitude operations including a kind of digital "terrain following radar" mode, to decreasing INS drift by comparing your radar altitude to the know terrain elevation in different parts of the map, and also to allow more accurate targeting without using active sensors. This is for example what makes high angle JHMCS markpoints accurate, as it can reference the known ground elevation of the location you're looking at. Without the Digital Terrain System implementation, the DCS F-16C has much higher risk of CFIT, much higher risk of flying into terrain/obstacles during low altitude operations, much lower targeting accuracy (especially at longer ranges and in uneven terrain), and higher INS drift over non-flat terrain than a real F-16C of our block and tape would. - ECM: Barely implemented. Currently only barrage jamming is kinda working, and even that is extremely ineffective most of the time. MODE 1 and MODE 2 self-protection jamming is wholly inefficient under all circumstances, as the ALQ-184 currently is seemingly incapable of breaking SAM radar locks. There's also no ability to choose which bands to jam, making it impossible to jam certain surface threats without jamming your own radar for A-A sanitizing. Neither MODE 1, 2 or 3 should inhibit your radar, but rather MODE 2 & 3 should reduce the effectiveness of your radar while actively jamming in the same band as your radar, and not impact the radar at all while jamming in other bands. The AN/ALQ-184 in DCS also has 360 degree coverage, whereas it would have roughly 120 degree cones fore and aft of the pod in real life, with diminshing effect closer to the outer limits of those cones. MODE 1 should only use the aft emitter to jam threats, while MODE 2 & 3 use both fore and aft emitters. It should also have high/low settings to angle the jamming emitters downwards for surface threats and upwards for higher altitude A-A threats, as well as cooperative jamming where multiple F-16C's in close formation boost jamming effectiveness. As an aside to this, chaff is completely useless against certain threats. You can drop 120 chaff in 1 second and you still will never be able to spoof an SA-5. This in combination with an inability to break locks during jamming, means that your only real defense once an SA-5 is locked on to you is to dive towards the ground and break line-of-sight. Other emitters have similar issues. - SEAD: This point encompasses a lot of different systems which are necessary for efficient SEAD, which after all is the primary role of the F-16CM-50 in the USAF. As mentioned, the AN/ALQ-184 is completely useless in self-protect mode (MODE 1 and MODE 2) as it cannot break locks, decreasing survivability, as using barrage mode will constantly transmit your location, and also disable all your active sensors as well as the HTS pod. Most importantly, the AN/ALQ-184 is unable to break locks, meaning it can only be used pre-emptively (not very good when employing wild weasel tactics). The AGM-88 has modes like TI/GS/DL which have not been implemented, limiting the AGM-88's effectiveness in the SEAD role. Also, many different AGM-88 HOTAS commands are completely missing. HAD priority targets are missing. The LINK 16 Special Channel net has a very rudimentary implementation. The ability to target/blank pre-planned threats is completely missing. The ability to store detected emitters as SEAD STPTs is completely absent, greatly decreasing your ability to engage SEAD threats as they will just disappear after going inactive for a while, and the only way currently to target these emitters once they go inactive is if you have a human wingman, because then you can send that emitter to him via L16, and then he can send it back to you. If you've got no human wingman, you're out of luck. The AN/ALR-56M Radar Warning Receiver is still incorrectly implemented, making it useless for any kind of high threat environment (the kinds of environments where SEAD is required) as it conveys no relative lethality of detected emitters but rather displays all threats as equally lethal, being especially useless for pop-up threats and active missile avoidance as you can never tell how much of a threat a detected emitter poses to you. In real life, the late cold war saw multiple datalink capable SAMs which don't give RWR warnings at all, increasing the need for the kind of relative lethality displaying of threats that the AN/ALR-56M does in real life, especially for SEAD operations. Currently, we don't have any datalink capable SAMs in DCS, but if it's ever added, the F-16CM-50 will be completely unable to operate in that kind of environment, unlike its real world counterpart. The AN/ALR-56M should also use data provided by the INS to update detected threat locations during maneuvering when emitters may end up in RWR blind spots, and even flip the symbology when rolling the aircraft upside down, so emitters are displayed in the correct direction under all circumstances. Having a functioning RWR is maybe the most important aspect of being combat effective in the SEAD role, and currently we don't have that. - AN/ALR-56M: Even though I mentioned the issues with the RWR just above, I'm still making this a separate point just to emphasize the importance of this system. If I could only pick a single thing that'd be fixed in the DCS F-16C, it'd be the AN/ALR-56M. Right now, the DCS F-16C is completely handicapped, not merely in SEAD, but in all combat situations, because the current RWR implementation is not merely incorrect, but it makes the RWR close to useless. The AN/ALR-56M was chosen as the new standard RWR for the USAF because of it's incredible capabilities and the added situational awareness it provided to its pilots, and this is also why it was rolled out so early on the F-16CJ/CM-50, the USAF's primary SEAD platform. However, in DCS, the AN/ALR-56M is the single least capable RWR in the whole modern US fighters lineup, and in many ways it's even inferior to the old 1980's SPO-15 mounted on the MiG-29A. If you get an AMRAAM fired at you, the SPO-15 (and the real life AN/ALR-56M) will indicate how quickly the missile is approaching and how close it is to impacting you, allowing you to plan your missile defence and perform last ditch maneuvers. With the DCS AN/ALR-56M, you have no indication of how far away a missile is except when it impacts your aircraft. This really, really, really, really needs to be fixed, especially for a SEAD platform like the F-16CM-50. - Air-to-air: This is also a collection of different things. AIM-120 is still missing many features, including target size options and not least the HPRF mode, greatly reducing the maximum effective range of the AIM-120 and making the bread and butter SKATE tactic non-viable against most threats, as you need to guide it all the way to MPRF mode, a.k.a "pitbull". The Uplook Search (ULS) radar mode is still completely missing. STT mode is extremely ineffective at long range, and even against a high aspect non-maneuvering target which is detectable in RWS/VSR, it will not be able to produce a stable lock. A-A, MRM and NAV master mode are also unable to have different CRM modes selected and retained. COAST mode is still missing, meaning that notching will immediately break your radar lock and the aircraft will not even attempt to reacquire the target. On the topic of notching, the current radar implementation is EXTREMELY suceptible to notching. You can be 5 nautical miles away from an enormous KC-135 in look-up conditions against a clear blue sky, and it will still notch you as it reaches 90 degrees aspect, even if it's only for a split second, which should be physically impossible with a modern radar like the AN/APG-68V(5). Even notching against ground clutter should be extremely ineffective unless the target is very close to the ground or has a big chaff cloud next to it. Auto range scaling in SAM/DTT modes still automatically decreases the range scale, which it shouldn't, making those modes useless for situational awareness as you should still be able to freely sanitize the airspace beyond your bugged tracks in those modes. Also the HAFUs are completely unreliable, making TWS especially useless as the art of upgrading tracks is a complete black box. Blanking LINK 16 symbology will often blank all the correlated bricks as well, meaning you cannot even see the things which you've detected with your own radar. You can lock them up though and launch missiles at them, you just cannot see them on the display. Contacts which start jamming will often get snapped to exactly 99.0 nm distance on your FCR, often forcibly rescaling your FCR and requiring you to reset the FCR range settings in the middle of combat, to be able and reaqcuire that same threat. HAFU identity is also very unreliable, with enemy threats often being displayed as green friendlies for no apparent reason. And when you're in ACM mode, the bore cross in the HUD and bore ellipse in the HMCS still do not show true radar line-of-sight like they do in real life, but are instead completely static paintings giving no information at all regarding where your radar is actually pointing. - Air-to-ground: Ground radar is still extremely janky and cumbersome. Ground maps will regularly instantly blank itself during maneuvering. When entering many different radar modes, rather than the radar moving quickly to it's starting angle and then sweeping to generate a map, it often moves really slowly to it's starting angle and just does nothing for a couple of seconds, and only then does it actually start mapping. GMT mode doesn't actually lock onto the target, but rather just the point on the ground your cursor happens to be over. Gain/Contrast/Level settings for the ground radar are not granular at all, and it is often very difficult/impossible to achieve a good balance between them. Changing these settings should also only apply for what is mapped after changing those settings, so if you raise gain in the middle of a sweep, the first half of the map will be low gain and the second half will be high gain. On some maps, like Persian Gulf, you seemingly cannot ground map terrain, only objects. JDAMs still cannot be programmed properly. JSOWs cannot be programmed properly. GBU-24 is there in spirit, but still hasn't had its guidance modes properly implemented, making it quite useless and unable to even reach the target when dropped at max range and high altitude. IFF interrogations are not possible in A-G mode, which they should be. There are also missing munitions, like the CBU-89/104's, various training munitions, possibly even the JASSM. - Lighting: Some things are completely missing, like the external IR emitters which our tape and block of DCS F-16C should have, being selectable through the COVERT modes to allow external lighting at night which isn't visible to the naked eye, and also to only illuminate the lights on top of your aircraft, to stop ground threats from spotting you. If you look at the the external lights through NVGs, you'll see that the green lights seem to be NVIS compatible, but the red lights will completely fry your retina. Cockpit flood lights have very low intensity even at the max setting, and also little to no light scattering, meaning they don't actually flood the cockpit. They're more like focused spotlights, leaving many parts of the cockpit completely in the dark, even at full intensity, including the new pilot body kneeboard which is completely unreadable at night even with every single internal light source set to maximum. On the topic of spotlights, the actual Cockpit Spotlights under the glareshield are completely inop. The Cockpit Spotlights are also the only light source in the entire aircraft which are usable purely with battery power, and are commonly used in real life to monitor engine instruments during startup at night. They are also used to illuminate the pilot body kneeboard when the pilot don't want to illuminate the entire cockpit with flood lights, in order to be more NVG friendly. In addition to these points, there are also issues with light intensities. Some lights like the left indexer or external formation lights, etc., usually go from slightly dim to quite bright between 0% and 5%, and then every setting above is just almost indistinguishable amounts of extreme brightness. With other lights, most notably the cockpit flood lights, you can barely see them at all between 0% and 50% intensity, and then they go up to kinda bright at 100%. This becomes even more troublesome because of the way light brightness works in the F-16C, because when the flood lights are set to high brightness, every other malfunction and indicator light in the cockpit will go to max brightness too. This means that we can't have a bit of flood lighting without getting completely blinded by every other light source. Some lights also don't seem to be NVIS compatible at all, especially the RWR panel which is extremely bright and will wash out your NVGs. The right indexer lights seem fully NVIS compatible and won't blind you even on max brightness, while the left indexer will wash out your entire NVGs at max brightness, and still be very bright at only a few percents intensity. - Textures: The default DCS F-16C textures (including those available in the texture template) are of incredibly low quality, with not merely bolts and screws missing, but entire panels. Also the textures themselves are just poor in quality compared to what you'll find in the DCS User Files section. ED should honestly just pay Roughmaster to make a new texture template for the DCS F-16C, and remake all the low-quality liveries which are currently available for the DCS F-16C, as Roughmasters liveries are of such incredibly high quality that it's almost incomprehensible. Cockpit textures are also missing textures for multiple things. - Tankers: When refueling at a KC-135, the boom still has no resistance and exerts no force on the aircraft. In real life, the boom will push back against the aircraft when connected, allowing the aircraft to "rest" and stabilize itself against the boom. This currently doesn't happen in DCS, making aerial refueling more difficult as you need to have more accurate thrust management than real pilots do in order to stay in position. Tankers in DCS also will never extend the boom farther than the halfway point when connecting even if the player is close to center and fully stabilized, so the player always has to move closer than the halfway point to connect, rather than like they do it in real life where the boom operator will extend the boom to meet the connecting aircraft. When it comes to tanker external lights, they will not turn on their position lights until the receiving aircraft is less than 1 nautical mile away, making night rejoins extremely difficult unless you want to fry the boom operator with an STT lock. Also, there are no external flood lights on the tankers, making them practically invisible while refueling at night, except for the fore/aft and up/down lights. Also, the background lighting on the fore/aft lights is very bright at night, making your fore/aft position incredibly hard to see. During daytime, the lights are very dim and the glass on the fore/aft and up/down lights is very reflective, with reflections often obscuring what the lights are indicating, especially when the sun is low in the sky. Lastly, tankers still do not transmit TACAN in A/A mode, but you have to use T/R mode instead as if they were a ground based station, meaning you also cannot see the tanker A/A TACAN distance on your DED/HUD. It would also be nice to have some basic boom operator functionality, like giving break-away calls and raising the boom if the player is to close/unstable (including an actual boom collision model), giving heads ups before entering turns, reading off the amount of transferred fuel at regular intervals, maybe even having the player be able to request a certain fuel amount via the radio menu. - DCS F-16C manual: This manual is still not up to date, and new features which are added to the DCS Stable branch still aren't updated in the manual, leading to a lot of unecessary threads on the forum as a lot of information about how systems work are lost to the sands of time in the Viper Mini-Updates thread, and usually have to be conveyed through word-of-mouth. For the things which are correct in the manual, the systems are in many cases bugged and not working according to the manual, leading to further confusion in the community when being referred to the manual. Honestly, everytime a feature is added or changed in the DCS F-16C, this should also be reflected in the manual, including a changelog of added/changed features in the manual itself. If systems are not functioning correctly, this should also be noted in the manual with a small notice in that section. After all, DCS is now a unified stable branch and then it'd make sense for every change to be in the documentation, since this isn't a beta build anymore. - The jealousy: Things which have been implemented in other ED modules, but not the DCS F-16C, even though they should be present for our block and tape. Things like the HSD Expanded Data, whose equivalents are present in the A-10C and F/A-18C, but which for some reason isn't planned to be implemented for the DCS F-16C even though it was present in the simulated block and tape IRL, greatly reducing situational awareness via datalink. Or the decision of ED to not implement the AN/ARC-210 radio which was already in active service for our block, tape and year of F-16 (confirmed by multiple ED active duty SMEs + non-ED active duty SME's + US DoD fiscal reports showing amount of quarterly AN/ARC-210 unit installations for USAF and ANG + the actual real world documentation for our tape of F-16CM-50 describing AN/ARC-210 functionality) because "it was more common later", leaving the DCS F-16C as the only modern US aircraft in DCS without the AN/ARC-210 (A-10C, AV-8B, F-15E, F/A-18C), and therefore it is the only modern US aircraft in DCS without the ability to tune multiple UHF frequencies and use a single radio for the entire UHF/VHF/FM range with HAVE QUICK capability, even though it could do this in real life during our tape and time. The AN/ARC-210 would be a very simple item to implement too as it requires no 3D modelling changes, but merely new DED pages, and seeing as this radio is already implemented in other ED modules like the A-10C and F/A-18C, it should be quite simple to port to the F-16C, making ED's resistance to implementing this radio even more of a question mark, seeing what an enormous improvement it'd be to the F-16's communications suite. There are also other things, like the HAVE QUICK page being available in the A-10C, allowing HQ functionality through SRS (SimpleRadio), however the HAVE QUICK page has not been implemented in the F-16C, making the F-16C unable to use HQ via SRS. The ability to choose Fighter/Mission Channels on LINK 16 is present in the F/A-18C, but not the F-16C forcing them to send D/L points to every F-16C on the server. Or the IFF page which has been implemented in the F/A-18C and allows setting Mode 1, 2, 3 and 4 codes, has not been implemented in the DCS F-16C, meaning we cannot set our squawk codes as you would IRL through the DED/ICP. We can only set Mode 3 via the analogue backup IFF panel. Also, the A-10C even has Mode 1 and Mode 4 timetable support, giving alerts at specific time intervals when the Mode 1 and Mode 4 codes change. The F-16C should have similar functionality where the aircraft will, instead of alerting, automatically disable/enable transponders, as well as change their transponder codes, based on certain time and position requirements. More importantly, none of these features require DTC as they can all be set from the cockpit. And even if DCS does not support HAVE QUICK and IFF functionality at this point in time, these things are supported through other softwares like SRS and LotAtc, and is as mentioned already present in other ED modules, so I don't see why we wouldn't get the same treatment in the F-16C? There are also some amazing features from non-ED modules like the Datalink Mission Assignment API in the M-2000C, which allows external sources (either AI GCI or a human via LotAtc) to send taskings via datalink to the aircraft and have them be viewed on the situational displays in the aircraft. The F-16CM-50 of our tape and year had that same kind of functionality via L16, where C2 assets can send a plethora of mission taskings which get received as a data messages, with the ability to view and accept/reject taskings via the HSD, and also send tasking completed/aborted messages to the C2 station. This would be a huge deal for human GCI/AWACS in DCS, especially with players speaking completely different languages, and it'd also open up a tonne of opportunities for mission creators to access this functionality via scripting. I'm not going to delve into why the DTC and its related functionalities are absolutely essential, as they're already in active development. Other systems like the IDM functionality and towed decoys are at least on the roadmap. For all the other points mentioned above, there seems to be no light at the end of the tunnel. If these kinds of major systems are completely missing at a so-called "full release", that would set a new benchmark for what level of quality we can expect of DCS modules. In addition to all the essential features which are still missing, the amount of bugs which still remain is impossible to overlook, to the point where you cannot even cold start the DCS F-16C according to real life checklists, as there are several inaccuracies which would force you to abort the mission and put the jet into maintainance in real life. In regards to BIGNEWY's recent comment that the DCS F-16C "is complete in regards to what we intend for the module. Our modules are never intended to be a 100% replication of the real aircraft.", I would like to point out that we're not even remotely close to a 100% replication, and people aren't even asking for 100% replication at this point. Making a 100% replication would mean adding things like the need to cycle the flight controls before initiating the FLCS BIT to warm up the hydraulics and get rid of any air bubbles in the lines, as the FLCS BIT will otherwise most likely fail. It would mean adding things like accurately modelled startup sequencies for individual systems like the FCR, MIDS terminal and other systems, where they run their own internal bits and take time to power up before being available for use. Or maybe some realistically modelled magnetic drift of the HMCS, sometimes requiring re-alignment in the air. These types of things are available in other F-16C simulators available on the civilian market, and I think we all would've hoped that the DCS F-16C would reach at least a similar level of depth and, as ED themselves have said, the DCS F-16C would be "the most realistic simulation possible" and offer a "detailed simulation of the Viper’s engines, fuel, electrical, hydraulic, comms, lighting and emergency systems and many more". I don't know how you can claim that the DCS F-16C delivers on any of those promises in its current state. I realize that ED probably wants the DCS F-16C out of early access since it's been there for over four and a half years now, but it would be a huge mistake to do so at this point in time. For ED's own sake, for their own reputation, and the communities faith in their current and future products, they should never allow a module which is in the dire state of the DCS F-16C to be considered "full release". Full release means finished, irregardless of what your post-release plans are. You might add a feature or fix a bug later at your whim, but in the end, the full release is supposed to contain everything we customers paid for, a complete and stable product, and anything which is added to the product free of charge after full release is merely charitable work on the developers behalf. It is not the fulfillment of some obligation to their customers, but rather a completely voluntary act which goes beyond what the customer paid for, in order to increase customer satisfaction. And to say "here it is" and give us what have currently + the Sniper XR would be an incredible betrayal of trust, and I for one would never buy a DCS early access module again, if this is what I can expect from it. I'm happy to support ED and third-parties early in the development process even by purchasing pre-orders as long as they deliver a decent product upon full release, which is what has happened previously in my experience. But if the F-16C is pushed out like this, that'd be a turning point for DCS as a platform. And this is something I say as a long-time DCS customer, who has been flying DCS on a regular basis ever since the A-10C was released over a decade ago, and has spent so much time and money on DCS that I don't even want to attempt to add it all up due to fears of what I'll be faced with. Without mentioning any specifics, I think we can all agree that the current drama in the DCS community is testing the community's faith in ED and DCS as a product. Pushing the DCS F-16C out of early access in its current state would do nothing to improve that situation, but would rather risk pouring fuel on the fire, which I don't think neither ED nor the community wants at this point. DCS isn't a perfect product, but it has the most potential of any combat flight sim on the market, and has been making strides to become the best combat simulator on the market. Please cherish this and do not make any reckless decisions in order to meet internal deadlines, while alienating your own customers. All I ask for is that when the F-16C reaches full release, the level of quality will at least be the same as other ED modules. The DCS A-10C which was released a very, very long time ago when ED was a much smaller company, was an incredible product. It had practically all the systems modelled that it would've had in real life to an incredible depth, only excluding certain systems which couldn't be modelled due to classification and such. It also had very few bugs, making it an absolute joy to fly, which it still is to this day. That level of quality is what I expect of an ED product, based on the benchmark that ED themselves set. Not only would a DCS F-16C release in anything close to its current state be well below this benchmark, but it'd also not even live up to what ED themselves have claimed their goals are for this product on the DCS F-16C product page and in promotional videos and press materials. So my final words in this very long post is simply a plea to ED: Please do not push the DCS F-16C out of early access before it lives up to the level of quality and fidelity which the community has come to expect of ED products.