All Activity

When panning the camera around I notice white lines above the FCU which I believe is some sort of artifacting. They go away when the panning stops and only appear during daytime, night is okay. Also they don’t appear when zoomed in. I haven’t noticed this on any YouTube videos so I was wondering if there was a setting in the sim or Nvidia control panel I could try. Thanks!

Correction on the above, unique to MS2024, it is working fine in 2020. There does not seem to be a forum for DTW in the 2024 section. Thanks.

Yeh I have the same but if you sign out of navigraph and then log back into it, it will have the latest AIRAC.

I can also confirm this in MSFS2024. The grass, runways, and all hard surfaces will not show any snow despite weather settings and the surrounding area having clear snow cover. Appears to be unique to MS2020, as snow is displaying correctly in MSFS2020. Would be great to get this working, lots of snow in Detroit!

The WASM folder was deleted, I reinstalled it, but... as soon as I enter a coordinate in FIN PAGE, this is the result!

@frank_mOn the Xbox version of the a350 there are a lot of issues. You have to enter the ils manually, the engines are not spinning and the performance of the a350 with msfs2024 is horrible. So the next couple of updates are really important to make the aircraft Fun to fly. But inibuilds have done a great job so far in my opinion!

Same issue, during cruise level without touching anything, never happened before

I had the same problem this morning, and my screens turned red

This very same thing happened to me this morning with the A350-900. However, i didn't manipulated anything, it was in crusie level, and when i came back i saw all the screens red with the message. Weird because it never happened before.

It would be nice to ass the WTT Fuctionality in the aircraft for the GTN as this aircraft comes with aerial survey and SAR Models. Could be nice to have the functionality of the SAR Modes on the GTN when flying

The A340 was an easy cash grab for ini - its clear the addon is heavily dependent on the default A330’s framework …. Don’t expect @iniBuilds to fix or improve anything when they can’t even sort the basics out - I can’t even get the thing to work without constant instrument freezes and WASM crashes, it’s been over 3 month since release! I provided them with endless crash reports and detailed forum posts… absolute silence… @iniBuilds now might be a good time to let us know what is going on in the office? Having a quick break are we… seems your customers are doing your jobs for you making the necessary bug reports and cross referencing systems logic with the real aircraft… but you still can’t be bothered to follow up - add some courtesy to your New Year’s resolution list !

Please learn at first, how to write a post in a forum. Who should read this mess with horizontal scrolling? Then maybe someone will read the question and answer more than a "RTFM" (which would help, btw.).

Hi everyone, I apologize for the formatting issues in my previous post. I am writing from a device that caused some display errors. I have now fixed the layout for better readability. Problem: I am using the A340-300 on Xbox Series X with the Thrustmaster TCA Airbus Edition (2-lever Quadrant). My main issue is that Engines 1 and 4 do not respond to any throttle input between Idle and Flex. They remain at idle power and only "wake up" and jump to full power once I hit the TOGA detent on my physical hardware. My Setup: Platform: Xbox Series X Aircraft: iniBuilds A340-300 Hardware: Thrustmaster TCA Sidestick & Quadrant Mapping: Engines 1&2 assigned to Lever 1, Engines 3&4 assigned to Lever 2. I have already tried to calibrate the throttles via the EFB, but the issue with the "dead" range on Engines 1 & 4 persists. I have checked the documentation, but as an Xbox user, I am limited in terms of external configuration files. Does anyone know a specific EFB setting or a sensitivity curve that fixes this asymmetric engine behavior? Thanks for your help and patience!

I solved it my disconnecting and re-adding my navigraph account in the EFB. Then it was able to download.

Not only flap 2. it happens during all takeoff phase.... If you engage the AP when nose pitching up, it will be happened again when you disengage the AP.

Hey there, ever since owning this aircraft (which is fantastic and good fun by the way) I asked myself if the engine start sound is really correct. The Trent XWB has this very distinctive growl when starting, very similar to the GE90. In my head, this should start exactly when the fuel flow starts and the combustion starts. In my sim, this sound starts much later, like five to ten seconds after the fuel flow starts and EGT rises. You can observe this behavior in many streams online as well. I started some research and looked for videos showing the startup. Unfortunately, there are not many showing the ECAM on startup. However, there is one I found, which is this one: Notice at 0:33, right when the fuel flow starts and EGT rises, the growl in the background is audible. So, question to you: Is the sound of the aircraft in the sim actually correct?

Same for me - iniBuilds please refund, otherwise Ill have to force a chargeback and file a dispute with my credit card company… I have been unable to use this addon properly since I bought it over 3 months ago… just because we are flight simmers doesn’t mean you can treat us like absolute trash! No normal consumer would stand for this

I recently upgraded my LAX in MSFS 2024 with the marketplace "upgrades". Apon installing, I noticed that the built in static aircraft that comes with the airport are missing textures. I have reinstalled the airport multiple times and yet it remains bugged. I am not sure what this could be issue here, but the default LAX that comes with the simulator is uninstalled.

Just keen to know, appears that it was dumped soon after release in a half finished state, thanks.

Hi, so I noticed that even in SU4, the flap animation for the a320neo seems still visually extended too little. Flaps 1 nudges the flaps a tiny bit, and does not move back then point down like say the fenix does. I think the a321lr does this fine, as it extends normally, but the a320neo doesn't. This is flaps 2 according to the image.

I've found this happening all the time since the last update as well. Really annoying.

This issue has also been troubling me for a long time, but it seems it has never been fixed. About 20 seconds after takeoff, the nose suddenly pitches up. Once the autopilot (AP) is engaged, it returns to a normal climb attitude. However, if the AP is engaged during this abnormal phase, then during landing, the moment the AP is disengaged, the nose also pitches up significantly. It appears to be a trim parameter issue. (All automatic assistance–related settings in the program have been turned off.)

A310 Broke for me mid December, EXT power shows avail, but when pressed does not power up the aircraft, even when spawning on the runway itself all the aircraft systems are off.

It is broken again 😞

It’s been a month - any update on this? Still broken as of 1.20