cofcorpse

Thank you! We'll look into this

Good to hear! Enjoy! :thumbup:

Good to hear! Enjoy!:thumbup:

Huh, interesting find. I'm sorry that I've read it so late. We'll look into this issue and correct as needed. Thank you for feedback!

Shorter track will be helpful, thanks!

Stranger things happen. It is supposed to be fixed, I need to check this. Thank you for feedback!

Wrong won't break instantly. You need to pull high Gs for some time, the bigger G the shorter time. Although it isn't final version of damage modelling and things may changes later

Thank you! We'll investigate this

I assume all of your external lights were switched off?

Thank you for feedback! We'll correct this!

Thank you for feedback! We'll look into this issue and will correct

This wasn't changed. I noticed too late and we don't have enough time. We'll certainly continue to improve this module!

Thank you for kind words! :thumbup: Fly safe and enjoy!

OK, I have some ideas about it. But give us some time to enjoy releasing such great module as F-5E :joystick:

Трейлер отличный! :thumbup:

Why summoned me? Some changes were made with tires, as I remember. But about FM I can't say right now. Need to refresh logs. But I think there is possibility that is just different feeling. Last couple of months we were focused mainly on releasing F-5E

:thumbup:

No problem! It's great that we find the truth here :thumbup:

Thanks for feedback! Issue is confirmed and reported.

Thanks for feedback! As said in Flight Manual this only applies for external tanks. And it works for me in 1.5.5 Open beta. Can't confirm. Fuel dump stops after reachiing bingo. Can you specify your fuel quantity and bingo setting?

It's quiet interesting. Just took a quick look through flight manuals of A and B versions and yes, FUEL LOW light works just like Fer109 describes. It is just a thing that changed with upgrade to E version. Thank you all for your concerns and feedback! :thumbup:

It's fixed in 1.5.5 Open Beta and will be fixed in stable version.

Thank you for feedback. Problem located and fixed. Hope you'll see it in next update!

Do you still experience such issue?

Issue is fixed in 1.5.5. How about 2.0? Does anyone encounter this still?