fat creason

Thank ED in this case, we don't know what broke it nor what fixed it.

This looks like a bug, I’ll investigate.

This. The next patch will make it worse for people who abuse the flaps while simultaneously making the flap drive mechanism more realistic.

The last time we changed buffeting was probably 6-8 months ago and it was at our pilot SME's request. People didn't like the change at first but they get used to it.

Now you see why I don't/can't spend 8 hours of free time on a weekend hoping this will happen to find the cause. Time like that is better spent on other bugs or new features. Like I said, no one on the HB test team has ever even seen this bug. That's how rare is it.

Buffeting has not changed in a fairly long time.

This drag change was for flap deployments beyond maneuver flaps at speeds way above the max full flap deploy speed. The flaps can jam now, but they are too robust and will be easier to jam in the future if you're overspeeding them and under moderate to high G load, i.e. doing 275 KIAS and pulling 3+ G

Man flaps can be used at higher speeds, full flaps should not be deployed above 250 KIAS at most. If you actuate the flaps above 250 you run the risk of shearing the torque tubes. The flaps do not break instantly at 226 KIAS.

We're trying to find the cause of this, the Sparrow worked on our testing versions over the weekend (and still works on our testing versions) and we haven't changed anything on our side regarding Sparrows in a very long time. Seems to be magically broken in this in specific OB version.

You could try hitting the switch in flight but I think it might depend on weight on wheels. I unintentionally broke this when trying to fix an error in the kneel switch solenoid logic pointing out by one of our SMEs.

ED finally figured out whatever was causing that. Good to hear.

No adjustments to the trim itself were made, just changed the default starting position of the pitch trim to be more nose down. More or less a QoL adjustment so it's already trimmed for a cat shot.

Flap drag was increased for flap deployments beyond the maneuvering range (i.e. full flaps) when well above the approved flap speed limit of 225 KIAS. Some people abuse full flap deployments to gain a BFM advantage, things like the would never be done in real life. I'm working on some additional flap torque tube shearing (aka flap jamming) logic for the next patch.

Can't do that, you would need the source code. :)

I know what the problem is, will fix it in the next patch.

The only way to solve this bug is for it to happen to me while I'm running in debug mode. No one on the entire HB test team has ever seen it as far as I know. Don't hold your breath.

Another thing that worked this weekend in testing that no longer work on this OB patch...

This worked on the version we sent to ED over the weekend. Glideslope reference appears to be broken again on this update...

I've spent hours trying to do that and it never happens. The thing is, I often only have a couple hours per week to work on the F-14 and spending all of that time hoping to reproduce a rare bug is just not worth taking time away from other much more important features and fixes. Maybe one day.

I've still not been able to reproduce this as it is an exceedingly rare bug.

You were most likely in SEC mode or had some problem with the AICS, but not enough info here to really tell

The F-14 isn't an F-16, be easier on the stick.

This is correct. It also depends on the control system type (reversible vs non-reversible, etc). In general, consumer USB joysticks do not even approach the lightest end of typical control force. The F-14 has an artificial feel system with springs, cams, and bobweights. If someone could make a new FFB stick that could provide 10x the force of a MS Sidewinder 2 I'd buy it yesterday.

This is correct.

No change, has been that way for a long time. If you have jitter causing the AP to engage it sounds like you may have a hardware problem. I can engage AP using my MS Sidewinder 2 without issue.