All Activity

The AP1 can be toggled between CMD and OFF using the "TOGGLE AUTOPILOT MASTER" keybind. The Autopilot disconnect (on yoke) can be used via the "AUTOPILOT OFF" keybind. The only one not mapped is AUTOPILOT ON as forcing it on via key event was causing other logic issues with CWS in certain cases. As for the 000 EPR issue, as mentioned above team is investigating the correct behaviour and working on it for a future update. Thanks!

Thank you Jamir

When you select the standard gate 233, it's still not working, or were you still attempting to use the jetway while being spawned in on the 233L/R stand options

Hello 👋🏽 SU 5 came out today alongside the 1.0.11 on Xbox Series X, and I have tried 5 different flights all of which resulted in a CTD. The first 3 had a CTD during the loading into the airports, before even clicking “ready to fly” The 4th came when trying to use the ATC, after setting up the flight, and was ready for pushback. Before every CTD i got the “Memory resources are getting low, disabling avionics to grant stability. Some settings may be lost due to this process” message. This has never happened before for me.

<removed> Looks like a weird filter thing ...

I fed your error log to the Gemini AI and got the following analysis back. I have no clue if it is of use but suggest to give it a try: WASM Crash Analysis: inibuilds A350-900 Conflict The provided error log points to a classic memory access violation (0xc0000005) occurring when multiple complex WASM modules compete for resources. While the inibuilds A350 is the "victim" here, the log reveals several other active modules that are likely triggering the instability. Identified Conflict Candidates Skyline Simulations (WMKK) - Primary Suspect: Log Entry: [SS_WMKK_Airport_Driver.wasm] SS_WMKK_Airport_Driver: Initializing... Reasoning: This driver belongs to the Kuala Lumpur (WMKK) scenery by Skyline Simulations. Interestingly, the log shows this driver actively reading the AIRCRAFT_TITLE of the A350 right before the crash. This interaction suggests a direct conflict between the airport's custom logic and the A350's WASM environment. Noolaero VDGS (Multiple Airports): Log Entry: [noolaero-vdgs-xxxx.wasm] EXCEPTION 25 Reasoning: These modules manage the Visual Docking Guidance Systems for various airports (LPPT, ESSA, EIDW, LSZH, etc.). The log shows a flood of "EXCEPTION 25" errors. While these might not always cause a CTD (Crash to Desktop) on their own, they clutter the SimConnect stream and increase instability. FSDreamTeam (FSDT): Log Entry: [fsdt-msfs-bridge.wasm] Reasoning: This is the bridge for GSX or FSDT sceneries. It is active but generally stable; however, it adds to the overall WASM load. The Fatal Sequence The crash occurs immediately after the SS_WMKK_Airport_Driver identifies the aircraft. Simultaneously, the A350 fails to locate several PNG texture assets: WASM: Error during EFIS_gauge_draw execution. Error code : 0xc0000005 This indicates that the memory address the A350 was trying to use for its gauges was likely "stepped on" or blocked by another module (most likely the WMKK driver). Recommended Troubleshooting Steps Isolate WMKK: Temporarily remove the Skyline Simulations WMKK folder from your Community folder. This is the most likely fix, as the crash occurs exactly during its initialization phase. Update/Disable VDGS: If you are using a standalone VDGS package or sceneries from Aerosoft/JustSim that use Noolaero, ensure they are up to date. Clear WASM Cache: Delete the contents of the WASM folder located in your LocalState directory (the path varies for Steam/Microsoft Store). The simulator will rebuild these files on the next launch. Use Addon Linker: Since the A350 is a resource-heavy aircraft, use an Addon Linker to disable unnecessary airport drivers (like the ones for Dublin or Stockholm) when you aren't flying to/from those specific locations.

Aircraft F406 currently missing from Library after SU5 update.

HI, today I mixed up during the iNS inittialisation two numbers. Result: magenta point (aircraft) on the INS map at wrong position. I didn't find a way to fix it. I did several re-initialisations of the INS. Re-Import Simbrief Flightplan. Switched form INS1 to INS2 etc. etc. But nothing helps, beside a restart of th Tristar. Any idea or experience with this situation?

Did you install any new liveries between now and then? Additionally SU5 is now out. Let us know after updating if this is still an issue as well as on the Microsoft Forums where they can ingest and diagnose the issue if found, thank you. https://forums.flightsimulator.com/

Approach mode arms itself at a certain distance or configuration. I'm no pilot by any means but I do know Airbus does that. G/S I believe will activate when below glide slope. It shouldn't activate when you above it. I can't explain the Nav IR. Probably a bug. Dumb question...could you turn the LS button off at any point and it would stay off? Slide deploying at the terminal may be because you didn't disarm them before open the doors? Step alts deleting themselves should not happen. May be a bug. Have never experienced this. I personally input STEP ALTS manually to avoid the WASM crashes and screwy ETA and FUEL calculation issue that arise from the auto input STEP CLB setting. CPU spikes can't help with because I am on console. Click spot issues I have encountered. Can be a pain in the butt.

