Rabbisaur

All my freezes happened when I was flying at relaxed 0.8 Mach with throttle half open and very low. In 2 out of 5 sorties I landed with half fuel, no freeze or CTD.

I fully understand the difficulty in coding debugging and also understand the early access state of F14. Take your time, keep on the fantastic job, and best of luck! We all love your product very much so we wish it to be perfect.

Hi, might be a differnt issue. I had 3 DCS freezings in 3 sorties while flying on BuddySpike last night with Jester on the back seat. Just low altitudes cruising over the mountains at Mach 0.8, manual terrain following, radar searching. Receiving SAM illumination on RWR. Then suddenly all Freezed.

I had 3 DCS freezings in 3 sorties while flying on BuddySpike last night with Jester on the back seat. Just low altitudes cruising over the mountains at Mach 0.8, manual terrain following, radar searching. Receiving SAM illumination on RWR. Then suddenly all Freezed.

Please fix this bug so AIM54s don't get banned in my favorite MP server.

Are you saying that Su-27/33/J-11 can also link to E-3??? This need to be fixed.

I wish for a key bind to ask Jester to release Chaff at a rapid pace. Otherwise the Chaff release is too slow to deceive a coming missile when flying with Jester in MP.

Thank you for your very detailed analysis. I agree with you that the missiles went for the chaff. I'll definitely need more practice with the 7M to develop the 'feeling'.

I never lost lock. I know I must stay lower than the target if I want to maintain lock. I also fired twice in P-STT mode. The missile tracks the target in the beginning, but will lost tracking as soon as the target went notching. However, the lock on my F-14 maintained all the time.

Hi, please take a look at the attached tacview files. Forgive my primitive combat skills. I just wish to demonstrate a finding that AIM-7M fired from F-14B lost track very easily when the target went into notching. But AN/AWG-9 maintained the lock for the entire time in P-STT mode when I was lower than the target. Edit: Oh, I cannot upload tacview file in the forum... So I put them in a ZIP. Tacview.zip

Thank you for your reply. I centered the T to the wing mark when firing. Is that the ‘dot’ on the F-14? I’ll look for the tacview file when I’m back home tonight.

:helpsmilie: Hi, I’m trying to understand how AIM-7M works on F-14B. When I was fighting an Su-27 within 10NM, I fired AIM-7M in STT mode at him. He entered notching immediately and dived down. I immediately told Jester to switch to P-STT and dived faster than him to stay lower than him, thus STT was kept the entire time. However, my AIM-7M lost track immediately after the Su-27 went into notching. The same happened to all my subsequent three launches until I was 1-2nm away and killed the Su-27 with AIM-9M and guns. P-STT was maintained the entire time. Just AIM-7M cannot track the notching STT target. Is this correct behavior of the missiles? Can someone tell me what is going on here. Thanks in advance!:thumbup:

So it is a ED MP issue and seems long existing, and by nature should also affect all other missiles. That perfectly explains why I saw completely normal behavior of the AIM54s during single player testing last night. Whatever I did I could not replicate the bug reported in this thread in SP games against AI or attacked by an AI F-14B. Maybe the bug on the ED engine also explains why sometimes we see R27R/ER, AIM-7s kept tracking after launching A/C turned cold or lost lock or crashed. Let's hope ED will fix this game breaking bug soon. And Thanks Heatblur, the F-14B is the best DCS experience I've ever had. Fantastic job!

OK, can you specify what should I do to reproduce the bug? So far I got no luck trying with an AI. Just give me a very specific instruction. Where to start, in which mode to shot, and what should I do after launch.

Sure, let's do some more tests with a buddies to figure out how to reproduce the bug, if there is any.

I did the same for AIM54A MK60 And AIM54A MK47 They all have correct behavior. It looks when the AIM54s go into pitbull, it wiggles a few times seems to 'look for target'. Once acquired it will start tracking. I saw this kind of behavior consistently, and also give me four friendly fires on BuddySpike. I want to say sorry to the unfortunate teammates who were close enough to the bandit that I fired upon. The simple test mission is also attachedF14AIM54test.miz, please verify if you like. I will also ask my buddies to help me do more testing in the coming days. But I think this evidence is conclusive.

