iniSteven

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.

Hi, we are aware of this issue (not a WASM crash but an issue where the sim and aircraft seem to lose connection with each other) - we are in discussion with Microsoft about the cause/remedies to the issue. We haven't been able to identify a fix yet but we are working on it 🙂

Hi, what marketplace upgrades are you referring to? Do you just mean that you purchased our LAX scenery?

Double check your content manager and make sure there isn't a marketplace version superseding it maybe?

As mentioned, please make sure that ALL assitances are turned off, not just Auto trim. Also, please ensure that you don't have a keybinding conflict on your controls - for example, do you have trim bound to an axis that is overriding the fly by wire?

As far as I know there's no way a livery could cause an issue with the VNAV - they don't interact in any way. Was it related to a specific route or procedure maybe?

Hi vanatia, At the moment we are not planning to make minor adjustments to the 3d model of the A350 - with the references we have available to us we feel that we have made the aircraft as accurate as possible. That said, we are working behind the scenes for more materials and access, but this is a longer term project for us. In the meantime, we think the model stands up well to other large aircraft available on the market and so we would like to minimize changes that cause issues for our livery creators 🙂 Best, Steven

Hi Ekosif - I think we need more information to know what exactly is going on here. I've flown a lot with the A350 over the past few weeks in 1.2.0 and haven't had the issues you are describing with the VNAV. Would you be able to record a video or take a screenshot when the plan is behaving as you describe? In the meantime, double check a couple things for me: What was the ISA on your climb? Sometimes the sim has a bug where the atmosphere incorrectly remains the same default temperature at all altitudes, and this causes a significant loss of thrust preventing the aircraft from climbing (As would happen if this situation occurred IRL) Do you have a keybinding conflict that is engaging or changing autopilot modes? If you have to push buttons several times for them to register, a keybinding conflict could also cause similar behavior. Best, Steven

Sorry, what A220 are you referring to? The A220 being developed by our partners at Synaptic has not released yet.

Hi stoneman - your rudder is not centered. You may have accidentally pressed Q or E or otherwise have a control binding conflict.

Hey guys, this should be fixed in the latest update 🙂

Hi, the sim currently has no way to support dual jetways. Something that hopefully can be added in the future!

I suspect this bug is more likely an error coming from the weather model that MSFS is pulling from, rather than an issue with MSFS itself. Hard to say with certainty though.l

The FlyByWire aircraft is coded in JS which supports vector graphics. Our aircraft is coded in C++ which doesn't natively support vector graphics and so we have to use bitmaps instead. JS is great at graphics but struggles with performance when performing complex calculations, while C++ is much more efficient at performing the kind of mathematical calculations that things like LNAV/VNAV and performance calculations require, but is harder to code graphics with. So it's a tradeoff and we've gone different directions in that regard.

Hi, looking at your ISA (bottom left of the lower SD) I see it's +47 - this is a bug with the sim weather making it MUCH hotter than it should be. Higher temperature = lower engine thrust = can't reach cruise altitude. Try cycling your live weather to see if it goes back to normal. An ISA of +10 would be considered very hot, +47 is like off the scale hot.

Hi Michel, Originally the FMS was based on a Honeywell P3 unit that we had documentation on. However, that documentation lacked certain pages including offsets, so in order to have that functionality we had to find alternative documentation on a different unit that included those functions. Now we have a tester with access to an actual A330 Honeywell unit so some pages have been updated as information has come on to better match that real unit. Despite that you can in fact consider our implementation a "hybrid" of different software suites in order to provide all of the functionality that users have requested. However, if you have detailed documentation on specific units that have all of the features we'd like to implement please shoot us an email 🙂 Best, Steven

Xbox is helpful, thanks. I will look more into it. -Steven