HarryCooter

I didn't look at your recordings, but are you playing the release version or beta? I don't know if they made the same update to both versions. I played the F14 a lot in beta yesterday, the missiles are completely different since the update. They act like they used to. I fired around 100 A's and C's, and they didn't loft at all. They actually tracked targets unless notched or chaffed. Before the update, they wouldn't track at all if fired within parameters where the missiles would loft. As far as energy, they have a ton of drag. So, the missiles are pretty easily drained by the bandit dragging them down, or if you are at high altitude and the bandit is low the drag will drain them pretty easily at even moderate ranges. But, the missiles actually tracking at least pushes the bandit defensive so you can push up on them and get close enough to fire a dangerous missile. Before, I would just push up on F14s with impunity because I knew their AIM54s wouldn't track.

This video shows exactly what many of us have been complaining about(at approx. 17:00). Can we please get this fixed?

I have tried this countless times and ways(literally 100's). I have maintained TWS tracks up until merge and fired at various speeds, altitudes, angles, and distances for both me and the bogeys. I have also tried the same thing with STT lock. That's why I am specifically pointing at lofting being the problem. If I fire within parameters where they don't loft, they perform as expected. I am not new to this module. I have had it for years and had no issues until they started screwing with lofting. Again, I only play beta and multiplayer. So maybe the problem is isolated there. I wouldn't know. Either way, it's a very real problem that more than a few of us have been complaining about for a while now.

Every shot I have taken that lofts does this straight up thing and then dives at nothing, and then pitches up and self-destructs. If you can manage to fire within parameters where it doesn't loft, the missiles will track just fine. Why this is still a problem is beyond me, and is making me hold off on buying any more modules. It feels like a big middle finger at this point. I don't care how many of you claim it's working just fine, it's not and hasn't been for quite some time.

In my experience, it doesn't matter which variant I use or the target size. If it lofts at decent altitude, its trashed. I only play the beta version of DCS, so maybe that's relevant. I am not aware of any difference in the missiles between the versions. Just based on what I have seen, it looks like a lofting algorithm problem. The missiles way over loft at higher altitudes, and after they have gone past the target they do this fake tracking maneuver by diving down at nothing and then pitch up and self-destruct. For some reason, Tacview only records the first flight of my session or I would have a few recordings to really see what's going on. Does anyone know if there is some start recording command or something like that I need to do to record subsequent flights?

Exactly why I said "want" and not "got". Working on it. I got Tacview today but I only managed to record 3 out of 10 flights. So, I need to figure out how to actually use it. From my flights today, it appears that if the missile doesn't loft it performs just fine. The only engagement I managed to record where I kept TWS tracks the whole time the missiles didn't loft and performed just fine. However, I had a couple situations today where I kept TWS tracks all the way up until all missiles got down to 0 but they were all just flying off into nowhere. All of those missiles were fired between 25-40 miles at 25k+ feet and all lofted.

Huh, that's odd. I just watched a couple other guys' AIM54's track some unsimulated satellites. So I switched over to the F14 to see if it was just them and had the same experience with every shot except one shot I made on someone already going down at 6 miles away. I don't care what anyone says, the Aim54 is broken and it's made the F14 unplayable. I want my money back.

I just went and tried all the different modes to see. All missiles just went straight and flew off into the distance, it didn't matter which mode I used.

I have been using voice attack for controlling Jester. If "track single bogey ahead" defaults to P-STT then that would explain why that is happening with that command, but it still wouldn't explain why the missiles also fly off in TWS mode. I'm not the only one having this issue with the missiles flying off, which leads me to believe there's an issue with the missile guidance rather than user error(which some of it very well could be).

I don't have tacview and the track file is too large to be uploaded. I just watched the track file again, and all of this missiles just flew up and off into the distance except one. The one I fired at 14 miles looked like it was tracking but it must have been tracking a submarine because it drove straight into the drink. None of them tracked the target I had locked. I was playing with a guy last night who was managing to get hits with the AIM54. His ping was low and I'm usually playing on server with a ping of around 120. So, I'm wondering if that has something to do with it.

In this particular instance, I believe I was in TWS until the 20 mile shot. TWS or STT, it's not working for me. I spent a couple days trying to figure out what the hell is wrong with this thing. I'm not wasting my time with it further until there is some fix. I almost wish I had never bought the damn thing, but it was fun for when it did work.

The F14 is practically useless right now and it's extremely irritating. It struggles to keep lock on anything under 20 miles, and when you do manage to keep lock you can't hit anything. During my final attempt the other day I managed to maintain lock from 45m-merge and fired at least 4 aim54s. 1 @ ~36m(30,000+ft), 1 @ ~20m(30,000+ft), 1 @ ~10m(30,000+ft), 1 @ ~4m(~10,000ft). Bogey didn't even have to crank. The missiles just flew off into the distance.