I have also reproduced the problem.(SP and MP) The problem in multiplayer seems to be worse. In addition, during testing I found another bug that may be related to this problem. I was not able to use acm mode or let jester stt lock after jester freaked out and mess with a button in the back. (You can hear him trying to switch something and I was not able to get the target lock). Though this is not really a common apperance compared to the ghost track. To compare, I was able to reproduce the ghost track behavior 90% of time during testing in single player and only 20 % resulted in the jester freaking out and spamming a button.
Note: If anyone need the tacview file for reference just contact me.
(Single player - instant action: beyond visual range(persian gulf))
Edit: Another problem! Something catched my eyed at 1:21, when I fired the 2nd pheonix on the target the computer suddenly cleared the tws number. I tried to reproduce this and I was sucessful. I think the problem only occured after the radar try to track the ghost track.
__________________________________
List of problem and video timestamp
1. Ghost track 0:50
1.1 An interesting ghost contact that came out of no where 1:44
2. 2nd pheonix fire went dumb and radar suddenly lost track 1:21
3. Jester went nuts after setting azimuth to center 1:52 and I was not able to lock the target in any circumstances 2:50
______________________________
Personally I don't know if this is realistic or intended, but for the past I have never stumbled upon this issue. But if this is an realistic/intended behavior I just want to say that right now the F14 is very frustrate to fly and engage a target with no rio (jester controlled). Not only it is unreliable, you cannot overide the tws auto once the pheonix is fire which makes thing very frustrating. I hope that this is a real issue and they will get it fix soon, so we will not be stuck with this weird radar behavior.
Thanks.
______________________________