Leaderboard

05 July 2024 Dear Fighter Pilots, Partners and Friends, The next DCS update, version 2.9.6, has been delayed and is currently in heavy testing and bug fixing. We sincerely apologise for any inconvenience this may have caused. It is very important for us to release updates with as few issues as possible and this extra time is genuinely required to deliver a quality product. Our initial aim was to release this massive update on 26 June 2024 and the announcement was made in our 29 March 2024 Newsletter and 19 April 2024 Newsletter. Despite the short timeframe for such a large release, we were confident we could do it based on past development experience. Indeed, we reached our internal goal and completed the roadmap that we set for ourselves and even added additional functionality to both the DCS: CH-47F and the DCS: Afghanistan map. However, some unforeseen events prevented us from meeting the schedule and we would like to share with you what caused the current delay. As you may know, we generally release one new aircraft module or map per DCS update, rarely more. In general, it takes about a month between releases to prepare for the next one. Starting in May, we released products twice a month: DCS: Kola, DCS: F-4E Phantom II, and the DCS: OH-58D Kiowa Warrior. These were planned to be topped with DCS: Afghanistan, DCS: CH-47F, and Flaming Cliffs 2024 with each product having their own specific features requiring careful integration into DCS. This is on top of the new Air Boss station for DCS: Supercarrier, many new module features and bug fixes, as well as substantial improvements to the DCS core. We overestimated our capacity to meet the challenge we had set upon ourselves but we are hopeful that you will understand our decision. Here is the event timeline for the delayed DCS 2.9.6 update: We announced the delay in the 21 June 2024 Newsletter. The decision to postpone the release was made based on 19 critical issues (stoppers) related to the DCS Core, Supercarrier, CH-47F, F-16C, F/A-18C, and F-4E. Normally, we have 5-8 stoppers a week prior to a release. By 26 June 2024 the list of stoppers had increased to 25 related to the above products, in addition to DCS: AJS-37 Viggen, DCS: F-5E Tiger II, Flaming Cliffs 2024, and the new Launcher. By Tuesday, 2 July, a tremendous job had been accomplished by the team and most of the issues were resolved. Nevertheless, the decision was made that the DCS: CH-47F should have additional time for content preparation and more detailed testing. Everything was moving smoothly when a new set of issues reared their heads. These were subsequently resolved on 3 July 2024 and we were poised to deliver the update together with the full list of fixes, improvements, and new products. However, by the morning of 4 July 2024 our QA team reported new stoppers related to AI aircraft in addition to a broken campaign and so the decision to further delay had to be made. We know that this is a very eagerly awaited update and that it will provide a lot of new and great stuff for you, including a fix to the DCS: F-15E Strike Eagle radar. However, in good conscience we simply could not let the it go out as is. A new date will soon be announced on our Discord and other social media channels once we have very high confidence in it. We would like to thank you and the Community, our third party developers and especially Heatblur for their cooperation, rapid feedback, and updates on their aircraft. The whole team at Eagle Dynamics apologise for the inconvenience and undertake to do their very best. Thank you again for your passion and support, Yours sincerely,

Please do not share Dates or other Information on external platforms such as Discord or Facebook. This is your Website! And this is where the Music plays and not on external platforms that do not belong to you.

