Leaderboard

new OH-58D video

Here’s a tutorial on how to start the F-14 Tomcat from a cold start, following the NATOPS checklist and real life procedures, with all the tests and checks explained. I hope you find it interesting and helpful.

Hi. This mod is adapted from KA-50_2 to display the HUD, PUI-800 Weapon Display and Shkval screens in English. This is the list of translations: HUD: Auto-Tracking: ТА to AT Memory Mode: П to M Laser Range-Finder Active: ИД to LA Beam-Riding Laser Channel Active: ИУ to LC Pause: ПАУЗА to PAUSE R-ALT Symbol: Р to R INU Normal Warm-up: ИКВ НВ to INU/NW Processing Target Point: ОТ to PT Updating Coordinates: КОРР to COOR Launch Authorized (Shoot): С to S Training Mode: ТРЕНАЖ to TRAINING Ground Collision: H to G Weapon Types: IGLA, RKT and AT (Anti-Tank) SHKVAL: TG Symbol (Ground stabilized): ТГ to ST TA Symbol (Auto-Tracking): ТA to AT P Symbol (Memory mode): П to M C Symbol (Launch Authorized): С to S Ground Collision: H to G PUI-800 Rockets: НР to RK Anti-tank Missiles: ПС to AT Bombs: 6Б to BB Gun Pod: ПП to CP Missiles: supposed to be "AA" but there's a little bug there. You'll see "AM" or something like that. SOME IMAGES: And a sample video from Black Shark 2 (Duration 4:49) NOTE: This mod will not pass the Integrity Check! DOWNLOAD: DCS: BS3 (KA-50_3) English HUD, Shkval & PUI-800 Mod v1.0 | Released: 12/2022

That seems like a pretty severe overstatement.

I just tested and have to agree that there is a massive performance impact in VR especially the CPU frametimes suffer: F18 caucasus ready on the ramp: 2.7.18: CPU 12-14ms 2.8.1 CPU 14-18 ms and this on my machine 5900x / 4090. Just switched back to stable. It was smooth and also looks good. The whole mess began with 2.8 and dynamic weather. Where does the up to 4 ms CPU frametime hit come. I don't think, that just some have a performance loss in VR, I think that only some check their frametimes and only this folks are crying out loud now. The others who don't measure the frametimes are quiet There is a massive loss of FPS on same settings, and this does not make me happy ED! Insert an optional button for dynamic weather or do something to bring back some FPS. There is a promise to bring a VR performance increase since 4 years, but it never hit the ground. This is very frustrating! I mean a 4090 and a 5900X should be fine to play 45 FPS under all circumstances. You read right, i don't even demand 90 FPS, I am fine with smooth 45 under all circumstances. But not even this is possible. Example: Sedlos Eastern Friendship under 2.7: smooth under 2.8.1: stuttering in the ground attack in the first mission Do you recognize something? Smooth under 2.7 - not smooth under 2.8.1. Something is messed up in 2.8.1!!!!!

