All Activity

WASM Crash after ZDN/DANIB waypoint in Iran Same exact type of WASM crash as I get with A350's, always happens after a waypoint during autopilot following the waypoints. Aircraft goes out of the magenta line and turns away and does it's on thing. In this example, all buttons worked apart from AP1&AP2, with thrusts not registering climb either, TOGA LK is replaced by this. Altitude wasn't changing either and I went up 3,000 feet randomly, with the heading also changed from --- to custom, which was the aircrafts doing and not myself's as I came back to this. I have reported this problem multiple times previously in both the WASM Issues - iniBuilds Discord and via here, each of the times the problem is directly related with one main cause, always occuring after a waypoint. WASM has been cleared prior to this flight as recommended to. This is my second flight with the A340 after purchasing on iniManager for £54 in which it isn't the best first impression to spend a 5h30m flight to nowhere, likewise with the other high purchase of the A350 for the same relatede issue. Very impressed with both A340 & A350 + variants of aircrafts, fantastic job by the iniBuilds team, but these WASM issues make the aircraft unuseable at this stage and ruins the experience, so anyone can understand after hours of flying to nowhere, where the disappointment comes from. Again, the aircrafts are very well made and a great job by the team. Aircraft: A340 EIS 2 Freighter Simulator: FS2024 Version: iniManager Navdata Method: SIM DEFAULT OFP: Attached WASM Error: The error you copied in Step 4 above Specs: Ryzen 9 9900x, 9070 XT, 64GB Corsair Vengeance Autosave File: Attached Videos of the problem: https://drive.google.com/file/d/1CM5AxqFD8CCRZcFTlrSgjgxFC0MKMXWt/view?usp=sharing https://drive.google.com/file/d/1c2GsIWhTCWO57DnpMaKPk5ToEyYkVPmV/view?usp=sharing 1768656953.bin 1768660570.bin 1768664246.bin 1768667936.bin 1768671639.bin FLIGHTPLAN_pdf.pdf

Hello, after I downloaded the flight plan via SimBrief and completed the loading in the EFB, the MCDU shows an incorrect trip fuel on Init Page 2. Correction is not possible. I have installed the latest update. Is there a solution for this? Thank you in advance. Wolfgang

Entering Waypoint in my flight plan, and using LSK1L results in ENTRY OUT OF RANGE warning. Also INIT-A page does not update CRZ FL/TEMP when a higher altitude is selected in the FCU (Is this propper A340 logic)

I also have this as a major sound bug. In flight it keeps increasing until it's at a deafening level. This is the iniManager version, 1.07, MSFS2024 Daniel

No option to activate a secondary flight plan.

Would be a great idea, I am not sure if I am doing any thing wrong, but I have no Activate SEC LSK on the SEC index Page.

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)