Question about the upcoming AIM-54 changes

https://forums.eagle.ru/showpost.php?p=4062564&postcount=1

The post says that the 54 will no longer go active immediately if tws track is lost (which is awsome!). However, does this mean that the 54 will no longer dive straight down upon losing tws track? Will it still continue it's trajectory to an estimated intercept point based on target's last known alt, speed, etc. then go active 16s from there?

Correct, as long as the WCS has a track, even if it's lost, it will continue towards that target. The track hold function is supposed to automatically enable when you launch a phoenix.

If the target is reacquired during this time can the wcs somehow re-establish a live track on it and send those updates to the missile? + in SARH mode if lock is lost then reestablished will the missile be able to reacquire like with the AIM-7's?

In TWS it would need to be the same track, in STT yes, theoretically. But it depends a bit on how it goes with our testing of our implementation so no promises.

So, if I've fired off a Phoenix in TWS, and the target notches the radar, and then the AWG-9 picks them back up, the AWG-9 will update the AIM-54 to correct their course, correct?

Each Phoenix is guiding towards the estimated position of a given track. If the radar was able to successfully figure out the "new" contact belonged to the previous track, I'd imagine so. Otherwise your best bet is probably to transmit the active command and hope the bandit flies into the missile's acquisition zone

Otherwise your best bet is probably to transmit the active command and hope the bandit flies into the missile's acquisition zone

Are we going to get the ability to transmit a "Go Active" signal?

Sent from my Pixel 3 XL using Tapatalk

Correct, as long as the WCS has a track, even if it's lost, it will continue towards that target. The track hold function is supposed to automatically enable when you launch a phoenix.

That's pretty huge then. This in combination with TWS auto, will significantly increase the range of the 54 for longer shots as it can be pretty easy to lose tws track at those distances.

...also will make friendly fire incidents less common

Awesome plan! Can't wait! I know the below are low priority but are we close to getting:

- tire morphing

- differential wheel spinning

- rudder misalignment fix

- missing ALQ-126 Mid- & High-Band Antennas (wing-glove)

- LAU-7 vs LAU-138 pylons

I also couldn't find any info on Pilot-to-RIO commands on prioritising TWS attack order sequence, e.g. skip closest enemy and launch on the furthest contact first.

Thank you for all your hard work and constant support!

Are we going to get the ability to transmit a "Go Active" signal?

 

 

Sent from my Pixel 3 XL using Tapatalk

I'm in no way affiliated with the team. My understanding of the system is that hitting the PH ACT switch with a track that is supporting a Phoenix selected will command the missile to go active. I could be mistaken.

Unfortunately that's incorrect, according to our material that switch only works pre-launch. As far as we know there's no way to manually command a missile to go active.

As for the WCS continuing to guide a Phoenix on a reaquired target it depends on if the WCS sees it as the same target, i.e. that it has not maneuvered too far away from where it's expected to be.

Unfortunately that's incorrect, according to our material that switch only works pre-launch. As far as we know there's no way to manually command a missile to go active.

That is directly contrary to material I have read, however as I cannot provide it to you, I won't complain.

I'm always happy to see new material so if you happen to be able to provide it feel free to.

Our material is quite detailed but early so it's possible this changed later on.

This is great and exciting news indeed. It makes 54 engagements unique in DCS, requiring new tactics and ways of employment. Can't wait to see this in game. Will Jester be able to use the new 54's properly from the start, or will the new features work best with a human RIO?

Also concerning the 54C this was posted in another thread a while ago:

 

 

*pic*

 

 

 

and it makes me wonder did the 54C get the ability to go active on its own? To get a basic go to this point and activate command? The guidance system from the 54C as far as i'm aware was essentially copy and pasted into the 120A.

Hmm, it doesn't say that the 54C is going active on its own. AFAIK it still needs to recieve the "Go Active" signal from the launch plattform.

This is great and exciting news indeed. It makes 54 engagements unique in DCS, requiring new tactics and ways of employment. Can't wait to see this in game. Will Jester be able to use the new 54's properly from the start, or will the new features work best with a human RIO?

I'm not sure if there is anything that should change in regards to Jester. If you fly with Jester it's still your choice as a pilot player wheter he should use TWS or STT and you need to tell him that.

will that improvment also change how AI deploys the aim-54?

on current stable branch, AI tomcats will deploy 54s like they were aim-120s (i assume that until now AI aim-54 were just reskinned 120s).

I'm not sure if there is anything that should change in regards to Jester. If you fly with Jester it's still your choice as a pilot player wheter he should use TWS or STT and you need to tell him that.

Two things from the top of my head.

1. I may decide to give Jester full control of the BVR shots and concentrate on flying the aircraft. As the RIO is the one with better SA in general, this might work better in some situations. Also for role playing reasons and immersion factor :D

2. Telling Jester to go Phoenix active before launch. Or has that already been implemented?

I just ask, once the dust settles, that HB please provide clear documentation as to how in fact the 54 behaves within DCS in all the various modes, so there’s no more educated guessing, and we can build solid RIO doctrine.

Sent from my iPhone using Tapatalk

I just ask, once the dust settles, that HB please provide clear documentation as to how in fact the 54 behaves within DCS in all the various modes, so there’s no more educated guessing, and we can build solid RIO doctrine.

+1

I understand that HB is still working on them and it isn't entirely clear even for HB how they will work exactly in the end, but once it is clear it would be great to have a detailed explanation/documentation. :thumbup:

Two things from the top of my head.

 

1. I may decide to give Jester full control of the BVR shots and concentrate on flying the aircraft. As the RIO is the one with better SA in general, this might work better in some situations. Also for role playing reasons and immersion factor

 

2. Telling Jester to go Phoenix active before launch. Or has that already been implemented?

Valid points :D

Will access to this API enable fixes to the lofting/midcourse behaviour as well or just the seeker logic?

Will access to this API enable fixes to the lofting/midcourse behaviour as well or just the seeker logic?

...look at the original post as well as very first reply

Really wonder when these changes will be introduced, since they said the changes are live in their experimental build. It can't be too much longer :)

The changes to the aim 54 should come at the same time of the tws auto since jester doesn't use the radar at all, he only looks forward without puting any kind of effort to keep a target on the radar.

Otherwise 90% of the missiles will be wasted in fail to track and/or to much risk going very close to the enemy without the possibility to crank.

will that improvment also change how AI deploys the aim-54?

on current stable branch, AI tomcats will deploy 54s like they were aim-120s (i assume that until now AI aim-54 were just reskinned 120s).

*bump*

*bump*

The AI will use the same missiles (as it does now), but whether their launch behaviour will change (which is what makes it look like it is using slammers), is a question that is not up to us to answer.