fat creason

This feature has not changed in a very long time...

AP will only engage if there is no force being applied to the stick (stick at the trimmed neutral point)

Only at very high speeds. The acceleration to get there will be slower than the F110.

Yes, in certain scenarios the TF30 has more thrust. Mainly at high mach numbers and down on the deck.

I use a MS Sidewinder FFB 2 to develop and test all the FFB effects. I've never seen this input lag issue before but will let you know if I do.

It will work like the current Stennis in terms of features and access. Additional functionality or features beyond that are TBD.

This is a DCS bug, best to make a post in the DCS 2.5 section.

We are trying to help ED figure out what the issue is. There are no forces we're applying from our side to the aircraft that would cause this behavior. It is somehow related to ED's ground reaction code or something they're doing while aircraft are parked on a moving object. Something seems to change that causes the sliding once DCS detects engine RPM above a certain value, and it's not anything on our side.

The stall model isn't currently a simple boolean, the severity of the flow reversal is variable and depends on many factors. The number of situations where the TF30 can stall is much larger than the F110, which will take some time to implement and test. I'll try to get the major ones in there for EA release though.

We have no plans for any ships beyond the Forrestal class right now.

http://www.heatblur.se/F-14Manual/general.html#engines-and-throttle-controls

The AB range is supposed to start at 80%, except a bug in the AB fuel system was preventing light-offs until about 88%. Once the AB was lit, you could go below 88%.

We have zero control over this, talk to ED if you're frustrated. We have sent them what they tell us they require to fix it. No idea what's special about cats 3 or 4 and why they don't work.

Good to hear. Hopefully everyone with this issue has found the option checkbox by now.

It has been difficult to get information regarding this issue from ED. There's not much we can do about it and we have been asking about status on this.

The main fix involved the pitch trim having an exaggerated contribution to the animation in certain areas of the trim travel. The stick's "zero" or neutral position is still the same.

https://forums.eagle.ru/showpost.php?p=4219152&postcount=3

If you can’t wait for the next patch, unplug any non-stick FFB devices and you’ll have no problem. This whole issue was caused by automated detection of FFB devices assuming the device was a stick.

This should be fixed in the next OB patch. We’ve added a new checkbox option to opt in to using the FFB trim implementation instead of the default trim.

The catapult functionality and on-deck handling is an ED side issue, we have almost no control over any of it. We have made ED aware of these issues and I presume they're looking into it.

The catapult functionality and on-deck handling is an ED side issue, we have almost no control over any of it. We have made ED aware of these issues and I presume they're looking into it.

The catapult functionality and on-deck handling is an ED side issue, we have almost no control over any of it. We have made ED aware of these issues and I presume they're looking into it.

Not sure we can query that option via the API, but we may look into making it an option.

This was an issue on an earlier testing version of 2.5.6 that was resolved by ED, I cannot speak to the version that was just released on OB. Cat shots worked as of early this week.

Are you using a FFB device?