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,

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

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.

the whole thing is sooo simple. PLANNED does not mean guarantied i know ED will not do this when not nesassary, and also im sure the will make a solid patch out of it, as nearly always Keep it up ED, thanks for all the hard work. AND thx for all the years i can enjoy DCS im on since BS 1

No sweat for the delay ED, you guys are great! DCS World are what my dreams are made of! I have just finished my training in the F-14A as close as I could per U.S. Navy procedures and I'm lovin" it! Nothing like a Case 3 in pitch darkness to get the adrenaline flowing! Regards,

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

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.

05. Juli 2024 Liebe Piloten, Partner und Freunde! Das nächste DCS-Update, Version 2.9.6, verzögert sich und befindet sich derzeit in einer intensiven Testphase. Wir entschuldigen uns aufrichtig für etwaige Unannehmlichkeiten, die dadurch entstanden sind. Es ist sehr wichtig für uns, Updates mit so wenig Fehlern wie möglich zu veröffentlichen, und diese zusätzliche Zeit ist wirklich notwendig, um ein qualitativ gutes Update zu liefern. Unser Ziel war es, dieses massive Update am 26. June 2024 zu veröffentlichen, die Ankündigungen dafür waren im Newsletter am 29. März und im Newsletter am 19. April. Trotz des kurzen Zeitrahmens für eine so umfangreiche Veröffentlichung waren wir aufgrund unserer bisherigen Entwicklungserfahrung zuversichtlich, dass wir es schaffen würden. In der Tat haben wir das Ziel erreicht und die Roadmap, die wir uns selbst gesetzt hatten, fertiggestellt und sogar zusätzliche Funktionen sowohl für den DCS: CH-47F als auch für DCS: Afghanistan hinzugefügt. Einige unvorhergesehene Ereignisse haben uns jedoch daran gehindert, das Update rechtzeitig zu veröffentlichen, und wir möchten euch gerne mitteilen, was die Ursache für die aktuelle Verzögerung ist. Wie ihr vielleicht wisst, veröffentlichen wir im Allgemeinen ein neues Luftfahrzeugmodul oder eine neue Karte pro DCS-Update, selten mehr. Im Allgemeinen dauert es etwa einen Monat zwischen den Veröffentlichungen, um die nächste vorzubereiten. Ab Mai haben wir zweimal im Monat Module veröffentlicht: DCS: Kola, DCS: F-4E Phantom II und den DCS: OH-58D Kiowa Warrior. Hinzu kommen DCS: Afghanistan, DCS: CH-47F und Flaming Cliffs 2024, wobei jedes Modul seine eigenen spezifischen Eigenschaften hat, die eine sorgfältige Integration in DCS erfordern. Darüber hinaus noch die neue Air-Boss-Station für DCS: Supercarrier, viele neue Modulfunktionen und Fehlerbehebungen sowie erhebliche Verbesserungen am DCS-Kern. Wir haben unsere Kapazitäten zur Bewältigung dieser Herausforderung überschätzt, aber wir hoffen, dass ihr mit dem Ergebnis zufrieden sein werdet. Hier ist eine Ereigniszeitlinie für das verschobene Update DCS 2.9.6: Wir haben die Verzögerung im Newsletter am 21. Juni 2024 bekannt gegeben. Die Entscheidung, die Veröffentlichung zu verschieben, wurde aufgrund von 19 kritischen Problemen (Showstopper) getroffen, die den DCS-Kern, den Supercarrier, den CH-47F, die F-16C, die F/A-18C und die F-4E betrafen. Normalerweise haben wir 5-8 Showstopper eine Woche vor einer Veröffentlichung. Bis zum 26. Juni 2024 stieg die Liste der Showstopper auf 25, die sich auf die oben genannten Module bezogen, zusätzlich zu der DCS: AJS-37 Viggen, DCS: F-5E Tiger II, Flaming Cliffs 2024 und dem neuen Launcher. Bis Dienstag, dem 2. Juli, hatte unser Team ganze Arbeit geleistet, und die meisten Probleme waren behoben. Dennoch wurde beschlossen, dass der DCS: CH-47F mehr Zeit für die inhaltliche Vorbereitung und ausführlichere Tests erhalten sollte. Alles lief reibungslos auf die Veröffentlichung zu, als eine Reihe neuer Probleme auftauchte. Diese wurden am 3. Juli 2024 behoben und wir waren bereit, das Update mit der vollständigen Liste der Korrekturen, Verbesserungen und neuen Modulen zu veröffentlichen. Am Morgen des 4. Juli 2024 meldete unser QA-Team jedoch zusätzliche Probleme im Zusammenhang mit KI-Flugzeugen und einer fehlerhaften Kampagne, so dass wir uns zu einer weiteren Verzögerung entschlossen. Wir wissen, dass dies ein mit Spannung erwartetes Update ist und dass es eine Menge neuer und großartiger Dinge für euch bereitstellen wird, einschließlich einer Problembehebung für das Radar der DCS: F-15E Strike Eagle. Allerdings konnten wir das Update aus gutem Gewissen heraus nicht in der jetzigen Form veröffentlichen. Ein neuer Termin wird auf unserem Discord und anderen Social-Media-Kanälen bekannt gegeben, sobald wir sehr großes Vertrauen in ihn haben. Wir möchten uns bei euch allen, unseren Drittentwicklern und insbesondere bei Heatblur für die Zusammenarbeit, das schnelle Feedback und die Updates für ihre Module bedanken. Das gesamte Team von Eagle Dynamics entschuldigt sich für die Unannehmlichkeiten und verpflichtet sich, sein Bestes für euch und die Gemeinschaft zu tun. Vielen Dank für eure Geduld, Leidenschaft und Unterstützung. Viele Grüße, Eagle Dynamics

