All Activity

The A300/A310 alarm can be a real ear-driller if you aren't used to it! Usually, you just need to hit the 'AP Off' button on the yoke a second time to silence the cavalry charge. If you’re clicking the dash buttons instead of using a mapped key on your joystick, it tends to just stay in that warning loop. I actually ended up using a simple site like https://onlinealarm.co/ on my second monitor to set 'reminder' alerts for my descent top-of-climb points, mostly because I kept getting distracted and missing my altitudes, which triggers even more annoying alarms in the cockpit.

When configuring Stanstead, button for Nool doesn't respond correctly - it just renders some half transparent tooltip text that is unreadable. Also results in the airport having both Nool and GSX screens rendered on top of each other.

Also another bug I found is that the OPT and REC MAX CRZ FL are always based on the entered figure on the INIT page rather than using the actual SAT that is present and measured by the A/C, so you constantly are updating the temperature value.

I was doing the LH715 from RJTT to EDDM, on the inibuilds A350-900 version 1.2.0, I have attached all of the auto save files of the aircraft and the simbrief OFP, I performed a std. preflight which included the FMS set up with a cpny flt. pln. request, followed by the departure, arrival, sec flight plan preperation, and the fix info and position monitor pages. The EO sid I entered was off of RJTT 16L to HNDX3 (RJTT16L/157/25) and hold followed by an immediate return to RJTT 16L with an ILS approach. Then I did the fuel and load, and to perf pages. I also imported all of the wind data and entered the T/C OAT and TROPO. I performed a successful pushback from RJTT stand 107, with gsx taxied out and then took off following the ROVER 4C off of 16L. I performed a successful Climb out up to fl350 and proceeded normally until about MARRC when I was playing around with OPT step climb function and ended up getting a more optimum stepclimb point for FL390 later in the flight, that was more optimum than what simbrief had calculated. After that, I stepped away from my PC and then the WASM crash occured within 5 minutes of me doing so. 1768160505.bin 1768160656.bin 1768160807.bin 1768160957.bin 1768161108.bin RJTTEDDM_PDF_1768153560.pdf

I had same orange screen after updating the A350 to v1.2.0 about ten minutes into preparing for a flight . Shutdown, cleared the WASM, updated terrain and Navdata only to get a crash to desktop about two hours into the flight - no idea why and Windows Event Viewer just says MSFS2024 crashed but I suspect it is A350 and therefore WASM related. Never had a WASM crash in any of the previous versions. Something is clearly slightly up with v1.2.0.

Dear iniBuilds Team, I had this WASM crash when I entered the Arrival Route on the left EFIS. To reproduce Before leaving cruise level Enter Arrival Route for LSZH RWY14 RNV14 (There were several dashed lines, however I could not reproduce them again) AMI14 NEGRA2A Systems freeze Information Aircraft: A350-900 (HB-IFA Wanderlust) Simulator: FS24 Navdata Method: NAVIGRAPH OFP: attached Specs: Intel Core i0-10900KF CPU @ 3.70 GHz, 64GB RAM, NVIDIA GeForce RTX 2080 Ti, 11GB RAM Autosave: not available, as reloaded flight before sending report WASM: Error during EFIS_gauge_update execution. Error code : 0xc000001d Volanta https://fly.volanta.app/flights/ebc2f137-87c0-4e44-a10f-871e4068dacc Kind regards Airliner001 VIDPLSZH_PDF_1768118427.pdf

Hello, I would like to suggest a few improvements that could make the Airbus A340 more complete. I am endorsed as an M2 Aircraft Mechanic on the Airbus A330. The A330 and A340 share many similar systems. I noticed several elements that could significantly enhance the aircraft’s realism. - Failures: A section should be added to allow failures to occur based on the aircraft’s condition. In the real world, pilots rarely fly perfectly functioning aircraft. In line maintenance, we constantly apply the MEL, and pilots often operate with certain restrictions. In the simulator, however, the aircraft is always in pristine condition, which removes an important layer of realism. - RESET pushbuttons on the overhead panel: These reset switches are crucial during Airbus A330/A340 maintenance procedures. Making them functional would greatly improve the accuracy and realism of the A340. - MCDU ACMS / CMS section: These pages are widely used in maintenance. To enhance the realism of the A340, users should at least be able to view the selectable options within these sections. Currently, they are not accessible at all. - A340 Avionics Compartment: The access hatch is visible inside the cockpit, but it cannot be opened. It would be fantastic to include the avionics compartment located directly beneath the A330/A340 cockpit. Thank you for your time and consideration.