There has been quite a few messages since my last reply, and it feels like some people in this thread think I mention all the systems I did in my post merely because I want to sit and LARP useless features, and I can tell you that this is definitely not the case. All the items I've mentioned have a direct impact on the combat effectiveness of the DCS F-16C, as well as the user experience. That is why I mentioned the things I did. As it stands currently, the DCS F-16C is unable to employ most real world tactics due to there being so many missing or inoperative systems, and its performance in combat is therefore very lackluster. It doesn't matter if you're doing BVR, WVR, SEAD, AI, or just hurling some bombs on a target. There's always several aspects of this aircraft that's missing or not working correctly, limiting your combat effectiveness in each of these roles. In my post I also put special emphasis on the SEAD role as, after all, this is the primary role of the F-16CM-50, and the DCS F-16C's performance in this role is woefully inadequate. You also have to remember that the combat environment we have in DCS is quite dated and sterile. In the 2007-era which the DCS F-16C is based on, you'd have much more capable weapon systems to face off against, which for the SEAD role would include things like both datalinked and home-on-jam SAM missiles, integrated air defense networks with intelligent and coordinated SAM operators, GPS and communications jamming, ground based radar decoys, etc. That is why I really appreciate when ED models things in depth, like the INS and its fix functions as well as GPS reception, which now enables the future addition of things like GPS jamming, which is a staple of modern warfare that even civilian aircraft and airliners have to contend with on a daily basis. And if we get GPS jamming, this also highlights one aspect of why the Digital Terrain System is important, as it, amongst many other things, increases the INS accuracy over topographically varied terrain. And all of a sudden, this has ripple effects into mission planning, where you might choose to ingress towards a target over more rugged terrain if you expect to encounter GPS jamming in order to maintain higher INS accuracy, rather than ingressing over the flat desert or ocean and having to do manual INS fixes, or it might affect which weapons you choose to employ, opting for LGB's instead of JDAMs, or it encourages you to actually make use of Offset Aimpoints or VRP/VIPs when engaging targets, et cetera. Just with the addition of a few systems, it makes the experience so much deeper, and it also gives you very good reasons to learn your aircraft more in-depth and to actually make use all the functions that have already been implemented into this product to their full potential. And for those who mainly want to hop in their jet, fly out to the range in a sterile environment, and drop some bombs on targets to blow off some steam after a hard days work, they can still do that. But it also allows people to get so much more out of the product, to get more invested into DCS as a platform, to increase customer retention, and in the end increasing future revenue for ED. These dedicated people who go in-depth are also usually the ones who creates a lot of content which benefits the entire community, stuff like tutorials, complex missions and campaigns, video content, etc., which entices new customers to join the fray and turns their toe dipping in DCS into a full submersion. And certain items I mentioned, like having a damage model, doesn't increase combat effectiveness, but it is of course an important aspect of combat. As it is right now in the DCS F-16C, the "damage model" is basically a big boolean. Either you audibly hear things hitting your aircraft, but not a single system is affected, or you die. Compared to other ED airframes, like the DCS A-10C or DCS F/A-18C, those modules actually model individual systems getting damaged, and you might actually end up utilizing emergency and backup systems to limp your jet back to base, and you might actually need to use your knowledge about how the fuel, hydraulic and electrical systems work in order to survive such an ordeal, isolate busted fuel lines, circumvent broken systems and components, etc. So when people claim the DCS F-16C has a damage model, that is simply not true because none of these things exist in what we currently have.

Why on social media and Discord only?

At the risk of getting myself another 40pts for sharing my opinion I’d like to know where we’re supposed to be getting ‘official’ news on everything? I don’t use discord, never had a FB or Twitter account but I have paid a fair few quid on DCS. I’d have thought this would be the place to go? I’m not bothered about waiting for updates or whatever so long as they’re dealt with better. Setting dates and making a big deal of it is setting yourselves up for all the nonsense. Having to go hunting to find out what’s happening isn’t what I wanna be doing so I don’t, I come here. Thanks to everyone for reading, apologies if anyone feels offended or upset and I wish everyone all the very best.

Don't understand the negative responses to be honest. I'd rather a working patch than one that breaks aspects of the game that was released to satisfy the impatient. Take your time ED, get it right even if it takes weeks rather than days. I will enjoy flying what I already have in the meantime.

Dear DCS Team, I believe there is a vast community of users who, like myself, commend you for your transparency, your efforts to satisfy us, and the unparalleled results we enjoy. Considering the remarkable goals already achieved and the complexity of the project, a few delays are normal. You can count on our patient respect.

Wow, so a special thread was created for people to vent on missing update? There was a plan for an update and ED told us the planned date. Testing revealed signifact enough bugs so the update got delayed. Everything works as intended - what's the problem? Can they not announce updates? No. Can they foresee problems? No. Can they push bad update? No. But they can do hotfixes! Some showstoppers like F-15E radar should be hotfixed asap.