Modern Missiles Mod - Updated 12/01/2023 v1.30 Modern Missiles v1.20 (digitalcombatsimulator.com) This mod is already included in the CFT mod and is not required if you have that installed. This mod will swap out the AIM-9L / AIM-9X and/or the AIM-120B for more advanced versions of the missiles. Specifically the AIM-9X-2+/AIM-2000 IRIS-T/PYTHON-5 and the AIM-120D. It involves swapping out models and lua files that have been adjusted for the new missile data This allows these missiles to be used on aircraft such as the F-15C, F-16C and F/A-18C/D/E/F/G. Since the missiles replace stock versions in DCS, the avionics for the aircraft will still show the old versions. However, they will look and perform like the new versions The mod includes new models, textures, modified LUA files and for the AIM-120B the mission editor icon along with scripts to swap them out or restore the original files. Includes weathered USAF textures for AIM-120 series missiles. All required textures have been added to the AIM-120.zipfile which is already loaded by DCS. The original is included and restored when the AAM_AIM_120B script is run. I've found that for the F-16C and the F/A-18 fuselage stations, the mission editor labels them as AIM-120B's. The F/A-18 pylon stations show them correctly labeled as AIM-120D. The primary limitation for the AIM-120D seems to be how far away you can get lock with the FCR. Max range of the missile is listed below but the farthest I've been able to get a lock with the Viper so far is ~70 NM which resulted in a kill. NOTE that because of the way DCS works (mysteriously sometiems) some of the information seems to be ignored in the modified files, such as the name I detailed above. This is the best implementation I've been able to get so far. Tests with current settings. All tests completed with targets at co-altitude ~32k feet in afterburner from an F/A-22A which has a RADAR based on the F-15C module. Results will vary based on the launch platforms RADAR. TYPE HOT ASPECT COLD ASPECT AIM-9X-2+ - 16.5 NM 18.0 NM AIM-120D - 95.5 NM 40.0 NM (INITIAL RADAR LOCK) There are also performance improvements to the AIM-9M. INSTALL INSTRUCTIONS: Use a mod manger to enable/disable the mod. It's built as OvGME ready and the folders and files are installed to your main DCS install. MANUAL INSTALL: The zip contains the following folder and file structure: AAM_AIM_9L.cmd AAM_AIM_9X2.cmd AAM_AIM_120B.cmd AAM_AIM_120D.cmd AAM_AIM_2000.cmd AAM_PYTHON_5.cmd AAM_Readme.txt Place these in your DCS main folder at the root (same place that sutoupdate.dat is located) Copy these folders to the same root location and overwrite when prompted. Bazar CoreMods MissionEditor USE INSTRUCTIONS: Run the script for the missiles you want to use and it should copy them. Script files to swap out the AIM-9L, AIM-9X, AIM-120B for other missiles. This includes models, textures and a code change for each. AIM-9L Back to stock AIM-9L and AIM-9X. AIM-9X-2+ AIM-9L becomes AIM-9X and AIM-9X becomes AIM-9X-2+ (Improved over the F-22 Enhancment Mod 9X-2) AIM-2000 AIM-9L becomes AIM-9X and AIM-9X becomes AIM-2000 IRIS-T (Same as in the JAS 39C Mod IRIS-T) Python-5 AIM-9L becomes AIM-9X and AIM-9X becomes Python-5 (Same as in the LAHAK SUFA Mod) IRIS-T Credits to the JAS39 Community mod. Python-5 Credits to the LAHAK SUFA mod and №15 | Neoshot (FC) AIM-120B (Back to stock) AIM-120D (Replaces AIM-120B with AIM-120D) If for some reason, the script isn't working, copy the contents of each folder into your DCS main installs corsponding folder. Bazar > Bazar CoreMods > Coremods MissionEditor > MissionEditor To restore everything to normal, repair DCS (Only needed for a manual install) or copy the original files back in place. The mod has a backup of all original files that are changed.

Thank you all for your reports We found some INS issues in cold start alignment and autoturn to target. Fix will be in January. Until this fix, I recommend using hot start if you need INS. If not, you have the ABRIS with satellite navigation that does not have deviation.

Today I learned of the passing of Olivier Balland, known as Olivier Gaming or HODGY... Olivier kindly recorded the lines of MAGIC for mission 12 in Bold Cheetah, and helped me a lot in Beta Testing. In the DCS community, he was a star, helping so many people with his tutorials, livestreams and 1 on 1 help. I am very sorry to hear that he is gone. He certainly won't be forgotten. Bold Cheetah is dedicated in his honour.

The level of Blood/Gore you want would change ESRB Rating to M-17+, Currently ESRB has DCS as Teen. That M Logo on box art and Store Page deters.

The AIM-120 has an issue where if launching on a group of targets the missile will consistently acquire the wrong target when activating its seeker. When the missile goes pit bull, the missile will consistently acquire the trailing aircraft in a formation instead of the intended target. The two targets can have almost 1nm of separation between them, and the missile will always go for the trailing target on seeker activation. 120_group_leading shows this quite clearly. The missile is fired at the LEFT/Leading target in the formation, and acquires the trailing aircraft instead. Note that the missile displays unusual guidance, most probably due to receiving (in this case) incorrect datalink data for the wrong aircraft. When the situation is reversed and the trailing aircraft in formation is targeted, the missile has no problems discerning the two targets even with a much smaller separation between the two. 120_group_trailing shows this with a separation of ~500ft between the two aircraft, yet the missile acquires the intended target in this case. 120_group_1&2 show a DTT launch on both aircraft in a formation from a left offset angle. Despite both missiles being targeted at separate aircraft, both missiles go for a single target; the trailing aircraft in formation. Something important to note is that this only occurs when a formation of targets is attacked from a certain direction. 120_group_3&4 show that if the same formation as in 120_group_1&2 is attacked from head-on or a right offset, the issue does not occur and the missiles acquire the correct targets. 120_group_1.acmi 120_group_2.acmi 120_group_3.acmi 120_group_4.acmi 120_group_leading.acmi 120_group_trailing.acmi 120_group_1.trk 120_group_2.trk 120_group_3.trk 120_group_4.trk 120_group_leading.trk 120_group_trailing.trk

