liketofly1

@ Eddie, Hi, and thanks for your support.... Here are all the autosaves stored on my machine and the flightplans. 1 flight EGLL to FACT and 1 EGLL to VTSB.. However, it should be pretty easy to recreate just start a flight before midnight lets say 22:00 hrs, and watch the Block/Flighttime. Then, sometime in the early morning hours of the next day, take note of the Flighttime (start time of Block/Flight time) and reload the sim. Once youre back in flight, the Block/Flight time will start from when you loaded this flight - try to change it to the time you really started the flight (previous day before midnight). It will not calculate it. It will however calculate the correct Block and Flight time if you do this on the same day ... let say you start at 08:00 hrs in the morning and load a reload from 16:00 hrs. Then you can enter your start times and the A350 will show the correct Flight/Block time again... I can reproduce this every time.... kind regards Richi... VTSBAPP.bin 1755809319.bin 1755809829.bin 1755810350.bin 1755810866.bin 1755811306.bin 1755811744.bin SAGOD.bin EGLLVTBS01.fpl EGLLVTBS_M24_24Aug25.pln EGLLFACT01.fpl EGLLFACT_M24_24Aug25.pln

I was on a truly uneventful flight between EGLL and FACT in the SimUpdate 3. Flawless performance and I'm super happy..... until this happened..... A passenger opened the door just as we pulled into the Gate, obviously beeing in a hurry to somewhere..... But Jokes asside, Nothing was active exept GSX remote controlled by the A350..... Any Ideas how this happened as it happened even before I turned off the Beacon Ligths...?

The Block and Flighttime do not recover after a reload of a autosave, and if you manually want to enter the offblock and T/O time and this happened to be on the previous day (lets say you took off at 22:00:00 hrs on the 16th and you reload sometime on the 17th, the Block and Flighttime stay at 00:00:00. So something is wrong with that logic - if I go off block / take off on the same day - and enter the correct off block / take off time it will calculate the correct times - only if the off block and takeoff happened on the previous day it does not calculate....

The Flight Time and Block Time are not saved on Auto-saves. If you want to manually enter them, and the Start of Block or Flight Time is the previous day (lets say 23:05:00) the entry goes to 00:00:00 and does not calculate from the previous day.

I'm pretty happy with the latest version of the A350 - however - after flying from LOWW to FACT, using 4x time compression - the plane froze at some point. I thought no big problem, lets use one of the auto-saves that I always have activated..... I basically love the feature but its missing quite some important data points in its saves.... 1.) Not all flight plans (secondary 1,2,3) don't get saved... 2.) Other settings like flight time and block time start from scratch, and Local Time is empty 3.) Would be nice if it could save the time of day.... 4.) Simbrief - Flightplan and Loadsheet - FMS shows correct GW and Fuel, but load sheet page in OIS is empty 5.) Fix Info pages are blank again although it retained the Pilot Stored WP's 6.) Alternate fuel is also wiped... So in reality its not that useful - I wish those auto saves would put you right back in spot and time where it was saved with all the data back in place in the FMS and OIS.... and all the settings of the switches.... I hope IniBuilds is planning on improving the great auto save feature, maybe with a checkbox or so if you want all the data stored like for a total recovery or if you just want the necessary data in order to bring you back in place and situation, which is a nice feature if you want to train certain situations....

Hi, I'm having trouble to download (update) EGLL from the in Sim Marketplace. 1st it wanted to update, which failed... then I uninstalled it, but now I can't download it anymore..... It only downloads 215B from what should be 1,98GB and says that's 100% and then the download fails... any help would be appreciated. kind regards liketofly

@IniSteve Any update on this as this FRED is now already a few months old and I'm sure there's hundreds if not thousands waiting for the MCDU compatibility with iniBuilds Airbus fleet...

Yup, youre not the only ones - count me in 😉

If I interpret that picture correctly, then you ran out of fuel and your engines turned off....

Still an issue in 1.0.9f. Come on Inibuilds - that should be an easy fix......

Hi, I have the same problem.... just floating around....

Just flying over the Great Lakes at FL350 and look at that nice ground speed.....

Dear Inibuilds team, Thanks for the 1.0.4 update - its a huge stability improvement. I'm currently on my second fligh, and up to now did not encounter a crash! However, while attending the toilet, I found my FO sitting in the galley, and was wondering why?

But do both of them do the sound or just one?

But do they work on both throttles?

Hi, I found that the "Audible Thrust Detent" only works on the Left (No.: 1 Eng.) and not on the Right (No.: 2 Eng.) If I move my throttles, the left one is clearly audible, the right one not at all.... Kind regards liketofly

Hi, Again WASM crash after Simbrief FP import from MSFS2024 EFB/Simbrief plugin/app. AMD 5900X, Nvidia RTX390, 64GM Sys.Mem., Windows 11 Pro, 24H2, Windows Feature Experience Pack 1000.26100.48.0. A350 v1.0.2, MSFS2024; SU1 installed and WASM was cleard just before the flight and ofcorse also before install of the A350. EGLLLEMD_M24_10Mar25.pln

Perfect 😁 Thanks!

Any hint when there might be an update, addressing the WASM/CTD crashes ?

Hi, did SU1 bring any stability updates/fixes for the A350 that where not in the beta?

Device name CHEWBACCA Processor AMD Ryzen 9 5900X 12-Core Processor 3.70 GHz Installed RAM 64,0 GB System type 64-bit operating system, x64-based processor Pen and touch No pen or touch input is available for this display Windows 11 Pro 24H2 26100.3194 NVIDIA RTX 3090; NVIDIA 572.6 Driver WASM error: WASM: Error during MFD_gauge_update execution. Error code : 0xc000001d WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty Error occured during step climb imput on MCDU

Sorry, this plane is absoluty bugged since the update. I could get a flight in on Thursday but now, after the update, I'm tying since the morning to get a flight, however the systems crash in sooo many diffentent ways its just not working. I already un- reinstalled the plane and cleared the WASM folder several times, It's the same every time. For now I'l not be using this plane as its just causing too much frustration. Last crash happend when I was working in the MCDU, trying to enter StepAlts when WASM crashed with these errors. Cursor just feezes and everything hangs. WASM: Varget of NAV HAS TACAN in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm failed with error 0xffffffff WASM: Error during MFD_gauge_update execution. Error code : 0xc000001d WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty Aircraft: A350-1000 BAW Livery Simulator: MSFS2024 SU1 Beta v1.3.24.0 Navdata Method: NAVIGRAPH Specs: ÁMD 5900X, RTX3090, 64GB kind regards Richard Oberwinkler EGLLFACT_PDF_1740840508.pdf