*Aquila*

The SLAM wasn’t designed to hunt vehicles but high value structures. Keep in mind that GPS signal is something vulnerable. Those weapons were designed to be used against the USSR, not only against Saddam’s Iraq.

Stop trying to keep the bandit in your HUD and fly the plane. You only need the bandit to stay one second in your HUD to score the kill. You're complaining about the easy planes being easy to fly while the F-14 is difficult to fly. All of this is realistic. And despite being the most difficult to learn, the F-14 is also the very best in close air combat. Just come back to basics and it will make you even more proficient with the F-15, F-16, F-18, SU-27/33, Mig-29, Mirage 2000. Because in those planes, a good Tomcat pilot will beat any single simmer on earth, except another good Tomcat pilot flying a Tomcat.

That's exactly what's Jester made for. Because there's no other way to simulate a RIO without a second player.

I suggest you have a look at this video

Could you please explain the problem with DCS night lighting?

How the hell did a topic about the MLC filter management lead you to discuss the intercept geometry? You’re all answering my request as if we already had a proper contact to track, which is off the point. If you fly online without a human RIO, you can’t manage your MLC filter like you can in single player, from the rear cockpit. That’s why I posted that request. If you’re able to define an intercept geometry for a contact you know nothing about, it’s cool for me. But I prefer detecting it before. That’s why the MLC switch has 3 positions. And that’s why I’d like to be able to use them from the pilot’s seat.

C’mon, that’s a serious topic. Engineers didn’t create that 3-positions switch for RIOs to experience ground clutter and simmers to sneer. It’s the only answer to some of us unable to detect a KC-135 30 miles away flying at the same altitude as them...

MLC filter management is not useful only when something is locked. You also may turn it off in some situations in order to detect something.

Please HB, could we have a Jester functionality to manage the AWG-9 MLC filter from the front seat, so we can avoid some contact & lock losses?

I think we need the Jester functionality to manage the MLC filter.

Sure but here is the place where I told, as a bitter feedback to the latest patch, that missilery was broken and got an upset answer for not documenting my words. I just notice that when documenting, I get no more answer. Anger sometimes collects more feedback than facts, as Cop wisely noticed previously

I wonder why my documented feedback about the missiles’ systematic lag trajectory under the plane’s guidance has no feedback.

Love you too, m8

And what about the AIM-54’s lag trajectory during its guidance by the AWG-9 ? I showed it previously here in TWS > 10 nm. It’s also the way it goes in PDSTT >10 nm. And the problem is not during the transition to pitbull.

Well, ok, you know better. Lase for 20 sec or more and the GBU-24 will hit consistently in DCS.

IRL, you won't drop at the very beginning of the CLAR as if the bomb encounters adverse atmospheric conditions, it will fall short. That family of GBUs is known for needing quite a long lasing time. Never lase less than 20 sec and you'll be a happy Penetrator shooter.

TWS, launch at < 10 nm. The AIM-54 is active off the rail and behaves well: it takes the lead from the beginning of its path. Looks like the lag path problem is when the AWG-9 is in the loop. Tacview-20201219-144149-DCS.zip.acmi

There's also something wrong during the very first part of the missile's flight. Here, in TWS, immediately after being shot, it turns toward the target's position instead of taking the lead as it should. Two problem: 1) it condemns itself to a lag trajectory, bleeding out energy and 2) it over-exposes itself to chaff. That behaviour is standard, anybody can reproduce it anytime. Here, it hits the target which flies on a straight path. Any wise evasive action will be successful. Tacview-20201219-115943-DCS-Caucasus-AIM-54-LR-test.zip.acmi

You read all that was written here about the AIM-7 and AIM-54 final tracking issues. You complain about the lack of details in my post? Well, dude, all is said: the plane is fantastic, flies like a charm, is a killer in ACM and in air to ground. The AWG-9 as of today is fantastic. The new Jester features are useful. But please, understand that when you use all that fantastic stuff in BVR and the missiles go stupid, it's frustrating. Especially when that happens with the AWG-9 at its best development status. The rifle is the best you can imagine, the sights are the most wonderful you can dream about but we shoot dud cartridges and it's frustrating. User mistakes? Well, no. I think I'm quite a fine driver and RIO, who read a lot and flied a lot to do things correctly. I experience what others do experience with the AIM-54s and -7s while using them by the book. The -54s in TWS fly to the target until they go pitbull, which is when they become stupid. Even the AIM-7s which work fine when you launch them from a Hornet go nuts with the Tomcat. What we get today is a wonderful plane wonderfuly modeled launching paper missiles. That's why I said it was fun in ACM, A/G and aerobatics but not in BVR. Well, as soon as shooting down stuff is the purpose of the operation. No hard feeling, dude. I really love the plane and I stil consider it one of the best, probably even the best modern fighter model one can find in a civilian simulation. That's probably why the old die-hard trolls ruining both the AIM-7 and AIM-54 make the experience really frustrating.

Try this: \Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F14\Missions\QuickStart

It will be a short feedback. Due to the persistent failure in simulating its BVR armament, the F-14 is a rewarding ground attack aircraft in DCS, as soon as there's no air opponents or Hornet guys shot them down. It's also a pleasant toy to buzz all around the place and have some 1v1 ACM fun with a buddy. But it's not a BVR fighter, which is a problem as we're talking about the legendary F-14 Tomcat. I've been one of the most enthusiastic guys about this module but sorry guys : the story is starting to look like the one of some of the most frustrating modules around here. When the Tomcat was released, anger was red hot against ED about the Hornet's development, and everybody who got their hand on the Cat felt reconciled with DCS and modern jet sims. As of today, that feeling is back in the Hornet's seat but fled far away from the Tomcat's ones.

I found how to do. I edited the topic's title and the first post.

As satellite views can confirm, conflict areas are, for various reasons, most often dark at night. How can we make this happen when building missions in DCS World? [EDIT] I tried a couple things and found the answer: starting a mission any night between September 1st 1939 and May 31st 1945 will let you see the whole map with its lights switched off. Only the airfields are lit. Quite immersive, very cool!

It makes a very loud noise when crashing. That’s the point.

The first thing you need to do is learn how to fly the plane at +/- 1000 ft AGL, 0 ft/min vertical speed, landing configuration (gear and flaps down), with the AoA indexer showing the orange O. Once you know how to do that, you just need to use the throttle: more thrust to climb, less thrust to descend, no variation to AoA. The throttle makes you go up or down, the trim and stick drive the AoA.