Тут на форуме по сабжу сломано копей уже на гигабайты трафика. Мне кажется, каждая точка зрения верная, просто не учитывается данный аспект: В есть качественный лаг между синими и красными. Вы говорите, что, если хотите летать на равных простив синих - ставьте синих чуть более старших. Ок, к этому вопросов нет. Проблема в том, что есть много синих модулей, против которых по этой вашей формуле поставить нечего. Вот и получается, что куча людей накупило эфолёты, и сейчас геймплей сводится к какой-то заварушке внутри блока НАТО. Поэтому люди, которым интересна красная сторона, и ддосят этими просьбами.

I have the feeling they reacted to the Razbam drama by overpromising a lot of stuff, like saying "we're here, all is good, check all these coming things". And now reality has catched up. Nothing wrong with a delay to improve things, but failing deadlines over and over again makes you look like a bunch of amateurs.

Confident ED will update us when they have the information. Thanks for the communication. We'll get there. In the mean time, go outside and spend time with your friends and family, lol

Will the new date be announced here on your official forum as well, or only on social media?

This is the intro video of Mission 1 of the MIG Killers DCS F-4 Campaign. In 1969 the first Topgun course began with a fam flight, where the instructor sat in the front with the student in the back. He demonstrated some confidence builder maneuvers, they landed, switched seats and then the student performed them. It's interesting to note that during the regular training course Naval aviators hadn't really been allowed to push their F-4s to the edge of the envelope, so some were taken by surprise when the instructors zoomed up until the jet ran out of airspeed and slid back tail first. Due to DCS limitations the players can go through the first part of the fam flight in the form of this video. The actual mission will start after the instructor and the student swapped seats, and the jet has been refueled. Enjoy!

Since @BIGNEWY was kind enough mentioned that their upcoming patch is BIG (a MOAR?), we can happily guess (without any actual knowledge!) what such a big release may include: Gobsmackers - Hook - 'Stan - Kola "Winter Soldier" - SupCarrier changes - FC 2024 - Maybe even some bug fixes to some great modules, e.g. - Mudhen Radar - Kiowa crew "Talked About" - Sinai first patch (one year worth of updates, may require map tech) - Iraq Even More Highly Speculative - some new map tech - some new weather tech - Airport AI - Vulkan - MT for servers - new campaigns - New Campaign Engine (included just for laughs, I know) - Persistence (again, just for laughs) or, plainly, a "DCS 3++"? That list above is indeed much too big to handle for anyone who strives to preserve their sanity. So, I agree with @YoYo's assessment that ED's products have grown too large to be managed in 'Big Block' releases. I'm thinking that they could investigate a multi-track release train, one for technology/bugfixes (the "world" track) on a 4-week schedule, and a "feature" track that has a distinct schedule that does not coincide with the world track. So if a feature has dependencies on a world feature, it will always come at least a week after a world release that enables it. No matter what, I'm happy to wait for the new patch, and I merely wish that ED would simply communicate more, and better include their Forums so dinosaurs like I who don't frequent discord, Facebook or Twitter can also be up to date. Good luck and Godspeed, ED - and let's hear a bit more about what you got in store for us

For ED - maybe it's worth considering whether the current policy is good, because as you can see, it simply doesn't work. Unfortunately, for the last 2-3 months, basically everything has been postponed (I think only Kiowa was on time). Maybe it's better to adopt the strategy that is in MSFS, so: 1/ SimUpdate - patches, 2/ World/Content update - maps, new content, new modules, but not improvements (based on the current SDK from the last patch) Of course such a „World Update” requires a new version of DCS, but it does not contain improvements that can break DCS and other things. This approach will allow for more flexibility, while not affecting the release of an expansion, campaigns, or anything else (new content) that is bug-free. Personally, I understand that some improvements could have messed something up, but this just shows that the current policy is bad, because it causes ED to miss the deadline, and it causes frustration for people who bought something and don't get it on time. So, maybe the strategy proposed by Microsoft is better - in the other times new things come out, and other times there are patches with fixes. thanks to this, the patch does not affect the timing of new modules which are ok. A request to consider whether it can be separated into SimUpdate and Content update (without improvements) for the future. I think the division in MSFS (SimUpdate / Content update - the first one contains engine fixes and is released less frequently, the second is new content.) suits me better, at least it's a bit more predictable and less painful if you have to wait, and on the other hand it gives more flexibility for the publisher.