While there is frustration at the last second "no jump tonight," I will give credit where it is due. This level of open communication as presented in the newsletter is exactly what is needed. The hope would be to see an earlier call made to delay if needed with a newsletter providing insight as to the challenges faced by the development team. Early calls with explanation to provide context would go a long way to rebuild trust & goodwill.

Check out PROJECT VARK, we're working on getting the C model released soon; it's an awesome team. I did the 3d and textures over there

My gratitude for your amazing work and service to the community Jamie. You are the man! Enviado desde mi ELE-L29 mediante Tapatalk

I wouldn't call it magnanimity, it's just behaving like an adult and understanding that the real world is not perfect. I don't work in software development, but I work as a BIM specialist in construction. Every project can face delays, regardless of the sector you are working on. Sometimes, it's inevitable to reach a major block and that can lead us to postpone the delivery to the customer. It's not something we enjoy, but sometimes, it's just necessary in order to deliver a quality product/project My opinion could be seen as ED simping, but I guarantee you it isn't, it's just maturity, because behind ED, there are real people with real lifes that also like to rest on weekends and enjoy their free time. I'd also like to be enjoying Afghanistan map this weekend, but I can also play other games and do things outside, so I don't care if it takes a couple weeks more to iron the patch as long as it comes out playable and I can enjoy it.

Once you see the patch notes and consider all that is coming with this patch, I would not call it routine.

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.

## __**Updates between 1st May - 6th July 2024**__ Hello everyone, here are the updates so far since we've last spoken to you! - Changed to programmatic sideslip drag, removing reliance on OpenVSP beta angle parameters. - Wing divided into 4 sections, flaps given new aerodynamics. - Roll Stabilised. - Oxygen system now working. - Refactoring of dihedral effect in aerodynamics. - Elevator and center of pressure implemented. - Fixed issue with autopilot initiation and bombs not dropping. - Differential braking and brake gauges added. Braking pneumatic logic rewritten - Keybindings overhauled. - Stall behaviour and speeds improved, tailplane is also now computed from airfoil. - Fixed some broken bombs. - Reduced elevator authority and replaced briefing image. - Exhaust and engine textures added. - Autostart fixed. - Tail wheel and ground handling improved. - Minor fixes to collision model. - Oxygen system hitboxes added. - Vera livery and external model update. - flight model refactored, prop strikes now kill engines. - Radiator flap animations and pneumatics. - ID lights, Nav lights, Landing lights, model fixes done. - Landing lights now work. - Rudders converted to airfoil based aerodynamics. - Climb performance calibrated for new aerodynamics. - Landing light effect and nav light illumination added. - Wing UV adjustments and visual damage textures on right wing added. Thank you! Small dev update from discord for those without.

I don't get the irritation Last I checked: Navy planes could operate from land bases as well I currently haven't trained any other plane than the F-14 (bar spitfire and Mozzie), so in this map, I'll be operating the turkey from Airstrip E-Z-mode

Thank you for giving us the facts! And don't worry about trolls who bitch about postponed release dates! Quality should always have priority over meeting target dates.

