Deleted Account

Network requests from code (from WASM, at least, not sure about JS/HTML instruments) are impacted by MSFS server status. Due to the popularity of the 40th Anniversary update, the servers are under heavy load. The simbrief integration was tested heavily during the production phase. Until server load lightens, the SimBrief uplink may be unreliable, this is unfortunately largely out of our hands. In the meantime you can use the SimBrief import/export in the iniManager under Pilot Support, as you already said under point 3 🙂

ATIS request is a known issue and should not be used at this time. It is known to cause crashes, sorry for the inconveniece. A fix for this will be delivered in the next version 🙂

Network requests from code (from WASM, at least, not sure about JS/HTML instruments) are impacted by MSFS server status. Due to the popularity of the 40th Anniversary update, the servers are under heavy load. The simbrief integration was tested heavily during the production phase. Until server load lightens, the SimBrief uplink may be unreliable, this is unfortunately largely out of our hands. In the meantime you can use the SimBrief import/export in the iniManager under Pilot Support 🙂

Heya, can you please tell me which departure this is? Or is it on every departure for you?

Heya! Sorry, I can´t reproduce this. Do you use any custom LEZL scenery by chance? If not, can you give me your complete flightplan (FROM/TO) + Alternate flightplan please?

ATIS request is a known issue, it is better to not use it for now. Will be fixed in the next version though.

If you can provide us with a detailed way on how to reliably reproduce this, we will of course look into it. But this unfortunately is too vague for the moment.

Correct, it cost too much performance, so it was omitted.

Heya, TERR radar is not the most performing item at the moment and hence it was not included. But we have it working in the sim.

Not at this time, no.

Yes, more information would be needed. Can you realiably reproduce this? If yes, how? Thanks in advance!

Nope, manual gear extension doen´t work. You wont need it anyways though, as there is no gear failure.

Steam\steamapps\common\MicrosoftFlightSimulator\Official\Steam\microsoft-aircraft-a310-300\SimObjects\Airplanes\microsoft_a310_300\texture

For the moment please remove custom airports from your community folder. We are actively looking for a solution to this, but for now this is the only workaround unfortunately.

No problem with LGSA29 here for me. 3348 is displayed as the first number as intended.

The aircraft uses the default Microsoft Navdata, so you shouldn´t need to update anything.

Shouldn´t need to input it anywhere else. Can you tell me the Airport + Runway please?

That unfortunately doesn´t help me in reproducing or in helping you on how to fix the issue. Please provide more information.

nope, updating the navdata should fix the issue

It will be some Airport in your Community folder, that uses custom navdata. We will definitely pass this along.

have you tried updating as well or are you no longer subscribed?

Crashing on entering From/To probably is related to this:

please submit a Direct Support ticket and we will go from there, thanks 🙂 https://www.inibuilds.com/contact