Systems

Hello, I have version 1.1.4 and flew from EGLL to KJFK yesterday. While approaching KJFK at approximately FL220, the autopilot failed for no apparent reason and wouldn't reengage. Since navigation using the manual heading and altitude also didn't work, I aborted the flight. Perhaps someone has had the same experience and has a solution. Best regards, Guidschi

Two issues in one go: First, after departure from EBBR, I suddenly received a TCAS overlay on the VSI. I didn't get any explicit climb or descend instructions, nor did I see any traffic on the ND. There was also none in the SURV TRAFFIC page. To fix this, I tried recycling TCAS, disconnecting and reconnecting from VATSIM, and nothing worked. Even offline it continued to show the overlay. This is shown in image 1 Second, I had 2 conflicts with aircraft that I would never have a conflict with as I was climbing out and at cruise. This is shown in image 2 and 3 Autosave file included for the first situation in case it helps TCAS.bin

fixed

1. In the middle of the bird the FPD is the inner circle. It should not exist with FD off. 2. Delta speed and synthetic runway function on HUD are missing 3. Flight path angle sometimes incorrectly shown on HUD and outright missing on PFD (-3 selected by approach). in the image below, while already descending at 2400fpm, the -3 path is suggesting 12 degrees pitch down. also, manual selection of FPA on AFS CP has no effect! (for example, in the first image, the selected FPA is -2.3 pulled) FPA -3 shown above horizon

Hi, I just want to address if this is an issue for anyone else other than me. Whenever I hit "Direct with Abeam" to a way point, I get two weird lines and it also messed up the ETA and fuel prediction stuff. I tried to fix this issue by hitting a normal "Direct" afterwards, but to no avail. This issue was not apparent if I hit "Direct" to a waypoint normally, and only happen if I use "Direct with Abeam" to a waypoint. This was also not an issue in previous releases and this is not the second time that has happened to me while using V1.1.1. If you need any other information, please let me know. Thanks for the help.

BKPR Pristina (Kosovo) is showing up as “Not in Database”. I get get the charts up on my iOS app, and the FMGC is accepting it as a valid airport. But when I try to select it in the Nav Display, it says it can’t find it. I’ve searched by ICAO, IATA and City name, I’ve also used the old ICAO code LYPR. Is this an iniBuilds "thing" or a Navigraph issue?

Morning All, Just tried requesting a PDC at EGLL + logging onto EGTT in the air (above FL100) and nothing happens. It says 'last notified........1320z' when I do so but doesn't actually log on. Any suggestions? I have got all the correct fields filled out in the EFB (S.I. Hoppie and Navigraph API keys). It does however work on Flight Sim Messenger (web based) but it's like the A350 isn't talking to the S.I. servers. I have spoken to S.I. and they have confirmed the A350 isn't talking to their servers. Help?

While doing a flight from wsss to efhk, I input the step alts as per the flight plan (FL340 to FL400) with auto step climb enabled. However, after executing, the FMS indicated that the aircraft will only reach a final level of FL360, and the rest of the step alts disappeared. In the process of trying to fix it, the aircraft did weird things like climbing to FL400 unexpectedly (I was less than 1 hour into the cruise) . I definitely did not enter the wrong way points as I cross checked multiple times with the simbrief flt plan. Am I doing something wrong or is it broken?

During long-haul cruising, WASM crashed without any user input. To reproduce: Unknown Information: Aircraft: A350-1000 Simulator: FS20 Navdata Method: NAVIGRAPH AIRAC2505r1 OFP: PDF attached. Specs: Ryzen 5 7600, NVIDIA RTX 4060, DDR5 16GB Autosave: Attached latest .bin file before crash. WASM: Exception c0000005 in gauge EFIS in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-1000/panel/inibuilds-A350.wasm RJAAEGLL_PDF_1755052024.pdf 1755078705.bin

Simple as that, really. With the Hoppie ACARS connected, auto update does nothing. It will update the ATIS once but then never again as if auto update was never enabled. This is what's on the hoppie logs, request 19545163 was the initiation of auto atis, 19545414 was me manually updating the ATIS once I realized it did update and I just never received it. I've, in previous flights, turned auto atis on a good way's out and still didn't receive anything until I manually requested the ATIS

The fixes could use some work. First issue is inability to draw abeam intercept as shown below The ABEAM button is grayed out and clicking it does nothing Another issue is inability to add the intercept of a radial / radius as a waypoint The button isn't grayed out but clicking it does nothing and no new waypoint appears on the flight plan Both of these functions are rather useful when it comes to flight planning as sometimes I find myself needing to use fixes to be able to, say, mark FIR boundaries, define when I contact ATC on VATSIM, and so on I've also included an autosave to make it easier to reproduce the issue, load it up i…

Hi, I'm currently doing a flight and both of my engines have got low oil pressure warnings. Is there a way to refill oil inflight without having to be on the ground with engines shut off?