Just a quick note, I’ve updated the Budgie main page on Github, specifically Readme.md to address initial performance issues on lower spec machines and why that happens and also a note on how bad my documentation has been since I found yet another reference to DLL injection. I’m currently coming down with the flu or something so I’m going to try and enlist ChatGPT to help proofread and ferret out any mentions of DLL injection. Regarding performance issues, Budgie keeps a record (in-memory) of everything that tries to call the time function responsible for the date based failure, the first time something new calls, Budgie essentially takes notes, this is so later on in the mission when that thing calls the function again as you’re lining up to pickle, Budgie knows it’s not the Mudhen calling and instantly responds with correct date/time. On Mission load, a LOT of things are calling for the first time and unfortunately with CPUs approaching minimum spec DCS may stutter or almost grind to a halt while this is all figured out by Budgie. While it’s not ideal you can wait it out and it should improve. We recently had a user in the discord where this took something like 2 minutes on an i5 4000 series. Having had an i5 CPU in the past I’m well aware if you push them even a little too hard you’re going to have problems. I am looking into ways to mitigate this and potentially push out an interim release before the next full patch, perhaps by writing some of the info to disk so when Budgie loads it reads from file to prime the system. This may take a while, please be patient. EDIT: The next full patch is intended to add features back to Budgie it had making it more complex and versatile, unless another module has a time/date based break I intend to release this after an official fix to be held in reserve should issues arise in the future. The complexity requires far better documentation than I can manage at the present time.

Not that I'm planning on purchasing anything coming in this update, or even know how to write code, but just wanted to say 'Thank you'! for providing some background into the unforeseen issues. @NineLine @BIGNEWY Thank you guys for all you do. You have a difficult job being the ED Forum punching bags, all the while remaining positive and professional. I'm absolutely *not* jealous of your tasks here. Id rather eat crunchy dog poop than be a ED Forums moderator...

Why on social media and Discord only?

Yeah. That is my take on it too. Bignewy said it was a blast flying and hauling cargo with. Not having a complete system means it will not work as it should. But an incognito trim system make it flyable. This is pretty much what I expected in the first place. System was a previously Chinook pilot making me aware of not many weeks ago. I knew there was a lot I did not know about this chopper. I can imagine how it flys but have no idea about how controls work. It is delayed, it is not complete and no matter how anyone feel about these facts it do not matter. It is what it is This doomsday speech is just as much assumptions as anything else. I assume you are just as entitled to assume as I am.

Watch out for the worms! Sent from my SM-A536B using Tapatalk

Did someone say Desert Carrier Ops? Now if I could only get the cats to work.....

Во наворотили. вам бы на рен тв за оплату выступать

Pretty much my prerequisities as well! [emoji1] Sent from my SM-A536B using Tapatalk

...and you are 100% sure that specific fix isn't causing one of the game breaking issues? So you can assure us ALL other modules are fine, if they do that? Or should they, maybe look at it and do some testing before rushing it out? Just saying...

I remember when beta version stopped working after an update coz ED wanted to keep the date and did not take time to test. We communicated with our pitchforks and ED improved. It is unfortunate that the new bugs were discovered, but I preferer less bugs and wait that the other way around. Besides it's just a game, that offers so much currently, updates are welcomed but quality is even more so.

@NineLine, @BIGNEWY thanks to you and the DCS Team for all the updates, outreach and being cautious. I think it's important that DCS World get it right - especially with a MRAP and Afghanistan map in the works, as well as a F-15E radar fix.

Ба... Это магазин теперь чужие фиговины чинит вместо самих Вась?

Ohhhh, I look forward to this for sure haha!

@BIGNEWY and @NineLine I read the newsletter discussing the latest DCS updates' tech issues. Kudos to the internal testing team members who discovered the technical issues before the release to the public. It is encouraging that ED's management listens to their beta testers and pauses while things are fixed. The delay is unwanted but is the better choice when many showstopper events occur. If the latest update had been released to the public with faulty programs, ED's forums would be in meltdown mode due to many posting their technical issues. Mike Force Team

I insist that upon release it have forward and rear rotor blades and can achieve flight. if that's asking too much, let me know. I don't want to come off as pushy.

It's not toxic, people are just sick of their BS. And rightfully so.