Guys, it’s a game. It is supposed to be fun and entertaining. It is just postponed and in the meantime, the game still works.

Kleine Impression vom Model Viewer: Roie, unser CO-Piot macht sich vertraut mit der BO

Are you tired of going barreling into the enemy IADS with no one at your back? Do you feel visceral anger when a search radar pops up on your RWR? Do you have a tattoo of the inverse square law on your lower back? If so, you're in the right place. Introducing the EF-111 for DCS, available soon as an AI asset. Still working on a few things, but it should be ready for release in the next week or two. The long term plan is to make it flyable and clickable. I'm in the VERY early stages of making that happen so don't expect anything for the next year. If you have any questions hop over to the discord https://discord.gg/HZYvhwMKxs

More German pack assets, the Skyshield with FCU and Revolver Gun Mk3 effectors.

This is the intro video of Mission 1 of the MIG Killers DCS F-4 Campaign. In 1969 the first Topgun course began with a fam flight, where the instructor sat in the front with the student in the back. He demonstrated some confidence builder maneuvers, they landed, switched seats and then the student performed them. It's interesting to note that during the regular training course Naval aviators hadn't really been allowed to push their F-4s to the edge of the envelope, so some were taken by surprise when the instructors zoomed up until the jet ran out of airspeed and slid back tail first. Due to DCS limitations the players can go through the first part of the fam flight in the form of this video. The actual mission will start after the instructor and the student swapped seats, and the jet has been refueled. Enjoy!

Im with you I think this should be the place to come for proper updates, you wouldn't want to any where near the ED Discord anyway its full of 12 year old's in the main channel anyway, a couple of the specific topic channels are ok though in small doses.

So, definitely not going to take the time to read through all the drama that this has caused, but I will second the motion of stop announcing a date you’re going to release something until it’s ready to go. I like a lot of people am a heavy mod user in my personal use of the system, so when getting ready for an update, I disable all my mods and update on a clean install. The process to reenable them takes hours. So, now that I disabled them all this morning, prior to this thread being posted…well, you know where I’m going. Lesson learned though, next time I won’t disable everything until I know that the update/patch is live. How about you get your patch or update, or product ready to be released and then announce that it will be released in 72 hrs…

ED Model Viewer Co-Pilot Setup

As I see it (as an ex-IT guy), the ED coding staff is too small, improperly managed, and QA is missing (which dumps QA on us.) I was a developer back when the IBM 360/370 was THE thing. Nothing I ever released had coding flaws in it. A customer would want more things added but that usually brought about a weekend addition followed by a six week QA check. There was no such thing (back then) as a Beta release. All of it was a finished thing. If we said that "it" did something, and it didn't or created a problem, the company's name was mud and died off. Coders, Docs, System Analyists, DP managers, and company owners/operators rarely made it back into the "known" IT world. Sometimes, good ones ended up at university, changed careers, or retired. Idiots would work until burn-out and quit. I got burned out and tried several years lecturing at colleges and university, and quit anyway. ED is the ONLY mil-sim able to give us what we all want. ED is seriously flawed. We all just have to live with it and enjoy the miracles ED produces in the manner in which they produce.

Good decision. It's better to wait for a refined update than to cry that new bugs have appeared.

All the new users advising that patches should be smaller, faster, and on a shorter schedule - That, is how we got here, no longer feasible. Basically 9 pages of: 1.) Those who have developed software, or worked on large complex projects - "Thanks for the update, would rather released clean and no show stoppers." 2.) Those that see anyone in the above group as "Shills and Fanboi's for DCS." I am in the first group. Thanks ED!!