Just no dude

I can think of a few differences: - The Heatblur store sells a two-crew license that saves US$20 from list price, this license is not avaliable on Steam or ED-shop. - The ED-Store gives you a 10% bonus in ED-miles, that allow you to save up to 10% on a future purchase. - The Steam store has a worlwide-sensible exchange rate, that sometimes allows you to get a Module for much less than the other two stores. - Both Steam and ED have seasonal Sales where you can get the Modules at a saving, don't know if the HB store has these Sales. I'm not sure .. I would assume yes, or else HB wouldn't bother to have their own store. No, there isnt, but in the past they have sold custom t-shirts, but I don't see them on their store anymore. A very short-sighted advice, you go out of your way to discourage potential buyers ... surely you don't realize that the more buyers you discourage, the less funds available to fix bugs or develop new modules ... well done

Да, при холодном старте точность получается ниже из-за вибрации вертолета от двигателей, как минимум. Может быть от ветра. Там есть косяки. Разбираемся. Автодоворот на цель не должен быть завязан на ИНС.

I have created a report for the team with what we have so far.

По кабелю работал только через Streaming Asistant, которая фирменная прога от Пики. Через эту прогу в принципе картинка мыльноватая, что по проводу, что без. Через VD по беспроводу подключался, картинка отличная. Никаких расфокусов. Для меня лакмус - цифры скорости/возвышения на радаре f/a-18. они самые мелкие, и вот через SA их хрен разберешь, через VD видно отлично.

it's almost there. Although flight manual done in CN, it's better to wait until EN is finished. also some other issues that more or less affect the play experience need to be addressed. but anyway, we are very close to end ob status

With the F-5 glass wing structure in place for over a year now, I have to assume this is a permanent feature. One can only hope all other modules will get the same upgrade. My group has pretty much given up on DCS, primarily because of this and similar issues. Oh well. Life goes on.

Octopus-G and his La-7: more:

Разработка модуля DCS: Ла-7 идёт полным ходом. Чтобы немного скрасить ожидание, мы подготовили для вас серию небольших заметок о разработке модуля, о самолёте и его элементах, о связанных с самолётом личностях. И начнём мы с небольшого сравнения. На фоне И-16 - представителя истребительной авиации начала Второй мировой войны, самолёт Ла-7 существенно более совершенен не только как боевая машина, но и как объект эксплуатации. Первое, что нужно отметить - конечно шасси. Больше нет тех мучительных многоэтапных процедур по подъёму/опусканию стоек посредством не слишком надёжного ручного механизма. Отныне уборка и выпуск шасси осуществляются простой постановкой гидравлического крана в соответствующее положение, что позволяет сосредоточить внимание лётчика на выполнении задания. Помимо этого, наличие триммеров в каналах тангажа и рыскания уменьшает утомляемость лётчика при пилотировании, повышая чувство комфорта. Для запуска мотора больше не требуется внешнее электрическое питание или ручная раскрутка стартёра. Автономность процедуры обеспечена бортовой системой сжатого воздуха. Закрытая пилотская кабина - также немаловажный элемент по части комфорта полёта. Единственное, чем отличался самолёт для лётчика в негативную сторону - присутствием удушающей жары в этой кабине от мощного мотора, с которой не справлялась система кондиционирования. К счастью, этот момент физически не затронет наших виртуальных пилотов. Разумеется, эти минимальные удобства были неотъемлемой нормой того времени, но для ценителей красной поршневой авиации настают поистине комфортные времена!

I just purchased this module a few days ago. I have one big regret, not buying it sooner. What a nice surprise! Can't wait for the different variants and a campaign.

Hi rotorheads, I would be interested to know how satisfied those who got the BS 3 update are with it? I personally bought it yesterday. And I'm really excited. And how realistic some extensions are or aren't...there are plenty of others that get lost in endless discussions.

