All Activity

Sounds like something is not initializing during the initial load which is causing issues, try clearing the WASM again (I hate to say it but this is kind of the turn it on and off again when it comes to this type of issue)

Hello team, any updates? We could need a few flags down there to help us land haha

On the same flight after 7hours WASM crash without touching anything. I love this airplane and I appreciate your steady work and improvement. But from today standpoint it’s worse than ever before. Sorry to say but this beauty needs to go to hangar until all is addressed to get back the fun. I know it’s Asobo too creating issues for developers like inibuilds, but hard to say I paid for it and would love to fly it again. thanks and best regards Andreas

When in ARC mode on the nav display selecting any other mode (PLAN, NAV, VOR or LS) the range selector increases one level by itself. For example, starting with with 40 NM set on the range selector knob and the ND set to ARK. Set the ND to NAV and the range knob will move to 80 NM. This happens in both the left and right seat. The opposite is also true. When in any mode that is not ARC, the range will be decreased by one level when selecting ARC on the ND.

Aircraft: A350-900 Simulator: FS2024 Navdata Method: NAVIGRAPH OFP: Happened on oceanic routes WASM Error: WASM: Error during EFIS_gauge_update execution. Error code : 0xc0000005 Specs: RTX4090 - I7-14700KF - 64GB RAM Autosave File: / 1773754170.bin

Any update on this?

Aircraft: A350-900 Simulator: FS2024 Version: v1.2.3 (iniManager) Navdata Method: NAVIGRAPH WASM Error: WASM: Error during MFD_gauge_update execution. Error code : 0xc0000005 Specs: i9-13980HX + 4060laptop + 32GB DDR5. Autosave File: Sim & Environment: Simulator: Microsoft Flight Simulator 2024 Weather/Time: Real weather Steps / Context leading to the crash: After landing at RJTT runway 16L, the speed was reduced to 30 knots. 1773751486.bin

Yes — both Fenix and FSLabs have already set the benchmark by implementing robust browser-based HTML/JS bridges, enabling seamless integration between the aircraft systems simulation layer and external interfaces. Their use of lightweight web technologies to expose avionics data, SimVars, and custom events through local web servers or WASM-backed bridges has significantly expanded interoperability with third-party tools, EFBs, and remote clients. iniBuilds, this is your opportunity to demonstrate that you operate at the same level of technical maturity. A properly implemented HTML bridge — with structured APIs, real-time data binding, and low-latency event handling — would not only enhance your aircraft ecosystem but also empower advanced users and developers to build around your platform. Think beyond static EFBs: open up access to LVars/HVars, expose aircraft state via WebSockets or REST endpoints, and enable bidirectional communication for hardware integration and external displays. In today’s flight simulation landscape, extensibility and openness are no longer “nice-to-haves” — they are expected in high-fidelity addons. Matching (or exceeding) what Fenix and FSLabs have delivered would send a clear message about your commitment to serious, study-level simulation. grazie mille!

Hi, as the title suggests, it seems like sounds from engine 2 are missing/not working correctly. Here is a video showing what I mean - listen to the audio and watch the commanded thrust: https://streamable.com/14u89l This is on 2024 SU5 beta, v1.2.3 Thanks!

Good luck

The following screenshot was taken just before take off, I've noticed that instead of NAV in blue it's RWY NAV, idk if it should be like that

Latest update feedback I tested the latest update and found a few issues worth reporting: AIRAC / FMS arrivals AIRAC appears to be current, but when selecting an arrival in the FMS, all STAR and runway information disappears. This happened to me on an EBBR–LIMC routing, and the same issue also occurred for edwardthepilot during his stream. I have attached a screenshot taken from the stream. Sound balance The overall sound mix feels off. Reverse thrust sounds are significantly too loud and sound distorted. Cockpit / exterior sound transition The cockpit sound balance also seems incorrect. When both the cockpit door and L1 door are open, moving around in the cockpit causes the exterior sound level to change very abruptly from very loud to very quiet. The transition does not sound natural. GPWS volume It would be useful to have a separate GPWS volume slider. At the moment, the GPWS callouts are too quiet compared to the rest of the aircraft audio. Nosewheel steering Nosewheel steering feels too sudden and overly sensitive, almost as if the aircraft is moving on ice. Even a very small control input causes a disproportionately large directional change.

