Wolfman289

I'm having the same issue and it's been driving me nuts! Good to hear that they have a fix coming.

I had it set as the spacebar so that was the issue. I finally realized it when I tried the mission again and pressed space to acknowledge something from Paco! The campaign has been super fun!

Nevermind, I figured it out! Just a key binding issue.

I can see both sides of the argument here. We all want this module to be realistic. I also want to enjoy it and to be able to get a hit with the AIM54, but that is extremely difficult now, even under good conditions. When past updates have come along, it has taken time to re-learn the missile and what it can do. With this update, I have been unable to figure out how to get any hits with it. It just always misses, no matter what I do. The AIM54 may be kinetically modelled realistically now, but now there's a glaring issue. Are other module's modelled as realistically as the F14 and the AIM54? What about the AI? It's obvious that the AI is not modelled realistically at all. Sometimes, they never run out of energy and can do maneuvers that are not possible, have perfect SA, chaff and flare work from a roll of the dice system, etc. Everything in DCS should be at the same level of realism, or this is a playability issue. HB has done an amazing job with the F14 and I love the module. I just wish everything was on the same page with regards to realism.

Whenever I fly the Tomcat the rudder is moving back and forth and making the plane hard to fly. It has been doing this on and off for a while, but today it has been pretty consistent and bad. It only does this with the Tomcat and no other modules that I have. I've tried clearing my joystick setting and reloading it and it still continues. Anyone have any idea's or is this a new bug with the game? Thanks!

@captain_dalanLol, I'm a fan of flying the A over the B as well. I'll have to try it again and make sure they are changing course. I do know that they have fired at me and it seems they have continued nose hot after they fire, but I'll double check. Thanks for giving it a try and the pointers, I'll mess around later with it. @IronMike I've tried the mission a few times with both C variants and have had the same issues as with the A. Both missiles actually perform almost identical to each other and miss. I don't think that I'm loosing track in TWS and it seems the JF's are continuing nose hot the entire time, but I'll double check that they are not breaking off.

Thanks for the reply. What's interesting is that when I try the Final Hour mission, the MiG's really don't turn cold after I fire. They angle themselves, but still are pointed towards my general area. On The Mariana's mission with the JF's, they continue towards me head on, nose hot and fire SD-10's at me and my wingman. I still can't get any AIM54's to hit on either mission, even with the JF's that stay nose hot. I'd attach some tac views, but I don't have any, sorry!

I just played several quick start missions where you engage multiple targets with the AIM54, like the Mariana's mission with the 4 JF's and Final Hour 2. I can't get the AIM54 won't hit anything. I've tried it several times and different speeds, altitudes, and ranges. I've had 2 hits out of 32 or so missiles fired. I'm typically firing in TWS at around 35,000 ft to 40,000, 30-40 miles away and around Mach 1.1 or 1.2. Some of these missiles are going as high as 70,000 ft during lofting and then start to drop down on the target, but cruise right by it. Some don't even take a correct trajectory to dive at enough of an angle to hit the target. I am centering the T symbol and I'm firing with the jet level. Meanwhile, I'm already having SD-10's fired at me that are tracking just fine. What is going on? I can't figure this out, but it's pretty frustrating. Also, I've tried every variant of AIM54 that's available on these two missions. I've had one hit with the A and one with the C. I've even tried at 25 miles away. Still nothing. Thanks all. I really appreciate any help or pointers, especially if I'm just doing something wrong.

You can go into the mission editor and change the A to the B and then fly the mission. I have done it on numerous campaigns and missions and have not had any issues. I will agree with what has been said that there is not much difference between the A and B.

Haha it got me too the other day! Glad it helped.

Is your air set to off? The gun will not fire if it is. The buttons for this are located on the right knee board by the lights. There’s several buttons, off, right, left, and both. Make sure it’s set to both.

I ended up sending you a PM, I don't want to hi-jack the thread. But I do enjoy story based campaigns and the voice acting and dialogue is pretty good. Maybe the issue I'm experiencing is a bug with mission 3, or I'm just screwing up lol. **Just an edit. I made it through mission 3 and it's a blast. I think the OP will have fun with this. I know I am. Sorry for the earlier doubts. I'm looking forward to seeing how it progresses. Thanks for putting all the effort into it, I'm sure it was a ton. Thanks!

I thought the same thing about it. I was able to do it, but felt it was a little tedious at times. I got stuck on mission 3 and will have to try it again later.

I could be completely off with this, but I wonder if one of the issues is that the info bar may be accurate to the sim, but is it accurate to real life as well? We are trying to compare a real life chart of the F14's performance to its performance in a sim. It would be extremely difficult(more like impossible) for the sim to be dialed in so that dimensions and other measurements are completely exact like in real life. HB could tune the F14 to match every real world chart that they can find, but if the sim is not perfect in it's measurements when compared to real life then the performance would still be inaccurate if that makes sense? Pretty tricky thing to do. Thank you to HB and Victory and the other SME's that are helping sort through it all.

I got a IPS monitor and everything now looks great! Looks like it was the TN monitor. Thanks!