fat creason

We do some special stuff to the trim functionality on the tomcat when non-vJoy FFB devices are detected. Can you try disabling FFB on your wheel?

are you using FFB? Did not experience this in testing

We haven't changed anything regarding that and ED has not informed us of any changes to how rearming works. We'll look into it.

This has already been fixed, waiting for the next patch.

On a cooler day like 8 C, it should be able to cross-start with the running engine just above idle.

We may have just discovered a bug related to FFB users or people using a vJoy device that present itself as a FFB when it actually isn't. Does this apply to your setup?

This bug happens very rarely, making it very hard to solve. I've never had it happen to me while flying or fun or while flying in debugging modes. Maybe one day it'll happen...

Unfortunately I'm the only member of the dev team and perhaps the whole tester team with a FFB stick (MS Sidewinder 2), making this bug impossible to catch in testing. I'll look into it.

I'd also like to add that most of the easier issues to address have been addressed. A large amount of the outstanding issues on the software side are either in the "difficult and time-consuming" pile or have run up against API limitations or lack of documentation/support (TWS Auto, Jester updates, TF30/A model, Forrestal, hook/trap dynamics, etc). This is why the pace of new features may seem like it has slowed. We are still working on new features, but many of them are complex and expecting a 50 item changelog every update with all of your top desired features is not a realistic expectation.

Flameouts are unlikely in the F110, but compressor stalls and turbine damage are definitely in the mix.

Some changes to this are in testing now, should be coming soon.

The entire AICS system is implemented and was fully functional on EA release. It affects engine inlet performance and inlet drag, try stowing the ramps when supersonic and see what happens.

Found the issue with the double trim while using FFB. Hopefully will be in the next update.

That’s the idle lockup protection above Mach 1.1. It’s not described well in NATOPS but it keeps the engines near MIL power until Mach number has dropped below 1.1

I might tone pitch up moment down a little bit at low speeds (i.e. right after takeoff at high power settings), will do some testing soon. Are you full flaps on the cat launch?

It can supercruise in a clean config around 25k, and should otherwise be very near sonic speeds from sea level all the way to 35k at MIL.

Yeah, more tweaking is necessary. I tune the high end of the thrust range based on the only performance data we have (which sadly does not include a clean configuration, and is only for two power settings, MIL and max AB), so a change in stores drag requires re-checking both the MIL and MAX AB thrust/top speed ranges since the stores drag is baked into the total aircraft drag in this situation. It's fairly time consuming, hoping to get it done before the holiday break. I've already started adjusting the AB against the 4xAIM7 and 4xAIM9 loadout (the cleanest configuration we have).

I have my FFB controller back from a friend, I'll investigate this stuff sometime this week when I have time.

Nevermind, that sounds like a bug. Probably somehow related.

This may be the idle lockup protection on the engine when the CADC detects mach numbers exceeding 1.1. This feature was added about a month ago but I will try to reproduce.

I'll get my MS FFB2 back from my friend soon and do some testing.

Yes, but it may take months for a response...:joystick:

Sounds like ED has changed something related to FFB. I don't have my FFB stick with me, but to my knowledge none of our FFB code has changed in a very long time.

Unfortunately none of us have a G940 to test with. I can try out my Sidewinder 2 FFB but need to get it back from a friend first. That being said, DCS FFB is sometimes inconsistent and not robust. The F-14 FFB code has not changed in a very long time so it would surprise me that it has suddenly broken, and no one else has reported a FFB issue for many months.

This bug is cross-confirmed on the F-14. We can see it in our code running in debug mode, DCS returns the mass of the aircraft differently depending on where it spawns. https://forums.eagle.ru/showthread.php?t=245331&page=6