That's IMHO an unwarranted assertion, unless you can point to some tangible proof. A software company heralding back to the 90's of last millennia is unlikely to have gone Agile, plus in my (some 30 years of large-scale project management) experience, the advantages of Agile are massively oversold by consultants trying to sell some "methodology of the year". There are advantages to Agile if you are start-up, and your teams and release train can cover the entire product. That is highly unlikely in what we see in ED's modus operandi today, and my guess is that they employ a development methodology that they deem best fitting for their current product portfolio. Yes, and above only applies if you develop large monolithic blocks. That's not the Agile way, as you should know, so you are somewhat contradicting yourself. "Release early, release often" is an Agile Motto, and you only pull from your Backlog what can be done in 2 Sprints. The Definition Of Done usually includes "tested" (unless your Scrum Master loves living on the edge), and in your Sprint Reviews you'll note when something isn't up to snuff and shove it into the next sprint until it's really done. The idea of Agile is exactly that you can rapidly release stuff without show-stopping bugs. But yeah, I'm the first one to agree that "Agile" is just an oversold fad that doesn't work will in large (i.e. non-startup) projects, no matter what that McKinsey guy sold the CEO.

If you want to sue us, then do so. That's the official Heatblur statement. Stop this nonsense, it's not productive. If you don't trust the "closed source packer" by Eagle Dynamics then why are you running any DCS code at all on your computer!?!

Согласен, бывает берешься за работу которая визуально максимум на день, начинаешь ковыряться - там дай бог за неделю справиться. А тут вроде все взрослые дядьки, а расстраиваются как дети малые), ну сместилось и сместилось, как говорила классик: "жили небогато и нефиг начинать".

I can safely speak for me and BN, we DO NOT enjoy drama... at all.

Stable Version Current version number: 2.9.5.55918 Next planned update: To be announced Dear All, We regret to inform you that additional time is required to thoroughly test the recent fixes, necessitating another delay. We will communicate the new patch date as soon as the tasks are completed. Thank you for your understanding and continued support. Eagle Dynamics

Oh my, the entitled drama....

