IronMike

I was mainly talking aim120c, the b will be much easier to go against, but it is still a successor to the aim54, a more modern, newer missile, and will have advantages and disadvantages alike.

Thank you very much @skywalker22 - that is very helpful! Thank you for all your kind input and the time you take to help us unearth these issues, it is much appreciated!

Hey Tomcatter, somehow this managed to fly completely under my radar, my apologies. It is tracked now. We need to check if this is something to be fixed on our side or DCS side, but we will investigate further. Thank you very much for the kind reports and reminder!

Yes, I hear @LanceCriminal86 is very good with stuff like that. In all honesty though, there are many capable skin makers out there, but I doubt someone would attempt this skin for you simply for free, as it is not really realistic (no harm in that btw), which simply means, it is not really on their radar. The best bet is to check the user file section, see who uploaded skins and simply write them and ask them if they would be willing to do that for you (but you would likely have to offer them something in return, doing skins is no small task). Good luck, and make sure to share the results with us please, if you do manage to find someone!

It really is up to you. If you feel like flying a case3 manually with ICLS, simply use that and turn off the autopilot. If you feel like doing a fully automated landing with ACLS, simply do that. In both cases you can use or not use autothrottle as well, which is also up to you. The radio call is a limit within DCS, so in the end, it is fair to say: the decision really is yours. Either way I wish you many happy and successful landings!

Thank you for your report and input, it is much appreciated! However, as some stated above, unfortunately AI tactics are not in our hands.

The aim120 and aim54 use a different API, yes. 40nm is long range, but not longest range. If you fire on targets at 80nm, the phoenix will win over the aim120. But within 40nm, ofc the aim120 will and should win. The aim54 benefits from many things, mainly range, that is very long range. There are also effective ways to use the aim54, albeit you have to find out and adapt. One of the problems is pitting the aim120 against the aim54 in DCS. This was never a thing in real life. The aim120 was a successor of the phoenix (the newer, more powerful, improved missile), not a threat to Tomcats. If you pit the aim54 against its irl threats, then you can clearly see its advantages. It never was developed to fight against F16s or F15s. It is natural that in DCS this is a thing, but has and cannot have any bearing on the simulation of the aim54. There will be no performance improvements, as the performance is as close as we can get it now, and we have no intentions to change that. Guidance improvements - which are not in our hands - and the transfer to the new missile schema, may give it a very tiny boost, but I would not expect much. F-14s vs amraam slinging F15/6/8 - outside of scenarios like red flag or trainings - is just not realistic. It is a bit like saying "how can the r60 keep losing against an r73?" Well, because the latter is the more modern, improved missile. You can still win against a Viper, Hornet or Eagle, but you have to work much harder for it, just like you would have to if you went with a MiG29A with R27Rs against a Flanker with R27ERs, or let alone against an SU-30 with R77s. The idea that a Tomcat should always win over its more modern successors, is somewhat misguided, if I may say so. It can, but it will be much more difficult than the other way around, which is expected. If however you create historically more or less accurate scenarios with its contemporary threats and opponents, you are pretty much mopping the floor with everyone else.

It depends. F14 tracks can be stable if you a) avoid using Jester and b) hit the autopilot within 10 seconds of mission start to avoid desync. Then they are much more reliable.

In majority, yes.

Apparently these two bugs are not related, although they clearly have the same outcome. ED is fully aware and investigating as we speak though.

Thank you Brody!

Jester is not capable of searching on his own. For now.

Often not, because they are protected, that is you cannot edit them, unless the developer released a coop version with them.

We need tracks only, tacviews are unfortunately useless (beyond initially visualizing an issue), but thank you for sharing nonetheless. With tracks we mean specifically a .trk file.

Thanks!

That is a DCS issue, there is nothing we can revert. Tactical ping for @BIGNEWY and @NineLine - is this known?

Yes, both Reforger and Cage the Bear can be flown as coop, with up to iirc 4 ppl. Apart of that several of our missions are included as coop versions as well, which you can all find in the mods/aircraft/f14/missions/multi folder in your main dcs install directory. You can also take any mission that exists with a Tomcat and simply change "player" to "client" and voilà - you have a coop mission. Important is, do not change anything else, triggers, unit names, etc etc... in order to avoid breaking the mission. Enjoy flying with your friend, we hope you guys have fun! Multicrew is how it was meant to be lived.

That's why it is part of pre-flight

hm, okay maybe we did not include it yet. and at some point that all needs to be added to the manual as well. However they are all listed in the updates when we released them, if you quickly scroll through the changelog thread, they should stand out. If you have some specific questions or need help how to use them, ping me please.

Yes, it was a slouch irl as well.

You can find them in the proxy lua.

That looks pretty normal for a 40 nm launch.

This should be disabled, as per ED. Means it should not double.

We did not change anything. Maybe ED adjusted missile lofting, but not to my knowledge.

We're aware, thank you! This is a general DCS missile guidance issue though, not phoenix specific.