IniSteve

Hi. You have the option of using either default or Navigraph data. You can set either on the SETTINGS/3RD PARTY page on the EFB. To use Navigraph you will need an active subscription.

This is already known and logged. Thanks for the report.

When this occurs is your head closer to the virtual screen? (e.g. are you physically in closer?)

Hi, ironically, they all come from the same aircraft recording. Despite that, we're going to take another look as its evident they are not meeting the overall expectation.

Hi, this is correct behaviour and has been verified from A340 pilots. At very low gross weights, the center gear will not make contact with the ground. Once you add fuel and payload it will settle onto the gear as expected.

There shouldn't be. I use the linker and cannot reproduce this issue. Are you 100% sure you have defined the exact path in the manager client? There is a very small change the manager didn't save your predefined path so you may have to redefine it in the settings menu.

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.