Systems

Every time I update, it stops after a while, or it gets stuck, and I wonder if there's any way to circumvent it or update manually

Hi, I have found out that it is not possible to continue the flight after landing on the first leg and start up again to do the second leg. After pushback to start the second leg in the same simulatpr session the engine spool up, but never get to work, choosing the panel state to "On APU" is not solving anything (also then the engines are not coming alive), only solution is to choose "ready for take-off panel setting..... What to do about this?

When selecting a Localizer approach from the FM in the A350, the FM by default flies the aircraft using FLS. When established on a Localizer approach, the FMA should show F-G/S and LOC. This is because the FM is programmed to create a pseudo glideslope called F-G/S but will utilize the localizer signal from the localizer transmitter on ground, and therefore the lateral FMA mode will be LOC. The iniBuilds A350 incorrectly shows lateral mode F-LOC during a Localizer approach (see photo). The correct FMA should show LOC. F-G/S LOC should be the correct FMA shown in the A350 when flying a Localizer approach, as selected from the FM database. Thank You.

I attempted the LDA W approach, runway 22 at RJTT. In real life, after selecting LDA W 22 and inserting it into the F-PLN, there should be a LOC index along bottom of the PFD where you can monitor the raw data localizer (in this case IKL 110.1, course 277). Nearing waypoint BONDO you would arm LOC in the AFS, and then preset the FPA of minus 3 degrees. Almost at waypoint BONDO you would then pull the FPA knob and fly the approach in FPA LOC (with an FPA of -3deg). I was not able to bring up the raw data Localizer Index at all at the bottom of the PFD. As shown in first photo, when selecting LDA W 22, by default it shows FLS with the F-LOC and F-GS index. When de…

Aircraft: A350-900 Simulator: FS2020 Navdata Method: SIM DEFAULT OFP: Not needed, did not happen during a flight-plan/route procedure event WASM Error: WASM: Exception c0000005 in gauge Systems in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm Specs: i7-7700k GeForce GTX1660SUPER 4x 8GB GSkill Trident Z Reproduce: So prior to this, I deleted the contents of the WASM folder as described herein the forums. I then updated to 1.0.2 using iniManager I then loaded up into a default WSSS with the Singapore Airlines livery. …

Updated to version v1.0.2 I am unable to move the flaps lever. The lever is stuck in 'Full' position and if moved immediately reverts to the 'Full' position. It won't move from the full position either using the mouse or via keyboard - both in MSFS2020 and MSFS2024. Aircraft is unusable. Any ideas?

Because of the size of the X cursor and circle cursor, I can't click recall in the mailbox.

I am trying to send an "ACARS MSG" or free text to another aircraft, but I'm unable to select FREE text on the ATC COM page. Is there supposed to be a separate ACARS page where I can send free text via hippie ACARS?

I’ve recognised a problem with the route on the Navigation Display. See the picture i’ve added.

Will try to keep this useful... Wanted to try out the new patch (which so far is much better from a crash/freeze perspective so well done for cleaning up the bits you have) The Change log is extensive so credit where credit is due.... Ive interacted with it on few short sectors and have done everything I'd do on a line flight (radial ins, extended ceterlines, route modifications, directs with/without abeams etc..so far no crashes so well done for the fixes. Please also take the assumption the aircraft has been set up correctly in line with realworld procedures. Not a 350 driver but fly 320 CEOs/NEOs. MSFS2020 Version 1.0.2 A350-900 TAKEOFF …

Since 1.0.1, there has been a problem that the autopilot randomly switches off during cruise flight and pulls the aircraft upwards at a 90 degree angle. This happens at a random time and cannot be explicitly reproduced. However, unattended long-distance flights overnight are not possible because you never arrive.

After GSX is done loading and during loading, the TOTAL pax remains at zero, and ZFWCG remains at 0. Additionally, if you add up all the pax stations, it does not equal the planned pax.

On the flight plan page and the ND, altitude and speed constraints that will not be made should show amber color. At this time, they show as magenta, whether you’re going to make them or not. Hopefully, this will be updated.

As said above, on the A350-1000, I can not select, which Sharket/Winglet Type I would like to have. The option is not available. Using 1.0.2, but the issue was existing as well with 1.0.1 and 1.0.0 . WASM was cleared and Aircraft was reinstalled to troubleshoot. Please have a look into it. Thanks.