Hello, I just started a Flight based on my simbrief planning I used for all flights before last update. I‘m underway with 190to ZFW and remaining fuel of 55to. I‘m flying on FL350 and the fiel consumtion is between 7 and 7.5 to/h. It should be 5.8 - 6.2to/h. I have a tailwind of abouut 50kn. Something changed after last Update. 7to Plus is never correct for -900. any thoughts/ideas? BR Andreas

Once a again the same issue, however I've notice that when pulling back the thrusts into the CLMB detent, the THR CLMB wont appear on the PFD until I press the climb button on the FCU.

Hi, I flew from Paris to Vancouver (A350-900) and the estimated fuel consumption on arrival was more than 2 tonnes different (much lower than expected). Is that possible? I’m using Simbrief and the profile available for this aircraft. Thank you

Another WASM (sorry no pics/logs) On the grnd VHHH, inserted RWY07C, SID DALOL 1C...all OK Then ,still in VHHH, Inserted RCTP RWY23L and then TONGA 1B with immediate WASM. (No transition inputted) Restarted flight, did the same inputs in the same order and this time - all OK. V1.2.3 A35K, Ini livery,MSFS24, VHHH scenery, Navigraph used, Simbrief used. RTX 5080 Gaming PC, AMD Ryzen 7 9800X3D 8 Core, AMD X870 Chipset, GeForce RTX 5080 16GB, 64GB 6000MHz RAM, 4TB M.2 NVMe SSD, Fractal Design North XL TG Case, 1000W PSU.

@IniJamir Do I understand correctly that V1.2.3 solved (at least part) of the MCDU-entry triggered crashes, which is good, but did not yet address that "ghost WASM" issue where some cockpit modules silently freeze and the plane cannot be controlled any more? Just curious to understand, because that "ghost WASM" issue is the big one preventing me to use the A350 for months. Will try again once a reliable fix for this has been released. Please clearly communicate the fix once available, I think a lot of people are looking forward to that fix. Thank you.

Ok so I got the throttle to work (sort of), it just has this very odd several second delay when entering the input...not sure why? Could not get the LNAV to work. Could not get vertical speed to work in descend mode. I put it into the negatives, saw the input in the HUD, but it refused to descend? Manually forcing the plane to lower altitude caused it to try to raise back up. I'm guessing it's some sort of stall protection, but it is reaaaaaaaaaaaally annoying and I'd like to turn that off if possible, but not sure how. I have stall protection disabled already in game assistance settings so not sure what else to do here. Guessing this plane is still a bit buggy, or I'm just doing something completely wrong. The A320 was far easier to fly.

Good morning, I did follow your instruction and youor first option did not work. So I uninstalled A340 from Inibuild and remaining folders. Reboot my PC and made fresh installment. Now my issue is, that EFB is not working at all so I can't do any calibration on my Throttles. Sincerly

Hi again, just wanted to leave a feedback on the apu binded to the extiror engine sound. This feels like a strange workaround and is actually not really satisfying. Hope you guys could just revert it to the volume level of...was it v1.1.8? Sorry I am not sure which particular version it was, but it was fixed and good. However, overall it is really great that you guys are listening to the community. Thank you and keep up the good work!

Hi there! v1.2.3 the dome light in the cockpit again does not work and so does none of the flood lights. Integrated lighting and screens are normal.

I've done several clean reinstalls (deleting WASM and cache) and I can't find the new features in 1.0.7. Namely, the option to remove engine covers by default. Also time acceleration and pause at TOD. Can't find it anywhere in the EFB (not on the gear icon, or any of the apps). It's like the new update isn't installing. Using inimanger. Tested in PW GE Pax and Cargo variants.

Thank you! I’m new to this whole forum, where can I check for updates on when it’s fixed?

This is what I thought too! So I'm not going crazy, yeah something must have goofed somewhere along the line then as I'm very familiar with flying the a320 and have no issues with that plane. Hmm...

Could be something that occurs when initializing a runway start instead of a cold and dark state.