Hummingbird

I can confirm that the G-onset rate (aka pitch rate)of the F-16C has been noticably reduced, it was a lot more responsive before. Not sure why this was done, and I'm not gonna lie, kinda feels like 1 step forward and then 2 steps back.

A JA37 would be amazing

It's during high AoA in hard turns, not level flight, that I noticed a lot of wing rock when attempting to apply small corrections in roll / bank angle using rudder only (didn't apply any lateral stick). That's what I don't recall being the case last I flew a little over a year ago.

It's more the EF (and Rafale) figure Im wondering about, as it goes against the statements of the pilots who have flown both (EF & F16). Not knowing the exact load outs is also problematic.

Who's the source of the picture? That the F-16 Block 60 is rated better than both the EF and Rafale in STR on that list is a bit perculiar, even when considering the upgraded F110-GE-132 powerplant (144 kN vs 131 kN of -129)

I agree, as fun as the jokes and stuff were in the beginning, they do become unnecessary distractions in the long run. A way to limit his vocals to vitals only would be nice.

Odd that such a rather drastic change was added so late. Based on what Ive read, you should be able to roll at high AoA without wobble when using rudder.

Well the above comments above indicated they hadn't

Finally got back to flying in DCS after a long hiatus, and noticed something different about the F14 right away. Specifically it seems a lot more wobbly when maneuvering at higher than 15 units AoA, eventhough Im only using rudder for roll here and not applying any side stick movement. I recall previously being able to roll without wobble at high AoA when using just rudder. To me this is a big change to the FM, and it strikes me as odd to come so late. Was it really all wrong before and is it supposed to handle this poorly at high AoA when using just rudder for roll? Asking as it appears borderline pointless to try maneuvering at high AoA atm due to the unavoidable wobble.

Did you guys not read this?: EF is going to beat the F-16C in BFM at any altitude.

@Aerges Devs Do you have available the real aircraft's EM charts to tune kinematic aspects of the FM with, or are you forced to extrapolate/estimate here? Just curious

Excited to hear about a change here, as the 19 felt way too stiff in pitch last I tested it. So really looking forward to trying her out again once I get back to flying

F4S imo, although I'd really like the J too.

The 54A Mk.60 goes over 500+ knots faster when launched from 33 kft at a co-alt target 80 nm away for me. Resulting in a speed of 1500 KTAS (Mk47 C) vs 2000 KTAS (Mk60 A) once withing 10 nm of the bogey. That's pretty extreme. Also noticed that the missile will go into a super high lofting arc even against targets at relatively close range of <20nm.

Ok, that's good to know. 10% can afterall be crucial in a dogfight, as it can amount to several deg/sec in turn rate.

Speak? Like I said, I'm not declaring any overperformance, I'm stating I've heard rumors, which has made me curious. No reason to create drama out of nothing. That's not where I got it from, I got it from friends who had been BFM'ing it in the F-14 & F-16. That doesn't mean its true ofcourse, which is why I need to check it out.

Tarnish? I wrote I've heard rumors. Calm down.

Planning on testing how all these changes have affected the STR of the aircraft soon. I've heard worrying rumors that the Mirage 2000 is now outrating every 4th gen jet in the sim, incl. the F-16, F-14, F-15, Su27, MiG29 & F/A-18. Which obviously it shouldn't be capable of.

@IronMike @fat creason Nothing?

Yeah looks about right, although I measured it between 40 and 30 deg, to makes sure it was up to speed, where I got about 6 deg/sec. But most curious is in flight where the sweep is constantly lagging behind the CADC command indicator, even at slow accelerations and thus slow sweep change commands. The sweep is lagging behind even at sweep change commands no faster than 1-2 deg/sec.

A 1 G auto trimming aircraft will try to achieve 1 G perpendicular to the direction of flight. If the direction of flight is up (or down) in relation to level flight, then you're not at 1 G perpendicular to direction of flight anymore, and hence the FLCS will be commanding a slight pitch up to achieve said 1 G. Hence its correct behavior. EDIT: Dummycatz post explains it perfectly.

What about the sweep rate? Seems abit slow and lags behind the CADC command even at low change rates, did something change?

Also noticed that the throttle wing sweep aft & forward buttons (wing sweep cover down) don't work on the ground anymore, even after pressing the master reset button. Used to be able to to adjust wing sweep on the ground using just the buttons on the throttle. In addition to this the sweep indicator also no longer automatically switches to "auto" after take off when you've reached ~300 kts speed, eventhough the CADC appears to have actually taken control.

@IronMike@fat creason Did something happen to wing sweep rate? Asking as I'm noticing the wings struggling to keep up with the CADC command even at rather low change rates. It doesn't seem like its achievning the 7.5-8 deg/sec sweep rate. This is at 1 G too btw, haven't checked if anything changed under G load yet, but you should be able to get 4 deg/sec @ 7.5 G (i.e. sweep rate only just about halfed at that G).

Decided to test the pitch stability today in terms of the aircraft's ability to return to 1.0 G flight after a positive or negative pitch command and then releasing the stick. What I found was that after commanding positive or negative G, and then releasing/centering the stick, the aircraft will oscillate in pitch around the 1.0 G attitude that it needs to return to by up to +- 0.8 G. In other words if you e.g. pull 4-6 G and quickly release/center the stick (zero pitch command), the FLCS will attempt to reduce G's back down to 1.0 too rapidly by applying too much horizontal stab trailing edge down, resulting in the aircraft undershooting 1.0 G (by as much as -0.8 G, i.e. it hits 0.2 G) before getting back up to 1.0 G. Here's a video recording, as well as track file of it occuring: F16FLCS1Govercorrect.trk Seems to be a FLCS command filter issue for when you decrease pitch/G commands by a big amount in either direction.