05 июля 2024 года Дорогие друзья, Сообщаем, что объявленное ранее обновление DCS до версии 2.9.6 было отложено и в настоящее время проходит тщательное тестирование и исправление ошибок. Приносим искренние извинения за доставленные с этим неудобства. Для нас очень важно выпустить обновление с как можно меньшим количеством ошибок, поэтому требуется дополнительное время для доведения продукта до нужного качества. Нашей первоначальной целью было выпустить это масштабное обновление 26 июня 2024 г. Об этом мы сообщали в новостных письмах от 29 марта и 19 апреля 2024 г., и несмотря на весьма сжатые сроки для такого большого выпуска, мы были уверены, что сможем сделать это. Особенно с учётом нашего большого опыта в разработке. И мы действительно достигли поставленной цели и даже добавили дополнительный контент: модуль транспортного вертолёта DCS: CH-47F и карту DCS: Афганистан. Однако, как часто бывает, непредвиденные обстоятельства помешали нам уложиться в объявленный график выпуска и ниже, и мы хотели бы объяснить почему. Как вы уже возможно заметили, обычно мы выпускаем один новый модуль летательного аппарата или карту при обновлении DCS, редко когда больше. В целом, между релизами проходит около месяца и нам достаточно времени, чтобы подготовиться к следующему. Начиная с мая, мы выпускаем по два модуля в месяц: DCS: Кола, DCS: F-4E Phantom II и DCS: OH-58D Kiowa Warrior. На этот релиз планировался выход карты DCS: Афганистан, DCS: CH-47F и Горячие Скалы 2024. Причём, каждый продукт по-своему уникален и требовал тщательной проверки для интеграции в DCS. При этом, мы дополнительно решили выпустить и давно разрабатываемое дополнение для DCS: Supercarrier в виде рубки руководителя полётов (Air Boss), расширить функционал уже существующих модулей, улучшить производительность игрового ядра и исправить найденные ошибки. Получилось так, что мы недооценили нагрузку от поставленных перед собой задач на этом краткосрочном участке и надеемся, что вы поймете наше решение. Ниже отчёт по событиям при тестировании обновления DCS 2.9.6: Первый раз мы объявили о задержке в новостном письме от 21 июня 2024 года. Решение отложить выпуск было принято на основании обнаруженных 19-ти критических проблем – в среде разработки мы называем их стопперами. Они были завязаны на баги во всех компонентах DCS: игровом ядре, дополнении к модулю Supercarrier, летательных аппаратах CH-47F, F-16C, F/A-18C и F-4E. При этом обычно, за неделю до релиза, у нас редко когда оставалось более 5-8 стопперов. К 26 июня 2024 года список стопперов увеличился до 25, относящихся к вышеуказанным продуктам, а также к обновлённому функционалу DCS: AJS-37 Viggen, DCS: F-5E Tiger II и модулю Горячие Скалы 2024. Дополнительного времени потребовал и впервые разрабатываемый для DCS лаунчер. К исходу суток 2 июля, команда проделала колоссальную работу и большинство задач было закрыто. Тем не менее, оставались проблемы с новым DCS: CH-47F и мы решили, что необходимо выделить дополнительное время и сдвинуть его срок релиза, для доводки вертолёта и более детального тестирования компонентов. Далее все вроде бы шло по плану, однако обнаружилась новая группа проблем. Они были решены к исходу 3 июля 2024 года, и мы были готовы выпустить обновление вместе с полным списком исправлений, улучшений и новых модулей. Однако к утру 4 июля 2024 года наша команда контроля качества сообщила о новых проблемах, связанных с самолётами ИИ и серьёзным багом в одной из обновлённых к этому релизу кампаний – нам в очередной раз пришлось принять решение о сдвиге сроков. Мы знаем, что это долгожданное обновление, которое принесёт вам много нового и интересного, включая исправленный силами ED радар на DCS: F-15E Strike Eagle. Но, мы не можем выпустить апдейт с серьезными багами. Новая дата скоро будет объявлена в нашем Discord канале, форуме и других социальных сетях, как только мы будем в ней очень уверены. Мы хотели бы поблагодарить вас и всё сообщество, включая наших сторонних разработчиков и особенно Heatblur за сотрудничество, быструю обратную связь и обновления. Вся команда Eagle Dynamics приносит извинения за неудобства и обязуется сделать все возможное в минимально необходимое для этого время. Спасибо за ваше терпение, энтузиазм и поддержку, Искренне Ваши,

New cup holder in the KA50

Seriously though, I get it, privacy is important, and safety of your hardware, data, computer is important. Full stop. But Heatblur Simulations does not ship malware to your computers. Period. Talking about some magical, hypothetical court case about us shipping malware is not productive and is just frustrating. Why would we, Heatblur Simulations, after 11 years of working hard to build our reputation and put every single fibre of our being into our products decide to start shipping viruses or spyware to customers? To a small flight simulation niche, at that? It makes no sense. What would we possibly stand to gain? The simple answer is that we don't, and if we do something that you guys are unhappy with, we will take steps to try and amend and fix it.

Not all heroes wear a capeTM

I believe that this approach is doable only when nothing in the module depends on new core features. And even then it’s not bulletproof - SU15 has been delayed multiple times. If hordes of devs and PMs in MS are unable to properly estimate amount of work and even then some bugs pop up then how do you think ED can do is? Geeez, I really hope people from the forum will never get anyone pregnant because pregnancies have a tendency to not follow the schedule. Not to mention late periods…Too soon?

i am simply going to say I am disappointed.

Public beta with such a quick patch cycle isnt possible now, DCS has grown way to big and it is very complex. Beta or stable in this case it does not matter it would have been delayed. thank you

