All Activity

to this extent in v1.0.9? find it hard to believe but I am open to stand corrected

I only had wasm crashes when starting the sim in admin mode.

I vote to give @Der Michel a free copy of the A380 upon release, for all his efforts in finding and squashing bugs and innaccuracies of the current Ini Airbus Fleet.

Aircraft: A350-1000 Simulator: FS24 Navdata Method: NAVIGRAPH OFP: Not to a specific route -- However this happened twice for me during a long flight (12+ hours). WASM Error: WASM: Error during MFD_gauge_draw execution. Error code : 0xc000001d Specs: Ryzen 7-8700F 8-core, NVIDIA GeForce RTX 4060 Ti 16GB, 64GB DDR5 Autosave File: Please include the latest ".bin" autosave file prior to your crash. Video of the crash won't upload due to file size. Link: https://streamable.com/zb4jae What happened was that I tried to enter the destination data for my arrival airport into the MCDU/FMC. I went to the PERF page and tried clicking on approach, but then it gave me a WASM crash. This is the second time this has happened. To reproduce: 1. Start a flight with the inibuilds A350 2. Fly a very long distance (ex. Middle East to the US) 3. Before descent, enter destination data in the MCDU/FMC 4. Go to the approach phase of the PERF page 5. WASM crash happens once attempts to open approach phase 1770058358.bin

Aircraft: A350-1000 Simulator: FS24 Navdata Method: NAVIGRAPH OFP: Not to a specific route -- However this happened twice for me during a long flight (12+ hours). WASM Error: WASM: Error during MFD_gauge_draw execution. Error code : 0xc000001d Specs: Ryzen 7-8700F 8-core, NVIDIA GeForce RTX 4060 Ti 16GB, 64GB DDR5 Autosave File: Please include the latest ".bin" autosave file prior to your crash. Video of the crash won't upload due to file size. Link: https://streamable.com/zb4jae What happened was that I tried to enter the destination data for my arrival airport into the MCDU/FMC. I went to the PERF page and tried clicking on approach, but then it gave me a WASM crash. This is the second time this has happened. To reproduce: 1. Start a flight with the inibuilds A350 2. Fly a very long distance (ex. Middle East to the US) 3. Before descent, enter destination data in the MCDU/FMC 4. Go to the approach phase of the PERF page 5. WASM crash happens once attempts to open approach phase 1770058358.bin

now i tryd ini A350 same issiue, i cant fly any ini plane

Hi, ironically, they all come from the same aircraft recording. Despite that, we're going to take another look as its evident they are not meeting the overall expectation.

Hi Thanks for your report. We'll investigate but please note that we have limited control over what AI Traffic or addons do, as we cannot specify particular pathing for them. The SDK tools only allow us to define basic information such as the location of runways, their start and end points, and the placement of taxiways. There is no option for more detailed control over AI or User Aircraft movements. Thanks.

Hi, Thanks for your patience. Your report is logged.

Glad we were able to assist, thank you!

Hi Thanks for your patience. Certain gates are used for static aircraft, and they are disabled in the AFCAD to prevent AI traffic from spawning on top of these statics. You can disable the statics 3D model, however there is no secondary AFCAD for these airports as such the gates remain "unavailable". There are only few such gates across the sea of other available gates at this airport. Thanks

Hello. I just loaded into the sim with both versions of the SAS Liveries on IniManager and did not see this issue occurring as demonstrated below. It is possible that the livery may have corrupted and recommend reinstalling the liveries as well as the aircraft itself just incase something did happen to corrupt.

That is correct Sir I did follow this accordingly and now it stays error failed to download

Hi, Are you able to produce media of the issue, I am on PC and updated to 1.2.1 and not seeing this issue occurring, have you attempted to clear WASM for the 340 or reinstall the aircraft? I loaded into the A350-900/ULR/1000 and did not see this issue occurring on my end. If you can please submit footage with the current version please and thank you.

Yes they have gotten really really bad. I already submited a ticket to this topic:

Hi Thanks for your patience. We’ve noted the reported issues and will investigate further.

Hi all, Thank you for your patience. We’ve taken note of the performance feedback shared here and the team will be investigating potential areas for improvement. Temporary tips to try if not already, while the team continues investigating: Lower Texture Resolution and TLOD/OLOD Verify that no duplicate scenery entries exist in My Library (can occasionally happen after updates). Disable various options from the Scenery Configuration Panel like Interior Clutter, 3D People, GSE or 3D Vegetation to help Thanks!

Hi, this is correct behaviour and has been verified from A340 pilots. At very low gross weights, the center gear will not make contact with the ground. Once you add fuel and payload it will settle onto the gear as expected.

Dear staff, Thank you for the problem fix - a clean re-install of just the aircraft without the ini-manager did the trick! You may close the thread. Best regards

Hey Thanks the issue is logged and the team will look into it. Yes helipads are known to cause such random conflicts with jetways. We saw something similar with our own KJFK scenery as well. From our testing it seems like the following gates are affected: Gate C50, 51, 51L, 52, 53, 53L Thanks!

Hey, You need to disable the Microsoft/Asobo OMDB scenery via My Library. You can see below guide on how to do so. https://flightsimulator.zendesk.com/hc/en-us/articles/17373373933340-How-to-enable-disable-and-download-content-in-the-simulator If that is not working, you can try to manually disable it via your Content.xml. In particular you want both these entries to read as either SystemDisabled or UserDisabled. Content.XML - Common Paths In there you will see a folder that is named after your XBOX user id. The content.xml file should be in it. Mine for example is richboy2307#6098. Save a copy for backup, and then edit with notepad as suggested above. Thanks!

Hi, for the EFB you can control the lighting in the Sound/Cabin Options section(See Image Below). For the FA Panels in the 350 I just have one of the custom camera key binds set to transition the camera from the flight deck to the FA Panel outside the L1 Door.

SAS OY-KBA from Livery Manager.

There shouldn't be. I use the linker and cannot reproduce this issue. Are you 100% sure you have defined the exact path in the manager client? There is a very small change the manager didn't save your predefined path so you may have to redefine it in the settings menu.

Hi This was by design to avoid duplication of POIs (Burj Khalifa Building) at the site. We were unable to exclude the default POI at the time (Feb 2025), however we take note of your suggestion and will re-asses if its possible now. Thanks!