iniSteven

Hi - Both of you were banned for being active members of a piracy discord. Best, Steven

I've been flying quite a bit and have not had a BRAKES HOT ecam on any landings recently - are you having it on every flight?

Try clearing your WASM folder entirely @LizzArd - you can find a guide here:

Well the BRAKES HOT message comes on when the brakes go above 300c. How heavy is the plane? Depending on the weight it can be very easy to end up with hot brakes after landing.

Hi Skilla, the freighter version of the A340 is a so-called "preighter" - these became common during the pandemic and so we decided to model this to provide a cargo option, as there is no actual cargo variant of the A340-300.

Are you using EIS1 or EIS2? EIS1 symbology does have less contrast than on EIS2 - maybe that can help.

Well, what's the temperature of your brakes when the warning comes up?

Yes, this causes issues for real aircraft as well, there's a NOTAM about it:

Thank you for the suggestion 🙂

Hi, I would also suggest clearing your caches if you're having CTD issues - you can do this from the options -> data page and clicking "delete" Best, Steven

Hi, the AUTOBRAKE OFF callout only sounds when the Autobrakes are disengaged at a speed greater than 80kts - see here:

Thanks, I've forwarded to the scenery team 🙂

Hi, unfortunately there's no way to choose doors in MSFS at this time - hopefully it's something that can be added to the sim in the future 🙂

Gotcha, thanks for the clarification - What platform are you on? Is this PC or Xbox?

Hi Sirup, your other issue is a traditional WASM crash - again we are working hard to reduce these but as we've mentioned it's not an easy thing to fix, most crashes are unique in the sense that there isn't one fix for all of them, so it's a game of trying to recreate each report to see if we can replicate it, and from there prevent that specific crash from happening. Your issue in this thread though is one we have identified a consistent issue, and are working with MS on a fix as we've been able to recreate this issue with other addons. Currently we are trying to identify exactly what it is about our implementation that seems to cause this to happen more frequently with our products.