Callsign JoNay

Only 2 and 3 bit on the chaff. 1 and 4 were notched. It's easiest to tell when a missile bites on chaff if you go to the missile's HUD view in Tacview. The center of the HUD will zero in on a chaff bundle.

Maybe it's just me, but I haven't seen any of my Phoenix shots go for chaff in many updates now. None of your attached Tacview files, or the person you're replying to either. I feel like ED made a stealth change to the CM system somewhere along the way, because I used to see 80% of my phoenix shots get trashed by chaff six months ago, and I never see it happen any more. Edit: To be clear, I'm not complaining. Just an observation.

It's probably user error. I have no problems with Jester locking things if they are within the AWG-9 scan volume. Make sure you can see the top half of the HAFU on the TID. That is what the AWG actually sees. The bottom half of the HAFU is only link-4. Jester is not smart enough to adjust antenna elevation or deal with notching targets to turn bottom half HAFUs into full HAFUs.

Hmm, DCSism or not I use it quite a lot. Being 3 (or more) degrees below a target works out to quite an altitude deficit over a distance, and something I prefer to not worry about. (What if I'm distracted by something else and and drift to 2.9 degrees and lose my target in the absolutely massive PD notch filter?) Nah, I prefer to use MLC out and try to stay co-alt so I don't have to worry about it. I hope you reconsider adding it to the Jester menu. The aspect switch made it into the Jester menu and there's almost never a reason to take it out of nose setting. I would much rather have it replaced with MLC Auto/Out options.

Lol, smart-ass.

I just about fell out of my chair when he said the IRST could pick up targets from 200-300 NM away.

Looks like it's still pretty effective to me.

Maybe your problem is (as your thumbnail is suggesting), you're shooting at under 25 NM only. The missile is not lofting from that range, it's basically taking a LOS trajectory. And your statement that it will never exceed Mach 4 is inaccurate. See my vid on page 2.

Suggest you try LARGE. The DCS AI usually cranks/notches in between where a 54 would pitbull from Large to Normal, resulting in missiles getting trashed before they can PB. Large will (usually) ensure that you'll get your pitbull before they begin defensive maneuvers. See my video on page 2. Granted I used the MK60. My experience is the opposite with chaff. I used to lose 54s to chaff 95% of the time when I was testing in mid 2021, but I haven't seen any of my 54s lose to chaff in the last few patches.

I did a fun before and after comparison on the MK60. Top half of the screen is before, bottom half is after. Pre-patch missile achieves a full Mach faster top speed over the post-patch missile, but their speed/energy was similar in the terminal phase. EDIT: Missile shot is at 5:08 by the way. I included the flight profile leading up to the missile shot to show any inconsistencies before the Fox-3, but feel free to skip.

Here's a video from our main weekly mission last Friday: We are still recruiting for F-14B, A-10, AV-8B, and all helos. F-16C and F/A-18C slots are currently full/waitlist.

I know it's not apples to apples, but every strafing video I've seen from A-10s, F-16, and F-18 seems to shake the camera and cockpit pretty good. Usually it scrambles up the compass too.

Yep. It some cases it would be more realistic if the AI turned and ran away from a 14 in their RWR, especially if they are flying an inferior fighter.

I mean, that's not realistic either. Good pilots anticipate when they're probably being shot at. They don't just fly straight ahead like dummies until their RWR tells them a missile has gone active. And chaff shouldn't have any effect on PD radar guided missiles anyway, so it's questionable that the AI should even dispense it at all, but I do think they should be capable of reacting in some way before the actual pitbull is achieved.

Personally I would love that to be implemented in DCS. Some kind of mechanic that prevents head tracking under G would be great.

I think its r.ctrl enter? It brings up a little overlay in the lower left of your monitor that shows your stick, trim, and throttle inputs. Over top of the window I know it also tells you if you are in RWS or TWS. I can't remember foe sure if it indicates PSTT or PDSTT but I'm pretty sure it does?

Doesn't it show the radar mode in the controls overlay? You could fly with that turned on, I guess.

Me and a few friends did some 3+ hour flights last month, nobody reported any issues. Can't say I've ever noticed what you are describing.

But the RIO's TID and DDD were both converted into huge MFDs too, so there ended up being a lot of glass back there.

Apologies if this has been asked before, but has anyone pushed the SC to its limits? What's the maximum number of multiplayer Hornets that can cold start at the same time before there are spawning issues? How about Tomcats?

Also ARC-210s, Link-16/MIDS, PTID... Yes, I think it would be an extremely popular module.

Are you using afterburner on take off? The Tomcat gets to flap overspeed velocity pretty quickly if you are, (which you're not supposed to in the B). Make sure the flaps are pulled up before 220-ish knots.

Same. And I think it would be a huge seller too. Too bad about the classified source material, or whatever the roadblock is.

I noticed the F-16s, F-18s, and a few other ED modules got some new callsign options in the ME, other than the usual Enfield, Dodge, Colt, Chevy, etc. Will we be getting any spiffy new callsigns for the Tomcat?

I was talking about in context to AAR which is what the topic is about. Some were saying curves won't help with AAR, or non FBW systems, and that's just wrong. You're correct there is a trade off by sacrificing resolution at the outer edges of the axes. I feel like I get the best overall performance across the spectrum with some curves, but that's just me. My advice to the one who asked for curves recommendations is to not listen to anyone's advice, including mine, and to do their own testing to find what works. Everyone's HOTAS+body combination is unique.