Saludos a toda la comunidad hispana de DCS.Acabo de fundar un nuevo escuadrón dedicado unica y exclusivamente a DCS WORLD. En cuanto tenga el DIscord totalmente listo, dejare por aqui un enlace al mismo para todo aquel que esté interesado.Un abrazo a todos. Este escuadrón se ha creado con la idea de volar DCS WORLD ,en modo estrictamente COOPERATIVO creando nuestras propias misiones o campañas en un entorno lo mas realista posible.He decidido no crear academias de vuelo ni nada por el estilo ya que creo que ralentiza la diversion y la forma de hacer las cosas.Si que nos enseñaremos unos a otros a aprender las caracteristicas y los procedimientos de los complejos modulos de DCS WORLD asi como del editor de misiones.Es muy importante que cuentes con un equipo potente que te permita disfrutar de DCS WORLD en su apartado multijugador y sobre todo disponer minimamente desde un principio de un TRACK IR y un HOTAS, ya que la experiencia me dice que si no se dispone de ambos perifericos , se pierde muchisimo el tiempo intentando amoldarse a un jugador que no los posea.La idea es explotar el realismo de este simulador no solo en combate si no tambien en apartados como la radionavegacion, cartas de vuelo etc.. volando con una climatologia lo mas real posible y en cualquier hora del dia y utilizar unas comunicaciones mas o menos realistas. Enlace a DISCORD https://discord.gg/DpySyr99ts

Есть проблемы с выставкой с холодного старта. В основном из-за вибраций вертолета. Сейчас решаем. Фикс будет в январе.

I think people are not ranting about "eyecandy" they are ranting about the priority ED has for some developements or in which order ED rolls them out. I mean the logical order would be: 1) increase performance of the core /modify the engine 2) then "eyecandy" like the clouds 3) and in the end such features like dynamic weather

I've not started testing the 4080 with DCS World yet - but have spent the afternoon testing with my VR games that are resource-intensive and all I can say is "Wow". Not just from what I see, but on fpsVR. Hope to do some DCS testing this evening, if Mrs doesn't mind me disappearing yet again. This card is just awesome - and the Pico 4 outdoes all my other headsets easily - though it does have the occasional minor glitch with PCVR wireless.

Да, там есть завязка. Уберем.

this is funny. ED shall fixt this . By the way I think the orginal laser warning pannel is more straight forward than the ABRIS.

There are many photos in this very thread that show the Ka-50 with the Missile Warning System, even some without the DIRCM turrets. Here's one from the 2nd post in the thread:

Обновление пока ручное. То есть качаем архив по ссылке, заменяем файл exe. Файл конфигурации не трогаем - все прошлые настройки останутся на месте Ага, была цель как раз таки до НГ успеть Скорее всего на днях ещё мелкое обновление будет, заметил пару некритичных багов....

Bye Phant

A user has already converted Deployment for the BS3: https://www.digitalcombatsimulator.com/en/files/3328007/

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

ED, I'm begging you, could you please make a deal with the creators of CAM, so those aircrafts are available straight from the bat in the mission editor? These planes adds another dimension to mission making, and when I create missions, I hate to have extra requirements for my mission to work. If the skins/brands adds a problem, then I'm fine with just generic skins, but please make the standard passenger jets available as standard.

Just stop asking for dates... it comes when its ready. Every day we are one day closer to it:P

I want my lights to smash!!!

What planet are you from? 60FPS in VR is "poor performance" and 90FPS is "low but marginally acceptable"? In my world, 60FPS in VR is very good and 90FPS is exceptional.

