All Activity

windows + shift + s to take a sreen shot, or the print screen key.

Doing the usual VHHX-RJTT, take off RWY13 Track 136 115.5 VOR, climbing 7000 till WHISKY in 1.0.4 Tristar Dial in FL370, haven't pressed any button to intervene/change. ALT window changes from 7000 ALT to 7200 ALT CAP (while 37000 is in the SELECT ALTITUDE box) and slowly climbs, uncommanded 500FPM. Fine, what ever, we are going to climb anyway. Hit VNAV, plane climbs at 500FPM. Cycle TM button to get the PMS EPR to work, and then we get climb thrust (apparently we shouldn't need to cycle TM button, just hit VNAV). So now in CMD1, TM/VNAV/VOR, happy at 250knots. Plane heads upwards, trim wheel start slowly turning to pitch up, and up, and up. We are now >6000FPM and speed quickly dropping. Stick pushes forward to slow climb rate and gain speed but the trim wheel continues to trim for a nose up attitude for some time. Eventually it all sorts itself out and we doing M0.83 to FL370 Anyone else have the trim wheel and stick fight each other? Below picture was borrowed from another post but illustrates the sequence needed to gain altitude.

Hong Kong usually defaults to traditional Chinese. “First Class” should be 頭等 “Business Class” should be 商務

Hello After updating version 1.25 these days, I used the new version to fly the ZBAA-LSGG-ZBAA route. The first leg of the flight experienced a simulated freeze and the plane crashed directly. After about an hour of recovery through AUTO SAVE, the simulated freeze occurred again and the plane crashed again. After recovering through AUTO SAVE again, it returned to normal. After landing, I cleared the WASM folder. After about five hours of flight, the second segment of LSGG-ZBAA experienced simulated freezing again. The plane deviated from its flight path and spun around. Normal after recovery through AUTO SAVE. Fly at double speed throughout the entire journey. The previous 1.24 version also experienced simulated freezing, but after clearing the WASM Wenjia folder, it did not freeze again. Frequent freezing occurred after updating version 1.25. Yesterday, I flew back and forth for a one-way trip of three hours, totaling six hours. Everything was normal.

After updating to version 1.25, I flew a long-haul route following the actual route, ZBAA-LSGG-ZBAA. During the outbound flight, the system froze twice, resulting in a crash. For the return flight, I cleared the WASM folder before preparation. During the flight, the avionics system froze once, but I was able to recover it through AUTOSAVE. @iniBuilds

just an update, I have a clean install on a new computer. Ready for the SU5. But not with a fresh install, NONE of the liveries will appear under configuration.

noolaero again, I've deleted every instance of noolaero, but I am yet to do a flight. You can run a simconnect log file, I found in mine that there were too many requests to simconnect just before the crash and it couldn't keep up, this was 6 hours into a 12 hour flight, and again taxiing into the gate after a 6 hour flight, the module ID was related to noolaero. Some airports are shipped with a noolaero wasm file in their scenery packages. SU5 was released overnight let's see if that had any affect on it.

Appreciate the support guys. Cheers and thanks for bringing this aircraft to the sim.

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.