Maybe you migrated your account, started over, but you seem fresh to the DCS scene. I have been flying modules here since the only one they had was the KA-50, that was it. You missed the entire Warbird Kickstarter dust up when Ilya blew town, and left all of us holding the bag, ED picked up a bunch of unfinished code, and brought them to life. As a Kickstarter, I was promised several modules, finally got the P-47 5 years later, and damn, if it wasn't worth the wait. Still waiting for my ME-262, but not upset about it. It will happen. Maybe you missed VEAO saga also, and others I have forgotten about. If you understood the depth and breadth of everything that ED has slogged through, and they are still here, while others have come and gone, you might get an inkling of the massive undertaking they are involved with now. Compared to the lonely KA-50 and the Caucasus map, which is where it started (even earlier actually), the pace and content they maintain is incredible. In the meantime, I fly the A-10C, P-47D, Dora, F-4E Phantom, Huey, and/or many more. I have dozens of other modules gathering digital dust I could explore while we wait. Yeah, the F-15 E is disappointing, but I am holding on to mine, it will get worked out one way or the other. Plenty of other things to do, so I get your point. But look around you, tell me, where else would you go to get this experience?? Fly another module, enjoy that new Kola map, fly Grey Flag or other Multiplayer servers, join a Discord DCS community. We will get all our toys in good time.

ED should take the “Scotty” route on Star trek. Tell Captain Kirk that it will take two days to get the warp engines back online, knowing that it will take 18 hours to get it done. Commander Scott knows if all goes well, success can come sooner but knows that glitches can arise so he extends the time frame to accommodate these glitches. Now, if he can get things running under the time frame, he’s a miracle worker, if not and he completes his task with his sublime timeframe, he kept his word. ED optimistically puts in a time frame, particularly ignoring the glitches which causes these unwanted delays. However, this is not Star Trek and people’s lives are not on the line but psychologically speaking, the results are the same. When one group sets a goal and date to reach this goal and falls short, people on the receiving end think about the same. Just my humble take on things. If you like or don’t like what I say, ask me if I care.

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 приносит извинения за неудобства и обязуется сделать все возможное в минимально необходимое для этого время. Спасибо за ваше терпение, энтузиазм и поддержку, Искренне Ваши,

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!

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

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.

@YoYo Isn't that the "Missiles Per Code" on the "Weapons BIT/Set-up Page"?

Unfortunately, it is much safer and more effective at this time to use a low altitude (>500ft), high speed strike with mk20s than to use shrikes to attack sam sites. Even when defended by AAA, a fast (<500 kts tas) run in with a salvo of 12 mk20s assures great results with barely a scratch on the phantom. I prefer popping up to 2000 ft agl about 7 miles out and using DT for delivery, as laydown requires a very precise profile, which is not very easy to attain in this setting. The key is remaining very low until pop up at about 5 miles out so as not to alert the defenders to your presence until the last moment.

Thank you for prioritizing quality above arbitrary dates! Thank you for transparency and clarity and communicating this publicly to your customers and partners!

Сброс триммера, насколько я понял, включается перед отключением АП, а не перед включением. Это всего лишь согласование положения ручки виртуальной и ручки физической. Тут дело в сбросе триммера или еще чего-нибудь. Баг в самом включении автопилота, а точнее в "активации" в нем положения, которое он должен удерживать. Я сейчас не могу записать трек, но может у вас получится. Достаточно выбрать горячий старт на полосе (стоянке), далее отключить каналы автопилота, зависнуть как удобно (с триммером однокнопочным, восьмипозиционном или вообще "на руках", удерживая джойстик в нужном положении), а далее просто включить каналы К и Т. Если планки станут на упоры, то это баг.

Get well Jamie! [emoji1695][emoji1303] Sent from my SM-A536B using Tapatalk

Ерунда. В мире компьютерных игр ( а как не крути, а у нас именно компьютерная игра), перенос сроков выхода чего-то там абсолютно естественное и распространенное явление и ни на чью деловую репутацию никогда не влияло. В отличии от свинского поступка Разбамов.

As per @MiGCap1 - take your time - get it right. In the scheme of things with so many recent additions - what is a few weeks? Your efforts very much appreciated.

Thank you for the transparency and update. As a former Alpha and Beta tester for another major sim title, I know how frustrating it can be when, despite massive amounts of testing, bugs pop up at the last minute.

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!

The other issue here that i see, well i am not even sure if this is an issue, but to me, ED really needs to understand that the F-16 is an iconic aircraft, it is not just another module where you can make profit off. This airplane is like the F-4, it made generations dream and still does. Having an aircraft like that not being taken care off like it deserves is hearth breaking. The F-16 constantly feels like it is hiding in its own shadow in DCS. This is also one of the main reason why people are so upset.

This is just an example how the tail section textures should be uv-packed. This leads to an 33% increase in pixel resolution aka sharpness aka crispness on each surface. This is just puzzled together quickly with Photoshop...