IniSteve

Hi. This should be working now as we have tested it with success on our side. You have to set the MCDUs up as independent units where one is marks CA_MCDU and the other is FO_MCDU in Sim App Pro. Then restart the service and it should display correctly.

All - Please refresh the manager client. It should force update to version 2.5.1 which will resolve the issue of missing config files. Alternatively, you can manually download the client here - IniManager V2 – iniBuilds Store NOTE: You must reinstall any affected airports to get the config options to show. Thanks!

Hi. We have resolved a server-side error that was causing this to happen and will push a client update shortly. Thanks for your patience.

Hi. Are you on the marketplace version of the aircraft? We've seen this occur due to the sims core compression method.

Please stay civil all. As mentioned in earlier replies, we are aware of the issue and continue to investigate.

As cool as this is it's likely beyond the scope of what MS wants to offer for this model. Despite that, a post at their forums would be the way to get this conversation started.

We'll check with our marketplace partners and see if there was an issue with the update.

Hi. It sounds like your ng token is not refreshing. Can you try logging out and in from the OIS and then seeing if it downloads the correct dataset?

Hi Luke. This isn't what we need actually. Please follow the steps outlined here if you encounter another crash (orange screens) and we can take a look - Thanks!

Provided you dont have "Realistic Refueling" marked on in the EFB, this should work.

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 😉 )