TWS memory mode and magic INS

[dundun92]

So a few days ago me and a squad mate were doing some tests regarding the magic INS issue, and surprisingly, we found that magic INS does not appear to be a factor when the AIM-54 is launched in STT. It only was a factor in TWS. Which reminded me of a bug the hornet has; essentially, the TWS memory mode perfectly tracks the target, so if you set the aging time to say 32 sec, shoot, and turn cold, the missile will guide perfectly off the TWS memory mode track, compensating for target maneuvers for the next 32 sec till it stopped extrapolating. Based on that, I speculated that perhaps that the magic INS on the AIM-54 is caused by (or at least related to) some sort of internal trackfile extrapolating in TWS. So I figured id ask a three questions: how long the the F-14 radar internally extrapolate trackfiles in TWS? And does STT extrapolate targets internally beyond when the player sees the lock dropped? And if so, is the process any different than the extrapolation in TWS?

 

 

 

Could be completely wrong here, but thought it was worth asking

[Southernbear]

So a few days ago me and a squad mate were doing some tests regarding the magic INS issue, and surprisingly, we found that magic INS does not appear to be a factor when the AIM-54 is launched in STT. It only was a factor in TWS. Which reminded me of a bug the hornet has; essentially, the TWS memory mode perfectly tracks the target, so if you set the aging time to say 32 sec, shoot, and turn cold, the missile will guide perfectly off the TWS memory mode track, compensating for target maneuvers for the next 32 sec till it stopped extrapolating. Based on that, I speculated that perhaps that the magic INS on the AIM-54 is caused by (or at least related to) some sort of internal trackfile extrapolating in TWS. So I figured id ask a three questions: how long the the F-14 radar internally extrapolate trackfiles in TWS? And does STT extrapolate targets internally beyond when the player sees the lock dropped? And if so, is the process any different than the extrapolation in TWS?

 

 

 

Could be completely wrong here, but thought it was worth asking

 

This is probably because as they've said many times that the INS issue is a ED missile API issue and they can't fix it till ED changes the things they need to change?

[DarksydeRob]

This is probably because as they've said many times that the INS issue is a ED missile API issue and they can't fix it till ED changes the things they need to change?

 

Actually there should be a way to remove Magic INS on the 54, however I'm pretty sure heatblur added it to reduce dysync isssues.So its more of a tradeoff betwen Dysync and Magic INS at the moment. So orignally if you knew how , you could give it magic INS manually as it didnt have it . If you didnt the missile would go dumb till pitbull and then yank itself towards the target even outside of the seeker view. Problem was this was a major reason for the massive dysync at the time with the 54. The way to do this was to press track hold after you launched a missile . Its all related to Memeory and surpirse surprise. The hornet can do the same just not to the extent the Tomcat can.

 

Since Febuary they removed the need for that and every target fired on in TWS will have its memeory kept for the lifepsan of the missile, givinig it magic INS . If they were to remove the memeory that should remove the magic INS but it will most likely bring back the old Dysync issues with it going in and out of loft for the shooter and for the person reciving the missile seeing the missile fly with magic INS.

[IronMike]

Just to remind you guys, we have no influence on guidance whatsoever.

[dundun92]

This is probably because as they've said many times that the INS issue is a ED missile API issue and they can't fix it till ED changes the things they need to change?

 

 

Im aware, but do you realize that is is fixed for the other ARH missiles (meaning its not purely a missile issue)? Which is why I suspected that the radar memory mode might have something to do with it, as this only happens in TWS, which tells me that this may not be fully a missile guidance problem, but also related to TWS radar memory mode (and not just on the F-14, but even the F-18 as I said).

 

 

 

Just to remind you guys, we have no influence on guidance whatsoever.

 

 

I know, im not suggesting you guys can do anything about the guidance directly, this is a question about how TWS memory mode affects the guidance, which is pretty clearly working differently from STT, and at least appears to be related to the magic INS bug.

Edited October 16, 2020 by dundun92

[DarksydeRob]

Im aware, but do you realize that is is fixed for the other ARH missiles? Which is why I suspected that the radar memory mode might have something to do with it, as this only happens in TWS, which tells me that this may not be fully a missile guidance problem, but also related to TWS radar memory mode (and not just on the F-14, but even the F-18 as I said).

 

 

 

 

 

 

I know, im not suggesting you guys can do anything about the guidance directly, this is a question about how TWS memory mode affects the guidance, which is pretty clearly working differently from STT, and at least appears to be related to the magic INS bug.

 

 

STT has no memeory in the Tomcat.

[dundun92]

So a note: from some more testing, we have noticed that the magic INS is only in TWS AUTO. TWS Manual does not have magic INS. Really odd, but again makes me think that somthing related to the memory mode is at play here

[near_blind]

TWS Manual does not have magic INS.

 

That should be a bug in of itself. The AWG-9 should not be letting the RIO select TWS MAN if it thinks it has an AIM-54 in the air.

[dundun92]

No it was doing that, only the mode it was launched seemed to matter, not the mode that supported it