I had this WASM crash when I tried inserting the received F-PLN from SimBrief. To reproduce Request a F-PLN from SimBrief and try inserting it. Sometimes it hangs, sometimes it works properly. Information Aircraft: A350-900 Simulator: MSFS2020 Navdata Method: NAVIGRAPH OFP: Loaded via SimBrief Specs: Ryzen 7 5800X3D, RTX 2080 TI, 32 GB RAM WASM: Exception c0000005 CommBus callback in module m178088ef2d4800fa WASM: callback execution for event NAVIGRAPH_FunctionResult, in module m178088ef2d4800fa, failed

I'm downloading a flight plan from SimBrief. I I want to update my fuel so change the fuel load value, I click Set Fuel but nothing happens? My FOB value remains at 300Kg's before and after. What is wrong?

When trying to enter the winds aloft for the enroute fixes that are missing the wind numbers (<- known issue), the system does not allow entries above 100 kts. When I try to enter e.g. 118 knots it won't accept and gives "Entry out of range" message, resetting my entry to 000.

Hi I was flying OTHH-OMDB in the A350. While taxiing, i was going to do the before takeoff checklist, when all the displays suddenly freeze (nav, both CDU). I only managed to check the first three lines on the checklist Aircraft: A350-900 Sim: FS2020 Navdata: Navigraph Specs: Ryzen 7 5700X, RTX 4060 TI 16GB, 32GB RAM WASM error:

WASM: Exception c0000005 CommBus callback in module m178088ef2d4800fa WASM: callback execution for event NAVIGRAPH_FunctionResult, in module m178088ef2d4800fa, failed MSFS2020 Navigraph data 2303r1 To reproduce: Load in LFBO Attempt to connect Navigraph - does not work even though Navigraph appears connected. Therefore unable to update. Switched to default navdata but encountered issue with missing SIDs at LFBO. Load flightplan LFBO-EKCH Go to FPL INFO, FIX INFO, Enter LFBO14R When will you start replying to my email tickets?

When using sim default navdata, in most STARs the waypoints generate 6 000+ miles away, dropping my FPS to about 10.

Hi guys, noticed cursor movement is stuttering and quite jittery on the displays. It's not fluid smooth like flybywire a380. Please fix. Thanks

See attached screenshots. 1. holding was set up for a parallel or teardrop entry, but the aircraft attempted to perform a direct entry. After leaving the holding aircraft does not reset the speed back to 250 even though there is no specific speed constraint. Tested both direct with abeam and direct, aircraft stayed at 230 kt Somebody was mentioning something about competency to refine holdings in the A300, I wonder if that was then lost or? 🙂

Hi Team I wanted to bring to your attention that the ATIS COMM's is currently not working for me in, despite us using the third-party Hoobie code. I was wondering if, in the future, we can explore a solution that minimizes our reliance on third-party applications. Specifically, would it be possible to use Navigraph, a reliable source, to directly support the latest ATIS weather reports? This could help streamline our operations, reduce the need for additional apps, and minimize memory usage on the PC, ultimately decreasing long-term dependencies. Looking forward to your thoughts on this.

I've noticed some issues with the VNAV in this aircraft. When flying on a STAR (Standard Terminal Arrival Route) and encountering a manual leg with a disconnect between the approach and the STAR, the plane tends to forget its current situation. It accelerates to over 300 knots and begins to climb and shows that I'm 99 feet below the path on my PFD. It lasts for about 5 to 10 seconds before the aircraft eventually corrects itself, realizing it is arriving rather than departing, and then slows down and stops climbing. Additionally, I've observed that the aircraft often disregards the set speed in order to get back on the path. For instance, if I'm below 10,000 feet and…

Hello everyone, I like to create a flightplan with Simbrief and then enter it manually into the airplane. When entering the flightplan into the MCDU (of the new ini A359), I begin with the INIT page of course, then entering the SID and then it comes to the flight plan... When I have a "waypoint" DCT "waypoint" in my OFP, eg "MEN DCT NINUN", i can enter it normally and everything works fine. But when I have an airway inbetween the waypoints eg. "NINUN UN871 OMASI" (on my way from LFBO to EDDM) and I click on the last waypoint in the existing flight plan, click on "Airways" and enter exactly those airways and waypoints and send it to TMPY FLT PLN.... Everything is mess…