Hi, if it still hasn't appeared, have you attempted to logout and back into the IniManager, as well as downloaded the recent update for the IniManager?

Hi, this is a known issue that the team is aware of, thank you 🙂

Hi guys, just a quick question. Is it normal SID ALT constraint gets active when bring the throttle to CLB? DEP OPKC set cruise ALT to FL390. When bring the throttle back to CLB SID ALT constraint shows up as FL070/7000. Not sure if this a350 behaviour normal.

I'll pass this along to the team, thank you 🙂

Hi Team @iniBuilds since past few updates the INCPT turns get curved which was not an issue in some of the previous builds. Screenshots attached.

Hi, so this isn't to say that the issues aren't happening on your end, however I've done 2 flights on 1.2.5 since it released public. I have yet to encounter any of these issues outside of the "Autobrake Off". I'll give Direct To's another go as admittedly my route was pretty straight-line both times and one of the landings was into Quito so you can't really deviate there. I'll keep an eye on that TCAS one as well as I noticed yesterday on VATSIM my MODE C was randomly off even though I was set to TA/RA in SURV page. Thank you

Similar situation here today. On my way from LSZH - RKSI, (V 1.2.5) after 6h 15 into the flight just before the chinese border the plane got off the planned course. I tried to correct it with a "direct to" prompt but the FMS did not show any reaction. Tried to disconnect the AP, same result. All attempts to interact with any system of the plane were unsuccessful. I checked the course on Volanta and Navigraph charts and realized that the plane was flying a circle and realized that the chrono wasn´t running anymore. After all, I could not intervene in any way so all I could do was to exit MSFS24 and close another chapter of experience. Besides the usual WASM-Crashs (orange screens) and the usual additional tasks like calibrating the throttle etc. I never had any problems. I successfully completed short-, long- and ultrolong-hauls like WSSS-KEWR - this was a new one. Maybe somebody has made a similar experience and knows the cause of this and has a solution. Btw just FYI I use BATC und FSLTL and ACARS running in the background. Unfortunately no error log of this incident.

You do NOT need to fly in LOC mode before ILS. When you're intercepting the localizer you just use ILS (or APP in different aircraft). I have no idea why so many people do this, the only time you'd use it is if the G/S is not working.

I was having some poor FPS at Heathrow so went in to the inimanager to try and toggle some options but I found that the options had all disappeared and only left Landside cars and 3D people as options. reinstalling the scenery makes the options appear again but they will disappear again for some reason when checking later Inimanager also keeps thinking that I have the 2020 version installed too despite uninstalling both then only installing the 2024 version

With the latest updates. Half of my liveries will not appear. Not selectable under configurator. I have uninstalled and reinstalled several times both the L1011 and the liveries with no success. Any assistance is appreciated.

Hi All, Firstly, I'd like to express that I am really enjoying the aircraft and flying it in the sim. Something I've noted as an improvement to the aircraft model to make it more realistic; As modelled, when the flaps are extended the spoilers deflect downwards to smooth the gap with the flaps. There is however also an additional panel (which doesn't act as a spoiler) between the inboard spoiler and the wing that also deflects/droops downwards in line with the spoilers which I've highlighted with the red box. I understand this panel moves downwards through all flaps settings (although the below screenshots are at flaps full) This isn't modelled in the sim. It would be great to see this modified in a future update! For even further realism, there's also another part of the wing between the outbound spoiler and the aileron that droops down as well. (although I appreciate this second part I'm pointing out is a really minor detail and generally isn't seen) Thanks for reading!

You assume that the person you're talking to is ignorant on the subject without knowing it, you start acting like a schoolteacher and treat me as if I were staring at one of your students, you don't know the problem you're talking about (you admitted this), you don’t know it is a bug and if you go watching in Inibuilds’s Discord you will understand it is a known problem , anyway you intervene only creating confusion, I respectfully replied to you, thanking you and not offending anyone and you offend me in response, who is the “nice guy” ?! please, and have a nice day

Hi, I’m experiencing a texture issue on the A310. I didn’t have this problem during my previous three flights, so I’m not sure what changed. Does anyone know what might be causing this? Thanks in advance.

Cheers mate, I posted on the fsdt forum and they confirmed that there is no support for the l101 yet. Basically as you enter parking gsx reads the aircraft icao code to know where the stop position is. As yet that icao does not exist in gsx hence why it doesn't work. Even if you modify the parking position the lack of icao code means it just won't work for parking guidance. Fsdt confirmed that support will only become available once it is available outside of market place.

What a nice guy this one, hahaha. See ya "thanks"