All Activity

Pong was my first … late 70’s … it set my career path … something so simple 🙂 yeah, getting sick of having to accommodate thieves pretending to be Robin Hood’s … they’re just some pathetic excuse of a human using limited resources and air which could be put to better use for people that actually care …

I just found that only the FO side oxygen test button can function well. The captain side's oxygen test button cannot be clicked.

Do you have footage of this occurring? Busy at the moment with other tasks but want to get that logged for the team, thank you.

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

Known issue being resolved in a future update, thank you.

Logged for the team, thank you.

External clients are using legacy fuel systems and need updating to FS24 standards. Same issue is seen on Asobo 737 for example which is also using modern system Thank you.

Surely this isn’t a new thing that you’ve heard of ?

The A300 , A320 Neo and A340 and A330 and A350 all do it fine although it’s very different to the Tristar. from where I am. If I tune the ILS freq for x runway and set the Tristar switch to radio it should pick it up instantly. it doesn’t.

Hi, someone else had suggested this and is now an ongoing item with no ETA for delivery, thank you 🙂

As someone that frequents BMS, I am so glad that someone told me to bind in the launcher and not in the sim 😄 And yes, the Marketplace serves as a way to combat piracy, thank you 🙂

Known issue, thank you.

This is something that is already on the teams list of todo items, no ETA for the delivery, thank you 🙂

Had several WASM crashes over the last week, each time entering (IIRC) the VIA in the SEC F-PLN. It's not 100% reproducible, but it happens often enough to have a pattern.

I'll pass it along to the team, thank you

Hi, I am sorry but I am going to need a video of what's happening to better understand what you are saying, thank you.

The A350 is on v.1.2.4, you said you have it on the IniManager, it is possible that the aircraft isn't actually updating the version in the EFB but updating the aircraft, completely remove the aircraft content from your community folder as well as the content from the WASM folder. Let me know if this helps.

Hi, Unfortunately it sounds like you had a sim-freeze, it's a known issue that is being investigated actively and a new build is being worked on that with the hopes of being more resilient to these WASM related issues. If you don't already, enabling auto-save is a good way to avoid these issues completely ruining a flight, as it restores your aircraft to the point at which it saved before this issue occurred (you have to manually select a save from the list of auto-saved states), thank you.

Hi, the map is a known issue and the emergency slides need to be disabled before opening the doors in the OIS > Ground Support Tab

Are you able to check and verify that other aircraft (Inibuilds and Non-Inibuilds) are picking up the Localiser? Additionally what are the details of the VOR station you are attempting to acquire

Hi, ultimately the aircraft is a Microsoft aircraft and as such any actionable requests will come from Microsoft and as such through their forums. That being said every so often I fly both A332/3 and do not find myself having these issues, not to say they don't occur, but that I can't reproduce the issue. Thank you https://forums.flightsimulator.com/

It’s not about capturing the localiser. on Xbox x the localiser for an ILS freq with RADIO set doesn’t even pick up the localiser

Over the past 2–3 days I’ve been flying the A350. The first WASM crash happened at LIMC right after landing, just after exiting the runway. I thought it was just bad luck and cleared the WASM. My second flight to EDDM was completely fine with no issues. For my third flight (EDDM–LTFM), during the approach I realized that I had entered the wrong STAR. Following ATC instructions, I updated the STAR from RIXE1A to RILE1A. The moment I entered "via IMREN", I experienced a WASM crash and, out of frustration, I closed the flight. Today I started the simulator again to try the same flight. This time, before even taking off, while still at the gate, I entered the STAR (RILE1A via IMREN) and again got a WASM crash. During all of these flights, autosave was disabled, so I didn’t have a file available. I restarted the simulator to try to reproduce the scenario with autosave enabled, but this time the issue did not occur. Before the last WASM crash occurred, I deleted the WASM folder, removed the aircraft and its livery, then reinstalled them through inimanager. I also updated Navigraph, installed the terrain data, and restarted the simulator. Aircraft: A350-900 / TC-LGS Simulator: FS2024 Navdata Method: Navigraph OFP: I don’t think the flight plan is related to this issue, as the crash can happen at any time and anywhere. WASM Error; WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty WASM: Error during MFD_gauge_draw execution. Error code : 0xc0000005 Specs: Windows 11 Pro 24H2. CPU: Ryzen 7 7800X3D GPU: NVIDIA GeForce RTX 4080 Super RAM: 32GB DDR5 6000Mhz Autosave File: I followed the specified file path, but there were no files there, so I do not have an autosave file.

I have to be honest, in all the flying I've done so far in the Tristar, I've never come across ANY INS drift. With it turned on in the efb, the aircraft is still crossing all its navpoints with laser-like accuracy. Also, when turning any of the INS units to DSR TK/STS, I would expect to see the accuracy index gradually go from 01 back up to (eventually) 90. But it sits at 01 for hours and hours with no gradual inaccuracies being introduced as one would expect. Also, (just currently going an EGLL-CYVR longhaul) about a half to two thirds of the way through my longhaul, my ADI has become stuck and the needle now does not move to the fresh track heading when going through the waypoints, and the orange digital 'time' and 'miles' readouts above the ADI needle have also frozen. I got to a waypoint 9 and expected the aircraft to auto select and input the next 9 waypoints as it should, but this didn't happen, so that the aircraft began circling at cruise level as seen in the image below.

Appreciate the reply as it’s quite a tricky thing not to have working. Thankyou Inibuilds.