All Activity

More info here about the issue regarding clickspots.

Something wrong with the geometry? The window frame seems to be too low comparing to the real one.

So helpful....

Been posted about a billion times, guys. Look around.

Same issue, but only on the GE variant. PW works fine.

Do you have any assistance options enabled?

Glad to be of assistance, happy flying :)

Hi, I just tested with the Avro RJ, and it worked correctly! It seems that it was indeed the issue. Thank you for your quick answer.

Latest buy via in-game shop updated issues still with WASM also unable to switch to com2 from com1 issue, not transmitting and also on com 1 Active and "standby" fq gaphic issue. Images attached.

Hi, I am on MSFS 24 on Xbox Series X. Enjoying all the airbus aircrafts + the two payware ones (a350 - a340). Nevertheless I have questions: 1) Liveries : -need more liveries on A350 such as (swiss, Edelweiss...) 2) I enjoy the a320 and 321 Neo but will there be any development on : 320 Ceo, 319 Ceo, 321 Ceo, and Xlr ?? As on Xbox, we cannot have Fenix or FBW. 3) will there be a 330-900 Neo development and a 340-600 as well ? Thanks in advance

Hi Inibuilds, would the new A380 thats in production and the A350 be coming to PS5 marketplace anytime soon or at all please? thanks :)

Hi, I just started to use a350 bundle ver1.2.6 on XBOX. But, I cannot start the engines only for A350-900, -1000 and 900ULR was confirmed that the engines started by same procedure. Why the engines for a350-900 only cannot be started....

Hi, I am using a350 ver 1.2.6 on XBOX. I had same behavior nose wheel steeringwas not controlled just after landing. Let me try turn autopilot off after landed. Special thanks for LineDX :-)

Thank you for the update, Jamir.

It seems the 1.0.9 Updates has broken the A300 .. Unclear status at loading Many clickspots not working at the overhead, buttons off Radio / Tuning Panel not working Startup impossible..... Guys, who has made QA for this update..... Reinstalled, cleared WASM etc... no changes ...

This is a known issue regarding the A300 and A310 in SU5. We have not received any additional information regarding the action plan for this issue at this time. This is an Asobo-acknowledged sim bug since SU5 Beta that has inadvertently broken the way specific types of clickspot interaction points are rendered dependent on zoom levels and resolutions. This will affect any aircraft coded with this specific type of interaction required for protruding 3D objects that move outwards on interaction. You can test it yourselves by enabling Developer Mode > Tools > Behaviours > Debug > Interactions. You'll note it works perfectly as intended in dev mode, but breaks without it. We don't have any viable workaround so cannot address it our end alone unfortunately in any way that will still make the switches behave as they ought to.

Please correct cockpit interactions with VR controllers. Right now it is not usable.

I've logged this for the team, thank you :)

Logged for the team :)

Hi, this has already been logged for the team however it appears I never responded indicating as such. That said the forums are not for show and just because one of us doesn't respond immediately doesn't mean that it hasn't been seen and actioned on. Thank you :)

Hi, this is because of two reasons; the first is due to how the team worked around some funky terrain to make the runway at EGLC appear authentic to it real world counter-part and the other being that the MSFS Failures don't exactly interact to well with both 3rd Party Aircraft and scenery and can sometimes trigger the "Crash Event" for said in game failures. It is recommended to disable all of the MSFS Failures that can be found in the Game Assistances menus. Let me know if this helps.

Have you installed any 3rd party liveries or mods specifically for the A350-1000? If so it's possible that this could be causing the crash on loading for one but not the other

Just wondering. Has this even been picked up by the devs, or is this forum just for shows? It's been over a month since I posted this but the silence is deafening.

Hello all 👋🏼 I recently brought the 350 series from inibuilds and i was wondering if anyone knows why my sim crashes to desktop loading into a flight with the A350-900 but the A350-1000 works completely fine I’ve tried deleting my wasm folder, uninstalled and installed but no no avail

I just flew the A300F yesterday for the first time in a while and I had these click spot issues as well on console. I was going to make a topic about this but it looks like that has already been done so here I am just throwing my hat in to the ring letting people know that I to have this exact issue.