Jump to content

Can we get more information regarding AIM-54 Going Active (Distance vs Time)


Recommended Posts

Quote

AIM-54 now uses distance (determined by TGT Size switch: large=13NM, medium=10NM, small=6NM) for going active, instead of 16s TTI.

 

With the latest patch, we see that the AIM-54 uses distance vs time to go active.

 

Previously, when using ~16s TTI, we could see on the TID the countdown and have an idea of when the missile would go active, planning our maneuvers accordingly (i.e., when/if to crank etc.).

 

(1) What can we use now? Is there a ballpark of time based on distances? E.g., large ~16s, medium ~10s, etc.?

 

(2) Also, will the countdown timer still flash when the missile goes active or is there any other indication that the missile has gone active?


Edited by Bearfoot
Link to post
Share on other sites

Input from SMEs finally let us determine the activation criteria for the aim54 better: the 16s TTI was more of a crew rule of thumb and not the actual AIM-54 activation criterion. Instead, the activation cirterion is distance based, whith the distance threshold determined by the TGT size switch position at launch time. Activation distance is 13, 10 and 6 NM for large, norm and small tgt size.

What does this mean: you can select the activation criteria yourself. The sizes are meant roughly for large = bomber, nom = fighter, small = missiles, etc... You can ofc set small for a bomber, too, or large for a missile. However: a smaller target with a further away activation may slip out of the missile's cone at activation point, so that is one thing that needs to be considered. Likewise, using large will give a warning to the bandit earlier, but let you extend sooner, while small will alert the bandit much later, but you will have to support the missile longer.

To answer your questions:

1) The TTI has been adjusted, so should be fairly accurate still. 16s TTI as such is not really a value you need to be looking out for, however, since we did the change, we found that often 16s and the missile going active indeed correlates, but it is not be taken at face value.

2) The timer will still flash, when the missile goes active, so nothing changed there.


You can select the tgt size via the Jester menu now, btw.

  • Like 1

Heatblur Simulations

 

Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage.

 

http://www.heatblur.com/

 

https://www.facebook.com/heatblur/

Link to post
Share on other sites
17 hours ago, IronMike said:

Input from SMEs finally let us determine the activation criteria for the aim54 better: the 16s TTI was more of a crew rule of thumb and not the actual AIM-54 activation criterion. Instead, the activation cirterion is distance based, whith the distance threshold determined by the TGT size switch position at launch time. Activation distance is 13, 10 and 6 NM for large, norm and small tgt size.

What does this mean: you can select the activation criteria yourself. The sizes are meant roughly for large = bomber, nom = fighter, small = missiles, etc... You can ofc set small for a bomber, too, or large for a missile. However: a smaller target with a further away activation may slip out of the missile's cone at activation point, so that is one thing that needs to be considered. Likewise, using large will give a warning to the bandit earlier, but let you extend sooner, while small will alert the bandit much later, but you will have to support the missile longer.

To answer your questions:

1) The TTI has been adjusted, so should be fairly accurate still. 16s TTI as such is not really a value you need to be looking out for, however, since we did the change, we found that often 16s and the missile going active indeed correlates, but it is not be taken at face value.

2) The timer will still flash, when the missile goes active, so nothing changed there.


You can select the tgt size via the Jester menu now, btw.

And what happens if don't change anything? How does Jester handle the entire affair? Is he using some defaults? And if so, what are those?

Current modules:

FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map......ah yes, forgot the Super Carrier! Shows you how often i fly these days....

 

Modules in waiting: F-14A, MiG-23, F-4U, F-8, Falklands Map

 

 

Wish list: South East Asia map, F-4J/N, A-6, F-15A/C, Su-27, Sea Harrier FRS.1, Mirage III, MiG-17.

Link to post
Share on other sites
12 minutes ago, captain_dalan said:

And what happens if don't change anything? How does Jester handle the entire affair? Is he using some defaults? And if so, what are those?

 

It will be set to norm unless you tell Jester otherwise. The tgts switch can be set via the Jester-wheel now as per the patch notes.

Link to post
Share on other sites
4 hours ago, captain_dalan said:

And what happens if don't change anything? How does Jester handle the entire affair? Is he using some defaults? And if so, what are those?

The switch is not new. It has always been there and it has always been set to NORM by default and according to Naquaii it will stay that way, unless you command Jester to change it.

Intel i7-4790K @ 4x4GHz + 16 GB DDR3 + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

 

DCS Panavia Tornado (IDS) really needs to be a thing!

 

Tornado3 small.jpg

Link to post
Share on other sites

Ah good to know! Thanks for for adding that option! 👍

Current modules:

FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map......ah yes, forgot the Super Carrier! Shows you how often i fly these days....

 

Modules in waiting: F-14A, MiG-23, F-4U, F-8, Falklands Map

 

 

Wish list: South East Asia map, F-4J/N, A-6, F-15A/C, Su-27, Sea Harrier FRS.1, Mirage III, MiG-17.

Link to post
Share on other sites
  • 3 weeks later...

Has anyone tested the results using different settings?  I'm interested in what would be best in different scenarios.  The difference between Small and Norm is 4nm. 

Does this mean that the missile has less time to correct terminal guidance, or does it mean it's more deadly because it was guided by the AWG-9 for 4nm longer?


Edited by GatorNutz
Link to post
Share on other sites

Yep. So far i prefer the longer distance/earlier going active setting. At least for SP and PvE servers. I'm yet to try it on human opponents. ALAS, there was no flying for me the last week and weekend, so hopefully some other time.

Current modules:

FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map......ah yes, forgot the Super Carrier! Shows you how often i fly these days....

 

Modules in waiting: F-14A, MiG-23, F-4U, F-8, Falklands Map

 

 

Wish list: South East Asia map, F-4J/N, A-6, F-15A/C, Su-27, Sea Harrier FRS.1, Mirage III, MiG-17.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...