mattag08 Posted July 20, 2020 Posted July 20, 2020 This is a variation on the old ghost track bug in TWS. When the contact notches the radar enters track hold for that track. All is well except the track will pick a random direction and drift towards the edge of the scope at multiple miles per second, which causes TWS-A to then fail horribly. This is reproducible with basically any BVR scenario where you launch and the enemy notches when the missile is detected (AI Su-27s are a good choice). I think the main bug here is in the speed and direction of the track(s). The radar certainly should enter track hold upon a lost track, but my understanding is it should calculate the lost track's movement based on the last known position and velocity so as to provide the best possible guidance to the AIM-54. I wonder if the tracks are having some calculation going to an undefined value (or close to) as the target's closure approaches the F-14's TAS. Flying the DCS: F-14B from Heatblur Simulations with Carrier Strike Group 2 and the VF-154 Black Knights! I also own: Ka-50 2, A-10C, P-51D, UH-1H, Mi-8MTV2, FC3, F-86F, CA, Mig-15bis, Mig-21bis, F/A-18C, L-39, F-5E, AV-8B, AJS-37, F-16C, Mig-19P, JF-17, C-101, and CEII
IronMike Posted July 22, 2020 Posted July 22, 2020 If no missile (phoenix) is in the air, or no track hold commanded by the RIO, TWS-A will not hold track. Could you provide a small video, track please? 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/
Bearfoot Posted July 22, 2020 Posted July 22, 2020 I don't have a track (yet), but think this explains some behavior I have seen a LOT! Right after launching a Phoenix, the contact gets dropped. I thought it had something to do with switching from TWS-M to -A on launching the Phoenix. But this analysis makes more sense, as it comes right after the bandit notches.
near_blind Posted July 22, 2020 Posted July 22, 2020 (edited) If no missile (phoenix) is in the air, or no track hold commanded by the RIO, TWS-A will not hold track. Could you provide a small video, track please? From the other TWS thread. The missile shot happens at ~2:30. You can see the AWG-9 momentarily lose track after launch, then reacquire the contact within a frame. However it fails to correlate the held track back to the contact, and the launched track accelerates away from the original datum at Mach: Yes. I've got the track in the original post: https://forums.eagle.ru/showpost.php?p=4345758&postcount=103 Admin Note: it's best to watch from a bit earlier around 2min, to see what happens. prio2 target basically splits into two targets, whereas the track with the active missile countdown drifts out of the scope, while the "new" track is where the target should be. (edited by IM) Edited July 22, 2020 by IronMike
IronMike Posted July 22, 2020 Posted July 22, 2020 From the other TWS thread. The missile shot happens at ~2:30. You can see the AWG-9 momentarily lose track after launch, then reacquire the contact within a frame. However it fails to correlate the held track back to the contact, and the launched track accelerates away from the original datum at Mach: Yes. I've got the track in the original post: https://forums.eagle.ru/showpost.php?p=4345758&postcount=103 Thank you, nice! We will take a look! 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/
X-man Posted July 22, 2020 Posted July 22, 2020 I've experienced the same wierd loss of track when launching in TWS-M, just to immediately pick it up again, but no longer correlated, thereby wasting shots (if it wasn't for magic INS, which is still a thing in MP, but might not be i SP). Shouldn't the AWG-9 be able to correlate a lost contact with a track hold if we're talking a few seconds? Sorry for just providing text. I'll try to get a track/video of this, as well as the active radar thing mentioned in the other thread. 64th Aggressor Squadron Discord: 64th Aggressor Squadron TS: 135.181.115.54
IronMike Posted July 22, 2020 Posted July 22, 2020 Shouldn't the AWG-9 be able to correlate a lost contact with a track hold if we're talking a few seconds? Only in TWS-A if a phoenix is in the air or if track hold has been commanded by the RIO. 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/
Sam Posted July 23, 2020 Posted July 23, 2020 I've experienced the same wierd loss of track when launching in TWS-M, just to immediately pick it up again, but no longer correlated, thereby wasting shots (if it wasn't for magic INS, which is still a thing in MP, but might not be i SP). Shouldn't the AWG-9 be able to correlate a lost contact with a track hold if we're talking a few seconds? Sorry for just providing text. I'll try to get a track/video of this, as well as the active radar thing mentioned in the other thread. Same thing here, and TWS-A steers the radar cone away from the actual track most of the time.
DoorMouse Posted July 25, 2020 Posted July 25, 2020 If no missile (phoenix) is in the air, or no track hold commanded by the RIO, TWS-A will not hold track. Could you provide a small video, track please? This is 100% not the behavior in multiplayer right now. I have a million tracks of this happening and can reproduce it easily. Ill make one ASAP Jester stays in TWS-A even with no missiles in the air and you cannot get him out of it.
Recommended Posts