Hi, After the update I was unable to load the A359, my sim was stuck at 100% for more than 10 minutes waiting... Later I tried to use the Inibuilds app to reinstall the aircraft, but when it asks for confirmation and you press "Confirm" to uninstall the aircraft the installer does nothing. I am stuck with no aircraft, and unable to remove the aircraft from my flight simulator properly. Anyone else?

Hello there. You ask me to send a video! that does not fix the problem. I am sure there are many other users with same issue (as I see online). The throttle can no longer be set on the tablet, the throttle inadvertently spools up or down and you crash. I changed all bravo quadrant configurations and nothing helps. Msfs2020 config and nothing helps. All other Airbus aircraft from other vendors continue working without intervention. There must be a fix on the tablet or else. Please help as I cannot use the A350 anymore. (no need to show you a video, simply, check the tablet for control settings) Thank you.

i have the subscription of navigraph,but when i connect to the ois,it show that i have no subscription.But in the ois i can use the chart provided by navigraph.i try to re-install the plane,reset the link of navigraph,and also clean wasm,this three ways are didn't work. By the way,my subscription of navigraph access is until 20 jun 2026.There is no such thing as a lapsed subscription.

I have installed ORBX YBBN v2 and attempted an autoland in an A359 on 19L, however the aircraft lands short of the runway. I then attempted the same landing using a Fenix A320 and landed fine, so the scenery is ok as is the Navdata. I did notice on another autoland at VHHH a few days ago that the A35K made a violent turn away from the runway just after LAND was annunciated. Has anyone else experienced similar?

Hello inibuilds team, I find that the GSX cannot load the passenagers for A350-900 now. When I start the GSX "Request boarding", it only upload the cargo...(And at this time the simulator will stuck periodly). Here is my actions: Import the flight infomation from the simbrief in "FLT OPS STS" Import the load infromation from the simbrief in "LOADSHEET" Click the Load by GSX in the OIS (I'm sure that the GSX has been sync with the simbrief) The verison of the A350 is V1.1.2 and the version of GSX is V3.6.4 Thank you!

hello. after 10h flight, on touchdown and decel, cockpit freeze. WASM: Exception c0000005 in gauge MFD in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm

Descending into KLAX. Got cleared for approach so I switched on LS and VV. Suddenly the speed, heading and altitude were no longer in managed mode. So I pushed each knob in. The PFD and NAV displays flashed for a moment and the dot next to the display came on for just a moment but it disappeared. I tried disengaging and re-engaging autopilot but that did not help. Even in non-managed mode, I could not get the aircraft to obey my selected heading, altitude or vertical speed. Autothrottle still worked and obeyed the speed on the FCU, but the other FCU knobs no longer worked. I was not able to put the aircraft into APPR mode either. AP was turned on, but pushing the APPR but…

Hello The aircraft on either version (900 or 1000) doesn't taxi after pushback is done with GSX. This has not happened on earlier versions but now it seems that the aircraft is stuck on the ground even with parking brakes off. I'm not using rudder pedals, just a joystick and a throttle quadrant. Hope for a solution on a future version.

Hello I've been trying to get the aircraft moving after pushback with GSX but the aircraft won't move forward no matter what I do. The parking brake is off, GSX Tow Truck is disconnected and the engines are on but the aircraft is stuck. Does anybody know why? Thanks for an answer.

I did a clean reinstall, I cleared the WASM folder, when I am loading the FMS, the plane is frozen again, literally nothing works, the autopilot panel knobs will not change, the FMS will not change. The only thing that works is the OIS, back to the hangar the plane goes. This very frustrating that I paid money for this aircraft and it will not work, this has been happening again again and again.

As shown in the figure, the simbrief account is entered correctly and the flight number and payload can be imported normally. However, the flight plan cannot be imported into the MCDU. After clicking the CPNY F-PLN REQURST button for a while, it returns to its original state Especially for long-haul routes exceeding 10 hours, short-haul routes can be imported but with significant delays, while long-haul routes cannot be imported at all

ini350 has been lunch couple months, untill version 1.1.2, still have too many bugs. 1.Yeaterday, I fly from ZUUU to KLAX ,through 12 hours fly, when touch down , warsm happened, I really fxxked up!!!! 2.1.1.2 cockpit light not available, the light is on,but cockpit still go dark. 3.hud still have bugs ,the biggest one is FPV not correct. 4.VOR display goes wrong ,looks like a new bug. 5.Under VR mode, hard to click on the screen, this bug go through 1.0.0 to 1.1.2. 6.about autoland ,when main gear touch down, aircraft suddenly goes left, flare mode also wired, same airport, sometimes flare looks fine ,but sometimes even no flare, just hi…

As titled. I had issues with flap stuck on 1.1.1, not fixed as well.