I did some more testing to see if it is maybe user error, but I still wasn't able to get the heading bug to shop on the ND ... Am I the only one flying the A350 with FD off? 😂

Hi all, I was wondering whether Inibuilds has ever explored the options of building the Inimanager as a standalone Xbox app that can work together with MSFS2020/2024? I can imagine there are xbox limitations but since game devs like Ubisoft and EA have built standalone apps that work with their games, would a similar thing be possible for MSFS addons? Perhaps it won’t be able to use as a platform to purchase addons on, but It’d solve the livery problem for Xbox users.

I tried more stuff and the bug is specifically in the A350-900 it works fine with the -1000

Any updates?

Both the Fenix 320 and PMDG 777 have a feature where the cargo doors “bounce” at the end of the opening sequence… it’s a tiny detail but very nice visually. Would be great if the 350 had this too.

@iniBuilds this is getting a little ridiculous now. Details below. I changed approach to RWY 14 at LSZH (NEGRA 2A). The crash happened when I tried to enter the waypoint TRA after AMIKI. This is basic stuff iniBuilds - the fact that the aircraft cant handle this is a joke. Aircraft: A340 EIS 2 + Passenger Simulator: FS2024 SU4 Navdata Method: NAVIGRAPH OFP: VABBLSZH_PDF_1768099299.pdf WASM Error: "WASM: Error during FMGS_gauge_update execution. Error code : 0xc0000005" Specs: i7-9700K, RTX2080 and 32GB RAM. Autosave File: 1768124718.bin

The A340 NOT freezing in cruise is an extreme rarity on my end... The A350 does the same even during climb. No matter if I flush the WASM folders or not. This is since release for both of them and there is no solution that works. I'm fed up with this and will make sure to stay well clear of any iniBuilds aircraft in the future unless they start offering refunds.

Unfortunately unless the 3rd party developers update it, the external and internal graphics are broken, Also, at present, all generic liveries downloaded from Inimanager have generic, none airline specific colours on the interior too. Looking forward to an update to correct his.

Same in A350. In past update i’m able to enter trip wind, but with latest i can’t

fix the front left door please

As seen in the recording, I am experience severe fluctuations of Engine Fuel Flow indications on all displays. This occurs on almost all flights, especially in the Engine Startup and Cruise phases. It happens sporadically (in that the indications fluctuate a lot and then stabilize, and then start fluctuating after a minute or two again). Fluctuations can cause the Fuel Flow to drop to 0 or climb up to the millions, and it hinders pilots' abilities to gauge current engine indications. I have re-installed MSFS2024 and the ini a350 in the timeframe that I have experienced this bug, and both have not fixed the issue. How could I fix this or would this be fixed in the near future? Recording 2026-01-11 150221.mp4

As seen in the screenshot, the attitude pitch indicators seem correctly positioned, but the PFD seems to be severely offset upwards to the point you can barely see half of it. The FMA is also not visible. I have experienced this bug on all flights since around 1 or 2 updates ago, and have done a fresh reinstall of MSFS 2024 and the ini a350 in that timeframe, but the bug still persists. How could I fix this bug, or will it be fixed in the near future?

Hi iniBuilds team, a high fidelity airport in the Spanish capital could be a very good airport, comparing to other big hub airports that already has a pretty good developer and you guys too! LVFR LEMD is also very outdated by now and the Spanish flyers or even pilots that fly into LEMD can agree and needs and update and why not have the best scenery developer to do it :)

Bumping, any news on this Ini team?

any news on this from the staff?

Looking at streams, the hundred above has not been changed, hope that gets changed before this update with other fixes and the VIP (which I personally don't care for) Also, any news on an a350 update soon? ^The same thing also has to be changed for the a350 although you guys are aware in other threads.

Actually going to add something with this now that I realise what you mean. The 5 callout oes seem to be 1-2 feet above the ground and this is the same in cockpit videos from what I have seen when I did take a look at this.

When I am pushing back using GSX when the plane is lifted off the ground the planes starts moving forward on its own?? And then I select to start the pushback. The tug spawns by my plane and when they are releasing the tug my planes starts moving forward again