Обновление 1.4 - Добавлены модификаторы действий: Теперь для любого действия можно добавить действие-модификатор. Основное действие при этом будет отработано только в том случае, если активен соответствующий модификатор. - Тип активации действия: Любому действию или модификатору можно назначить тип активации: ◉ Стандартный (как было раньше) - действие активно, пока НАЖАТА выбранная кнопка джойстика или ось ВХОДИТ в назначенный диапазон; ◉ Обратный - действие активно, пока ОТПУЩЕНА выбранная кнопка джойстика или ось находится ВНЕ назначенного диапазона; ◉ Переключатель - статус изменяется каждый раз при нажатии кнопки или входе в назначенную зону оси. - Новые типы действий: Помимо стандартного и расширенного режимов отработки кнопок, добавлено: ◉ Расширенный режим для осей: на оси также, как и на кнопки, теперь можно назначать двойное и долгое нажатие (нажатие оси = время, когда она находится в назначенном диапазоне. Тип действия также учитывается); ◉ Циклический режим: Назначенные команды будут отработаны несколько раз через заданный интервал времени. Количество повторений может быть задано явно, либо действие может повторяться, пока активно соответствующее действие (хорошо сочетается с тумблерами или типом действия "переключатель") ◉ Секвенции: отработка разных команд по очереди. При каждой следующей активации действия выполняется следующий назначенный набор команд. При достижении конца списка, выполнение начинается с начала (спасибо FenechkA за идею). ◉ Переключение профилей (beta): возможность переключать запущенный профиль по команде с джойстика. * Beta: В процессе тестирования было выявлено, что процесс переключения занимает 30-50 мс. (на моём железе), при этом отработка других команд приостанавливается. Соответственно, при быстром переключении профилей туда-сюда, возможны пропуски отработки команд. Пока я не придумал, как решить это, не загадив оперативную память лишним хламом и не нагружая процессор ненужными вычислениями. Поэтому пока beta. - Эмуляция действий мыши: Кроме набора клавиатурных команд, теперь можно также отправлять в игру нажатия мыши. Поддерживаются 5 кнопок (левая, правая, средняя и 2 дополнительных), а также эмуляция скролла колеса мыши - Автоматическая проверка обновлений: При наличии новой версии, программа при запуске покажет уведомление и ссылку на скачивание. Само обновление пока ручное (заменить скачанный exe файл в папке программы). - Улучшения UI: ◉ Возможность сортировать паттерны по группам; ◉ Отслеживание состояния действия с учётом типа активации, проверка работоспособности с учётом выбранного модификатора в окне настройки паттерна; ◉ Отслеживание отправляемых команд при запущенном профиле для проверки правильной настройки паттернов и модификаторов; ◉ Прочие мелкие улучшения UI. Скачать: https://github.com/tjden88/JoyMapper/releases P.S. В связи с недостатком располагаемых устройств / времени и прочим, а также в связи с обширными изменениями и нововведениями, протестировать все новые возможности маппера как следует не получается. В связи с этим просьба неравнодушым - пожалуйста, сообщайте мне в этой теме или на гитхабе о найденных баголагах и прочих неприятностях, если таковые обнаружатся. Спасибо. Скриншоты:

Any news to share? Can we have a general info if the rate performance will be changed?

Hi, No offense taken, your message is detailed and constructive! Yes, IRL you barely hear the engine inside. I agree that there are pro and cons for making the engine more audible from the cockpit. And there are actually pro and con users regarding this, the beta testers that helped us adjusting levels actually liked them... and were maybe not representative of the full user base. And on the other hand we had ground crew feedback asking us to shift the whirl by a halftone as it wasn't matching... everyone tends to focus on a different detail And yes we have no professional sound designer in house! The big work done here was coding an "engine sound engine". I agree there is still some work to be done in samples and levels, you can hear in the video above some upcoming changes. Cheers!

I did another test with Marinaras replay posted here. 5800X3D, 32Gb RAM, SSD, 3080/7900XTX, Quest 2 https://imgur.com/a/ebjtdLF 7900 XTX performs quite a lot better than 3080 on low CPU scenarios. Even the VR performance is quite a lot better. Very nice upgrade for flat screen definitely and on paper for VR too. There is however issue with VR. Unless the FPS is same as display refresh rate like in the beginning of Marinaras replay, moving head is stuttery mess. There is certain amount of stuttering even with 3080, but it is so smooth that you don't really notice it unless you are looking for it. ASW also does not work with AMD currently(has it ever?) so it can not be used to get rid of the stuttering either. What worries me is the high CPU scenarios where there is barely any difference between 3080 and 7900XTX. Servers like Enigma or missions like Liberation both are very CPU heavy. Drivers also might be an issue and if you are believer of fine wine theory AMD might get better. It is however quite a bit risk to bet on that. I honestly don't know if I should keep this or not. 7900 XTX is 1200 euro, 4080 is 1500 euro and 4090 is 2300 euro here. 1200 is pretty much the limit I am willing to pay for GPU. While 4080 might be better for VR, I am not willing to pay that price.

