iniSteven

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

I've been doing flights in the A350 all week in 1.1.9 and haven't had an issue with a localizer as of yet. Are you guys on Sim Default or Navigraph data in the aircraft? Are you within the service volume of the beam when you are verifying reception?

Hi all, we're looking into this and we are unable to reproduce, and we have other users on the public build saying its working for them as well. Would you be able to try with a clean community folder and see if its working then? Perhaps this could be related to an imcompatible addon or modification? -Steven

Nothing has changed in 1.1.8 that would have changed the performance - it's not like we've reverted back to the high node count models. Perhaps you could post a screenshot of your FPS window so we might be able to diagnose where the performance issues are coming from?

I can't say I'm sharing your experience, I'm currently getting ~90fps on the ground in the A350 in Su4. I also can't see the photo you've posted of the A350 fps, only the Fenix. Could you repost it? It would help to diagnose what might be hurting your FPS. -Steven

All of the improvements we made for performance have been applied to both the 2020 and 2024 versions of the aircraft. None of the changes we made for the sake of performance were 'only' applied to 2024.

I take it you didn't read all your NOTAM's before you flew 😉 These waypoints are an issue IRL as well. The correct procedure is to plan direct from MUDOT to UNSEK when flying eastbound.

The reason the OIS is supported by touchscreens is that it's coded in JS and runs outside the WASM module of the aircraft. the MFD, as a core part of the aircraft avionics, has to be part of the WASM module and it is not possible for these screens to be controlled by a touchscreen.

Hi, the only way to fix this is to increase your texture resolution. There is nothing we can do to 'exclude' the airport navigation texture from being reduced in size by this setting.

Hi all, you can now download the A350 terrain data from the inimanager if you have trouble downloading it within the sim🙂

These things would have had to have been installed by the user in the first place. So of course as with any 3rd party modification we can only say that they need to be removed in the user added them 🙂

Thanks Rerem, I've found the issue. If you're on the NEW WAYPOINT page and press LSK R5 the key BELOW return, it crashes. I've passed it on to the team.

Hi, could you provide the full flightplan you tried to enter? And is this repeatable or it just happened once? Were you on Navigraph or Sim Default navdata? -Steven

Hi all, this issue happens when the aircraft doesn't fully initialize, and it's been an issue with the Su4 beta primarily. It can be rectified by restarting the flight - some users have reported that waiting a few moments before pressing "shift-c" to enter the aircraft helps make sure its initalized.

Are you on the Su4 beta? Runway and Air starts are broken in the beta at the moment.

Can you confirm that you're running a compatible livery?

The author of the ACA livery will need to update it to be compatible with the newest version.