I came back with data. Unfortunately none of my buddies are available for some testing tonight. So I have to do some crude testing with AI. In the mission editor, I created a new mission using Caucusus map. With an player controlled Heatblur F-14B on grid CH88 at 25000ft traveling east Mach 1.4. And a AI su27 on grid DH87 at 10000ft in a wide zigzag pattern centered on west at Mach 0.5. The separation was around 53 NM. And a single AIM-54C was fired at 45NM to the target in TWS mode (Jester in the back seat). After launch I immediately asked Jester to go silent on radar. I went to the back seat and verified that the radar is in standby position. The contact icon on the TID also disappeared shortly after about 3 second delay. The AIM54C immediately went from the initial LOFT trajectory into a straight line. Although the Su-27 was cranking to the north west and turned to cranking south west, the AIM54C did not track at all. Only after the AIM54c reached within 7.3 NM, it suddenly begin to track, because the Su-27 is passing in front of it heading south west(to its right). (See the tacview screenshot in the attachment) Of course it lacks the required energy to hit the target. In the zoomed out you can see there is a initial angle and all flying in INS and/or fox3 but no tracking until 7NM to the target and then lost track crashed into the ocean. I guess this is concluded for AIM54C. No unrealistic tracking at all, and fox3 radar can only acquire Su-27 at less than 7NM. More testing with AIM54As is coming.

Good point. Let's restrict the discussion to AIM54a/c. But I have to say the points about range and INS that you listed here also have little to do with the '27ER keep tracking after launching platform has been destroyed issue'. Let's all focus on help Heatblur to fix potential bugs and make the F-14 even greater. And help stop banning AIM54 on popular online servers such as BuddySpikes as for now.

I also felt it was probably too good to be true, since it almost 5/6 hit rate in only PvP when fired in TWS mode at 25k~30k ft altitude 20-25NM away. The only target AIM54 has trouble hitting is the SU-27. All my misses are Su-27, even fired at 20NM away.

That's for sure, it shouldn't track in that case. Let's do some more tests just to cross validate and the bug has been reported here. Just wait for it to be fixed once validated.

Yes, I back you on this. I saw that as well many times. And I remember seeing this in a youtube video from Growling Sidewinder. He also pointed it out in his video. But he has so many videos I need to take time to find that specific one.

And I hope you know that you should fire AIM54 in TWS not STT. If in STT mode and you lost lock, the missile immediately goes to pitbull.

I was planning to do some testing tonight on other things. Now I will definitely do additional test on this. Experiment design: single target flying in zigzag. F14 launch AIM54a/c at 35nm, turn off radar immediately, ensure there's no other Aircraft in the map, esp. E3A/E2C/any carriers than might potentially use datalink to update target information. Look at missile behavior. I will post the result later. If it can be confirmed, then we have more evidence this need to be fixed. I won't let the F-14 go in spectator in case to rule out that might be a bug of going to spectator instead.

@FoxAlfa I think what says here is correct. From here https://www.forecastinternational.com/archive/disp_old_pdf.cfm?ARC_ID=1066, I read the following piece of information: Control & Guidance. Both missiles use the Hughes AWG-9 Doppler radar fire control system, with an infrared subsystem. The central processing computer is built by Control Data Corporation. The missile incorporates command/inertial guidance through the mid-course and active terminal guidance; the onboard guidance system is designated DSQ-26, the detection device is designated the DSU-28, and the safety fuze the FSU-10/A. Northrop Corporation Electronics Division supplies the inertial reference component. The AIM-54C features an all-new Digital Electronics Unit with all-digital processing and an ability to identify targets by individual characteristics through pre-stored computer simulations. The aerodynamic control surfaces are electro-hydraulically actuated with components supplied by Hydraulic Research and Moog. Borg Warner has developed a pneumatic actuation system for the AIM-54. It appears that AIM-54 has a inertial guidance updated by command(datalink) from launching platform(F14) and/or E-2C. I'm looking for more definite answer for you. I also remember I read somewhere that AIM54 has FM antenna on the missile that receive datalink updates of target information. But I forgot where the source is at this moment. I will try to find it for you. So it is more than SARH. At the mean time, you can try ask your buddy to fly the F14 in a one on one test situation with your su27. TWS launch the AIM54 and immediately turn off the sensors on the F14. And you, flying the su27, do your dancing to evade the missile and look at its behavior. when the missile past your flight path, ask your buddy to turn on the radar and given you told him your location so hopefully the radar on the f14 immediately acquires your location, and look at the missile's behavior at that moment again to see whether it can turn back and chase you. That would be more constructive information from you than your first post. Good luck and have fun!