I'm on pins and needles for the 2023 and beyond video.

I'd added the hold task to try and get lead to stop going off on it's own. And I needed to set a high speed for timing purposes for the rest of the units. Sure, I could add a very close by initial 1 waypoint at 20mps and then go 'full throttle'. If it was that difficult and the vagaries of DCS AI are such that it's unreliable - that itself is a bug/reason it needs a *serious* re-write and fix.

The downside is you just broke your plane. If all you care about is guns only BFM, with magic airstarts then it doesnt make a difference. In a real F14 you would never fight BFM with flaps down because A) it will break your plane and B) it will break your $%&345! plane you lunatic and you might crash at some point because of it and even die so don't do it. Ever.

(source FB)

I'm hoping for January, campaign has been approved by ED and sent for release .

Привожу картинки с конусами всех 4-х пеленгаторов ракет. Чтобы было понятно какую область они покрывают. Каждый пеленгатор имеет конус видимости с углом 110 градусов. Стоит заметить что есть заметные провалы между пеленгаторами на 12, 3, 6 и 9 часов. То есть с этих направлений ракеты могут пролететь незамеченными чуть выше вертолета.

No one asks you to. Not a single customer owes us a single bug report. But it should be known at the same time, that simply saying "it doesn't work", does not allow us to follow up much. In this case it is a bit different, the (factual) issues are known to us (as are the more non-factual complaints and opinions), but the fact remains. That said, this thread is full of hyperbole, which does not help make a case, if I may add ever so kindly. This is where factual bug reports that leave out emotions, help your cause simply better, because they add data that helps speed up the process of fixing. The more data we have, the easier we (and ED) can pinpoint the issue and adjust what needs adjusting. Reading hyperbole or absolute statements such as "is utterly useless" does not allow for much more than acknowledging your opinion, which by all means you are entitled to have and which is by all means appreciated a priori. Of course it also invites diverse or controverse opinion as well, which everyone else is allowed to have as much as yourself, including us, btw. Hence, if you put it like that, I disagree. The phoenix is anything but useless. How would I know? Because I use it myself. And if you look closely, the experience with the phoenix is as diverse as are the users on this forum, and the difference between those who make it work and those who do not, is that the former do not open threads about it being so brilliant for them. They make a post or two, about how more or less successful they were with it (online or against XY), or post a tacview here and there, but then don't linger much, because they do not face a constantly re-occurring problem for themselves, like not getting the missile to work. This is not a remark on skill btw, just on the matter of the fact that some make it work more, and some struggle with it more. And the latter do have our full understanding. It is an older missile to employ while still "amraam enough" to trick folks into thinking it should offer the same reliability and ease of use (by truly forgetting about it once fired), both from the side of the employing platform (AWG-9) as well as on its own. But this is not true. The AWG-9's TWS was the first ever, and came with its own set of issues. For example target weighting. We use the algorithm used by the AWG-9. And it has its limits. It comes to no surprise that PDSTT was a preferred employment method IRL, but in DCS players of course do not want to drop the comfort or advantage or if you will, "leveling ability" of TWS when flying against opponents like F-15s, F-16s and F-18s which come equipped with a much more modern and reliable TWS, more modern amraams, etc. Understandable to then think: But what good is the phoenix and TWS to me, if I have to fire it like a sparrow against a slammer weilding Viper??? And this is where making the phoenix work is more complicated than making an aim120 work, it involves more pre-launch decision making and more post-launch caretaking. (But if one person can make it work against Vipers (forgot who recently posted about that), so can we all, at least theoretically. And reports like that do not stand alone, just that they are more quiet, as mentioned.) This is one side that feeds into folks having issues, and many explanations in this thread and the main thread point exactly to that. The other side are of course its remaining issues as well: they add to that complexity and make it even harder and sometimes you can do everything right and it still won't work. That is true for all missiles in DCS to some degree btw. Missiles in a sim will never be perfect, heck, they are not even perfect IRL. Just recently a new post came up about the phoenix turning 180 with an overpitched shot. Guess what, if you overpitch or "manually loft" a missile that much IRL, it could potentially encounter something eerily similar. That said, in DCS this is still a bug, because it was not coded with intention to go 180 when you crassly overloft. But you know the saying, when life sometimes simulates fiction... And it does not change the fact, that even without a single bug being present anymore, you still should not overloft it. Which just goes to show: dealing with missile issues in principle is a thing of flying fighter jets. That certain bugs are more frustrating than others is also understandable: the automatic pitch up after being notched is a thorn in our eyes just as it is in yours. The general lofting logic otoh is far less off than most make it out to be. It is supposed to go high steep fast. And we tested it: a more shallow loft results in less terminal velocity. Which goes to show: not everything being "felt" or tossed around, is always substantiated. Hence: factual bug reports help more than opinions and feelings, as much as we appreciate any kind of feedback. Just that some is actionable and some isn't really, as much as we'd want it to be. Lastly, about issues not in our hands: I am not sure who you talked to at Heatblur (it wasn't me, I've seen you sent me a PM but I hadn't had the time to reply to it yet, and hopefully my reply will answer most of it here), and who you talked to at ED. But both ED and us have a firm and commonly shared understanding that we want to improve what we can, each from their side, which @NineLine pointed out aptly above. We work together and neither of us is interested in shifting blame. But we share different responsibilities, and some things fall upon us to work on, and some fall onto ED to work on, simple as that. AI, guidance, etc - that is in ED's hands. Which does not mean that we simply go "here, fix it please." We make our case concerning these issues, trying to produce actionable data that shows where one fix would help another, where things work not as they should, or need fixing etc. Likewise ED engages with us in this dialogue and common effort the same way. We help each other, out of a common interest to improve what must and can be improved. And some things are quick and easier to fix, and ED has always been very forthcoming in helping us with numerous issues that let us improve guidance, loft, fixing various bugs with the missile, from patch to patch, ever since we adjusted the overperformance of the phoenix. But other things cannot be changed over night, like having a new AI, or some parts of guidance logic, which result in some weird outcomes like the pitch up after the notch. We first need to understand what it is wrong or causing it, to be able to fix it. When we say we are working on it, we also mean that. And as soon as we understand the cause of an issue, either on our or ED's side, it will get fixed, as always. But we keep turning in circles here on our forums about issues that are known and, in the end, are still not in our hands and affect not only the phoenix in DCS, which also means: ED is not only responsible to help us, but to help numerous 3rd parties, keep a base game progressing, keeping modules maintained, etc. The phoenix is one issue out of many. Let me conclude with: we do hear you. We heard you the first time in the guided phoenix discussions and every subsequent time, too. We agree with some, but not with everything, and in both cases thank you for your feedback. You really don't need to open extra threads about these issues (especially since that is what the guided discussion thread is for), because we are fully aware of all the remaining issues and we have been committed to them from the moment we encountered them. But at the same time a lot of the complaining stems from wrongly set expectations as well, and as someone who flies the Tomcat daily, I know that it is far from unplayable, or to circle back to the phoenix: far from useless. The issues that remain anger me as much as they do you. But they pester me far less, because within the entire complexity of employing the phoenix with maximum aid by pilot and RIO to make a successful kill shot, or defensive shot, these issues are not the primary concern. And once you develop a certain discipline for the phoenix, you may find, like me, and many other, less loud voices, that these issues factor into the balance between success and failure far less, than one would think if taking the hyperbole, the boiling emotions and the frustration shared among some too literally - if you'll pardon me for saying it a bit more directly. Either way, I can assure you: we are as interested in fixing the remaining issues as you are. Even so I would caution everyone to not think that these fixes will turn the phoenix into the magical trick for all treats that some apparently would like it to be. But most importantly: hyperbole and exaggerations will not get us there. And I cannot stress this enough: the phoenix did not get nerfed. We don't nerf stuff. It is a notion as misguided as the accusations we received before that we intentionally overpowered the missile "to sell more modules." We adjusted its overperformance to be much more realistic following newly gained insights. That is something everyone should finally get to terms with. We do not care how good or bad a missile is, or what it means for PvP etc. And while we hope that you are successful with it and have fun with it, above all we care about it being accurate. PS: I am closing the thread, because we already have a guided discussion thread for the phoenix. Please keep discussing there. Opening more threads about your gripes with the phoenix will not help speed up the process at all. Factual reports will. Thank you! https://forum.dcs.world/topic/308085-dcs-f-14-development-update-aim-54-phoenix-improvements-overhaul-guided-discussion/