I don't even think it's the frequency of the major patches. It's the infrequency of smaller hotfixes in-between that contribute to the high frustration levels. Waiting weeks for an comparatively easy fix for a bug that prevents you from using a module or playing a campaign for no apparent reasons (=reasons not transparently communicated to the customer) is irritating.

From my point of view, the underlying problem is that ED has no competition, it is the only one on the market for semi-realistic combat flight simulators. In other types of markets where there is competition and the actors make an effort not to look bad with their clients, (who are the ones who feed them) this type of deficiencies (constant postponements) make them fall to the basement of the market, leaving them, as is now the case, without any credibility, I like to compare ED's behavior with really professional companies, ED always loses, always. That is to say that we, the clients, have to wait and nothing more, if you don't like it you put up with it (take the dog to the park, start playing and keep quiet) because you have no other option, it is already known that when ED proposes a date you will be a silly if you believe him, ED NEVER keeps his promises or his dates. But it's better to wait until the patch is good and doesn't break anything, of course it does, but in the end every patch ED release breaks something else, doesn't it? But I repeat, if you don't have it ready, don't publish it. On the other hand, it is true that patches are a series of fixes, fixes and more fixes, the improvements or innovations are almost nil. As I said at the beginning, everything happens because ED has no competition. (Google translator)

They should be much better at predicting a realistic release date. Now announcing a delay the second day in a row, merely few hours before anticipated release seems to me that they have no clue about current state of the patch. Kola map update end of June - Nope CH-47 EA release end of June - Nope Afghanistan Map EA release end of June - Nope F-15E Radar fix - Nope General updates to the rest - Nope

Nobody's ever going to be upset about playing a less buggy patch, but that's not what this is about. This is about ED setting dates a month in advance, and not being able to hit even the simple date which was going to be for a patch. On top of that, when the delay is only 1 day (which they must say for a reason) and for them to go "oh sorry another big bug came up" last-minute signals to the entire community they don't have it in order. That is what people are upset about, constant promises ED cannot deliver upon. ED desperately need to overhaul how they compile and test patches, and how they subsequently set deadlines. They cannot keep leaving the testing to the last days because time and time again bugs pop up (as happens during testing) and the release dates for even regularly schedules patches gets blown past. They need to get their stuff in order if they want to save any bit of face at this point, the excuses have worn out.

Yes, most of us would I guess. However more than one thing can be true at the same time. The way this constantly happens with ED with almost everything they announce, whether module EA release,normal patch, Q&A newsletter answers ,whatever you name it , points to systemic organisational/planning issues. Which is why people are getting annoyed. Its not because they delayed this one patch. They delay everything and usually more than once and usually at the last minute. Its not the first rodeo and it seems ED is not really learning from their experience. I totally get why people react negatively.

Can't make this stuff up. They should stop announcing anything, can't take them seriously anymore anyway at this point. I get that its software and unexpected things do pop up, but the frequency , not to say consistency with which these busted release dates and last minute patch delays happen with ED seems to point to serious planning/organisational and QA issues.

As a SW developer myself, I don't necessarily agree with ED's priorities in some areas (longstanding bugs in older modules), but delaying a release...? No problem, I'll wait. Sure, I don't plan vacations according to their announced dates, maybe that's it. I understand people eagerly anticipating new things, e.g. the Hook or AF map but I don't understand the traffic (and the style of the traffic) that happens on this forum every time something is delayed or postponed. I'm looking forward to the next patch, whenever it comes. Better late than sorry, indeed.

It will be heare as well as always: https://forum.dcs.world/topic/233848-patch-status/?do=findComment&comment=5472954 Yep, absolutely, going out with my love tonight. Enjoy your life folks!

We know these delays are disappointing and we are sorry for them, but if we find issues that can not be fixed in time it would not be right to push the issue out to you folks. Delaying is the best option. thank you

I’m glad they’re not pushing out bad patches just to hit a deadline. But, it might be a good idea to hire a decent project manager to run this stuff, it’s making them look like a bunch of amateurs.