All Activity

I noticed this behavour today also. I am confused as to why when you select a DIR TO the TMPY FPLN comes up on the 2nd MCDU. I think when you have an additional DIR TO you need to clear the previous one from the box of the DIR page, in the case of your video delet SVL I had the same issue where the 2nd DIR cleared my entire flight plan, BUT, I was able to get it back with out with some missing parts by clearing the previous DIR fix from the LSKL1 box on the DIR page and inserting the new DIR waypoint.

No, the simulator still crashes.

Hallo. Ich habe mir letztens den Airport von PIXELSIM - Bari LIBD gekauft und installiert, jedoch wird er mir im Sim nicht angezeigt. Weiß jemand an was das liegen könnte? Alles andere ist ok. Vielen Dank fürs Helfen

when will a350 see more liveries for xbox users? this is the 3rd or 4th time asking and no response

Hi @IniSteve, thanks for responding. I'd disabled autosave and the route is above with only the addition of ITREN as the transition.

I think I figured out what the problem was. One of my four RAM sticks isn't working (it's just corrupting the data it contains). I've removed it now and will try the flight again. I'll let you know the results.

Same issue on my side. Interesting though that this has become an issue just recently although I cannot remember a specific version when it started.

The registration could be: F-OSAM

The A350’s livery is expected to look like this.

When using engine reverse selectively the engine display behaves weirdly. I've found this in v1.0.7. When reverse is selected on Engine 1, all engines show as in reverse on the engine display. When reverse is selected on engines 2, 3 or 4, no reverse indication is shown on the engine display.

No, I do not have automatic saving enabled. The next day I tried to do a flight between VTBS and LFPG, and a second bug appeared after about 10 hours of flight: everything froze, it was impossible to disconnect the autopilot, etc. I only had engine sound and ATC still working. The aircraft was no longer following the flight plan. For your information, I had not activated FSLTL. I was forced to use (Alt + Del) to quit the game. The following day I repeated the same flight and this time it worked. I was wondering whether the problem really came from the A350 or from MSFS 2024.

And I also find that this problem will happen in iniA350 ,when you click CPNY F-PLAN REQUEST it will change to REQUEST PENDING and 20 seconds return to CPNY F-PLAN REQUEST and no message come from FMS but OIS can import simbrief flight plan perfectly just like the efb in a340 But the pmdg fenix ifly maddog even default 787 didn’t have this problem, and I find that before SU4 the A340/A350 works perfectly , this problem seems may probably appear after SU4

I tried running with an empty community folder to rule out any addon conflict and follow the steps above, but still can’t import my flight plan

Reporting a WASM crash on the iniBuilds A340 when inputting the arrival into the FMS. Steps to reproduce -Load plane at gate, power on, turn on APU -Load flight plan in tablet then via FMS -Enter Departure and Arrival procedure While putting in the arrival procedure, select the runway, approach, arrival and arrival transition. WASM crash occurred when I clicked on "NO VIAS" in the ILS approach for runway 27C at KORD. Aircraft: A340 EIS 1 Passenger Simulator: FS2024 Version: 1.0.7 Inimanager Navdata Method: Navigraph Specs: AMD Ryzen 7 7800X3D, 64 GB Ram, RTX 4070 Ti SUPER 16GB The Autosave file was not available in the folder indicated in the post about making WASM reports. I am enclosing all other screenshots and the flight plan. Not a good way to start off my first flight in the A340, but I hope this information helps. Thanks, Jose KJFKKORD_PDF_1768609824.pdf

I have yes. I haven't done many flights as still waiting/hoping for lots of bugs to be fixed, but I saw it on both flights I did yesterday. It was quite a short turnaround and not the longest of flights so it is possible there was some residual heat on the second flight which was into a long runway and shouldn't have heated the brakes that much. I will do another flight tomorrow and make sure I fly to a long runway and select a BTV exit right at the end and see what happens.

Hey @IniSteve Just wanted to check in and see if you had any suggestions. If there is something I can do configuration wise to mitigate I am happy to try.

Tried twice to fly using this flight plan, both times same thing happened screens all went red with WASM error. Aircraft: A340-300 Simulator: FS2024 Navdata Method: NAVIGRAPH OFP: EDDFKBOS Flightplan attached WASM Error: [inibuilds-A340.wasm] Error: Unable to open directory [inibuilds-A340.wasm] \work\autosaves\ [inibuilds-A340.wasm] WASM: Error during DisplayManager_gauge_draw execution. Error code : 0xc0000005 WASM: Module vfs://inibuilds-aircraft-a340/SimObjects/Airplanes/inibuilds-a340/attachments/inibuilds/Function_A343_Interior/panel/inibuilds-A340.wasm is now dirty Specs: i5-8400, Intel Arc B570, 32 GB DDR4 Autosave File: No Autosave folder available, was still sitting on the ground when error occurred and was my first flight in it. EDDFKBOS_PDF_1768593086.pdf

Same here. For my next flight, I'll use the MCDU through Spad.next, without SimApp Pro, to see if the problem disappears. Latest SimApp Pro update and latest MCDU firmware (1.04)

This is the second time this has occurred. The first time I was on approach and paused the sim. When I came back and un-paused the plane still said on the OIS that I needed to un-pause my game even though the plane was flying. I was not able to control anything in the cockpit by clicking it or using my external controls. The plane didn't follow the nav route either it just flew at its last heading at the same altitude. The second time it happened I was tabbed off MSFS and when I came back I noticed my plane was in nav mode but not flying the flight plan and when I tried to intervene I wasn't able to move any controls besides a few like the FD and LS buttons (they pressed but didn't do anything) and it just kept flying off course. I'm able to interact with the OIS but nothing responds. I cant turn the time compression off or change its speed etc. FS 2024 A350-900 version 1.2.0 System Specs: i5-12600k, 32 GB DDR4 (3200), RTX 4070 Super

Same thing happened to me yesterday

1.07 and same issue it freezes constantly, reconnecting helps but yeah it's a bit immersion breaking. I am on the latest update.

Issue is reported. Thanks.

Hi. We'll investigate to see if this is possible without a massive hit to perf.

Hi there，will this be fix in upcoming upadte，cuz it wasnt considered in the latest update.😁

Ironically, I've literally just discovered a clash between a saitek panel input and the flood lighting control. Thank you for your reply though. If in doubt, its a third party plugin 😅