IniSteve

Hi, We've looked into it but as the A300 uses older code it's not really simple and would require a significant rewrite. Despite that, we haven't outright ruled it out so perhaps it can come in the future.

I would start by disabling auto-throttle when you get just above minimums.

Hi. We are taking an active look at this and will see what can be done.

Amazing. Glad to hear.

Thanks. This is logged and will be fixed in a future update.

Can't speak on behalf of other devs, but we did not find a solution that wouldn't compromise another function, so we chose to let the user have full control over their setup.

Thanks. Do you happen to have an Autosave from before the crash?

You profile was co-located and active on a piracy server which is against our rules, so we've suspended your participation in the discord. Despite that, you can still receive support for legitimately owned products via the direct support portal.

Getting back on topic, @Diegolas__Are you able to provide a brief example of the last interaction you had wiht the aircraft pre-crash and do you happen to have an autosave from before then?

Appreciate the assist here but please let's keep this topic and forum on the whole a civil place. It's 100% fair to be frustrated anytime this happens and no one should assume every user is keeping up to date with the findings from these events. And yes, an autosave and any debug console information that can be provided will assist greatly in finding out if this is a repeatable crash or a one-off caused by a memory error in the sim.

It's an LVAR (a "local variable" that you can use to disable/enable different functions) There is no key binding in the sim for pedal disc but you can use a 3rd party control program (FSUIPC, SPAD, MobiFlight, etc...) to assign functions using the above variable. We will look into if we can create a native solution in the future.

Hi. It should be this LVAR - `L:INI_TILLER_DISC`

I will pass this on to the team. Thanks

Ah, interesting update. I don't believe that to be the case but this also means there me be a spike in the weather refresh that is causing this to happen. Are you able to do a 8-9 hour flight over the weekend or in a manner where you can actively monitor and quickly respond to the sim to see if this occurs again? (I know what Im asking so no stress if you can 😉 )

Hi. Looking into this it seems the wrong winglet type is coded in the livery config file. I will forward this tot he team for correction into the master livery file but if you don't want to wait you can copy the following file here - [YOUR INIMANAGER FOLDER]\inibuilds-aircraft-a350-900-edw-ihc\Config\Edelweiss\ **note: IHF will be the other livery folder This should restore the "short winglets" Alternatively, you can just delete the config file and set all the options manually in the OIS. We'll consider adding them, but it will depend on painter availability in between other projects. LiveryConfig.cfg

Hi. This should be resolved in a future update. Thanks!

Frank is correct. You have an older livery or an incompatible community mod (an outdated HUES zCore is oftne the culprit but they have since pushed an update) Please confirm you're on the latest aircraft and livery versions and see if the problem persists. Additionally, you dont have to fret "clearing" your community folder. You can simple rename it to "_community" or "commbackup" and the sim will regenerate a new one on the next launch leaving your current one intact. After you troubleshoot, delete the new one and rename your old one and all will be as you found it.

Please create a separate thread.

Can you share a picture of what you're seeing so we can better understand your issue?

From the info provided it sounds like the live weather bug is affecting your flights. We've have seen and received reports of the Static Air Temp (SAT) shooting up to unrealistically high temps (+25C at FL300 and above) and it causes the aircraft to experience a short stall thus shutting of the AP. Its a well-documented sim bug that is being looked at but there isn't a clear-cut solution for it yet.

Hi. We'll take a look and see if it is indeed a LOD thing.

Hi. Apologies for the inconvenience. Please resubmit the transfer as there is a chance it wasn't received.

This is best done via a 3rd party control process and the base MCDU is quite different in the keymap to the KCCU and might not suit every user. I personally use Mobiflight as an input only profile and it works well enough, but it requires a bit of customization.

Kirkus is right. The Init-B is no longer avail after engine start. You'd then use the FUEL PRED page to check weights.