Skip to content
View in the app

A better way to browse. Learn more.

iniBuilds Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

All Activity

This stream auto-updates

  1. Past hour
  2. EfexBACK joined the community
  3. Today
  4. Hello Jamir, thanks alot for your quick answer and your advice. As soon as I find the time, I will do what you recommended and will let you know about the result. Have a great day :-) C.
  5. florian478654 joined the community
  6. Canko55 joined the community
  7. mik_a joined the community
  8. Artorias joined the community
  9. could seven joined the community
  10. matthew.nissenza joined the community
  11. rory1129 joined the community
  12. Glad I could help, A300 is a personal favorite of mine so always glad to have another enjoyer in the skies. :D
  13. Hi, I went back and uninstalled it and re-installed it from the default marketplace. It worked! My fuel is working how it’s supposed to and I was able to do several flights already with the 300. It’s a great aircraft. Thanks for the suggestion🙏
  14. MadDog5 joined the community
  15. Hi, if you're having a crash every time you load the aircraft then it is most likely an issue with the stability of your computer. Have you overclocked your computer at all? Are you running any other addons alongside the simulator? Other users have reported that reducing the speed of their RAM (either turning off EXPO/XMP or reducing the timings of their memory) has had a large effect on the stability of their sim. In the future, if you have a crash and you please follow the steps outlined here (especially with regards to the logging variables and they help immensely in tracking down the causes of crashes) The A350 is a complex aircraft and it is asking a lot of the simulator, unfortunately it is simply the nature of the plane that it is sensitive particularly to the stability of the memory on your PC - that said, it is one of the most flown aircraft in the simulator and so we know that it can be stable but there are a lot of variables that are beyond our control.
  16. Hi, the update is in testing but we don't have any ETA to share at this time :)
  17. I have loaded the A350-900 default cabin config at least a dozen times in the last week and not had this phenomenon. Can you confirm you don't have any light enhancement packages installed and that the aircraft is otherwise behaving as expected?
  18. Escarcel joined the community
  19. Yesterday
  20. Hi Chris, I understand your frustrations with the aircraft and rest assured that we don't have broken iterations of the aircraft just left on the Marketplace. It sounds like something may have actually corrupted during the installation of the aircraft as over the past few months we've done a great deal of WASM bashing with 350 and 340 to identify, fix, and then attempt to replicate until WASM crashes are non-reproduceable. It sounds like something however may have corrupted during the initialization of the aircraft which could be causing these issues to appear more than is currently experienced across PC and Xbox. If you could try uninstalling the aircraft, fully restarting the Console, then reinstalling the aircraft to see if this helps. Thank you.
  21. Hi, just to verify you don't have an additional light packages that affect aircraft or airport lighting? Just the A350 and the sceneries are the only 3rd party content in use at the time?
  22. Hello, I just created my account here ..so Hello to everybody from (currently fairly hot) Vienna, Austria :-) . seems summer finally kicked in ;-) First of all, I want to say thank you to iniBuilds for their so far great planes they offer and for their high amount of engineering time they invest in their products for us to have pleasure with the FlightSim-World. Well, I am using the Airbusses A320, A330, A350 so far, I have to say, it took a while until every of the plane worked properly, but now they are doing fine without really critical problems. So I was quite happy when I saw the A340 is under discount so I decided to buy it finally to have a 4-engine-Airbus, too. Unfortunately, I am unable to use that plane....WASM crashes mostly, or CTD...in one word, unuseable. You can imagine, my disappointment was great. Well, I had this with the A350 for a while, too...but now it is working there. So I would like to suggest something: If you know, you have a plane on market place...and I am sure, you know, that the plane is not really working....why let you it on the market place and do not remove it or at least give the information, that the plane is currently hardly to use. I assure you, as soon as the plane would be announced as useable or bugfree, I would buy it then. But I hate to give good money for - for nothing. This feels a bit as a betrayal on your customers. You offer somthiing to a customer what he wont be able to use properly, Well, I hope you understand my point of view. I am sure not mad or pissed off, I am just disappointed that a good and successful company what makes good stuff for us Simmers, is acting like that. You could do better, dont you think? Have a good time and I am looking forward to have my first flight with the A340! :-)
  23. Thank you for these, I'll pass this along to the team.
  24. I did this the other day and can confirm that it works.
  25. Runway start: Cold start. Never going above 430 RPM
  26. Would love some different a321 NEO variants to fly like the XLR and Standard NEO
  27. When can we expect to see the 1.0.8 update? It's been pending for quite a while now and some needed fixes have already been promised for it in the ini Discord and here on the forums.
  28. An interesting finding: The issue only occurs with the A350-900 using the default cabin configuration. I have tested the following variants and they do NOT exhibit the problem: - A350-900 (No Cabin) - A350-900ULR (Default Cabin) - A350-900ULR (No Cabin) - A350-1000 (Default Cabin) - A350-1000 (No Cabin) So far, the problem appears to be exclusive to the A350-900 with the default cabin model installed. This makes me wonder if the issue could be related to the specific model variant or cabin package rather than the aircraft's lighting system itself. This may help narrow down the root cause, as the lighting issue seems to be tied to a specific aircraft variant rather than affecting the entire A350 product line.
  29. Hi everyone, I am experiencing a strange lighting issue with the iniBuilds A350 (v1.2.6) in MSFS 2024 and would like to know if anyone else has encountered the same problem. Issue: - Landing lights remain illuminated externally even when the aircraft is in a complete Cold & Dark state. - Strobe lights also appear to be affected and do not always follow the switch position. - The problem occurs on every flight. What I have tested: - Aircraft loaded directly in Cold & Dark. - Batteries OFF. - External Power OFF. - APU OFF. - Landing light switches OFF. - Tested with both default iniBuilds liveries and third-party liveries. - Reinstalled the aircraft through iniManager. - The issue persists. What makes this particularly strange is that the landing lights remain visible from the outside even when the aircraft has no electrical power at all. I am running: - MSFS 2024 - iniBuilds A350 v1.2.6 - GSX installed (issue occurs even without using GSX services) Has anyone else seen this behavior? If so, were you able to find a workaround or fix? Thanks in advance. Screenshots attached showing the aircraft in a completely unpowered Cold & Dark state while the external landing lights remain illuminated.
  30. For the route and weights below, according to Simbrief I should use about 4000kg more fuel with cost index 400 (compared to the CI 45 I did the original flight plan with). So trip fuel should be about 4-5ts more than on the screenshot. However, neither the fuel predictions nor the actual usage (!) increased during the flight with cost index 400. In other words: I was able to fly with cost index 400 and use about the same amount of fuel compared to cost index 45. EBBR/25L ROUSY2P ROUSY DCT GTQ DCT POGOL DCT LASAT DCT MOROK DCT GILIR DCT GEVEA DCT KOGAS DCT MEDAM DCT VEVAR DCT BARSO DCT KOLON DCT RARQU DCT NESUL DCT ETOIL DCT CIRTA UA605 DJA UB730 DIR UG862 BUN DCT ASEKA DCT MUBAK DCT EGREK EGREK1B HRYR/10 I can reproduce this on every flight. The highest (!) fuel usage actually comes with cost index 0. So there's something fundamentally wrong.
  31. Hi. Testing this right now and the auto switching is working well, but for clarity, BATC doesn't support time compression, which is why you'll see errors after a while.
  32. You can upload the video to YT unlisted and link here as well as Google Drive and link here.
  33. I would upload videos here but it only allows 7.81MB. I have the same problem. RPM aren't going above 431 on cold start and if you start at a runway engine constantly going down and up down and up. I have few aircraft bought from different developers and this is the first time I can't use one. I have dissconnected all peripherals and restarted the game several times and the problem is the same. With XBOX controller, Keyboard and mouse, with MOZA, with TurtleBeach. All the same. F406 by iniBuilds is just not usable at all for me. I tried passanger and cargo variants and it's all the same. UPD: If you start from runway and your throttle at 100% you have RPM and TORQUE oscillations going up and down. Only at throttle lever 93% and below it is table and not losing/gaining power. If you put it 94% or above it start going down and up and down and up.
  34. Hi Pilota459 Thanks for jumping in. Yes, I've already gone through all the usual steps, plus several others I found mentioned across this forum: Full reinstall of the A350 (multiple times, both via Content Manager and clean manual install) Cleared the WASM cache folders (wasm and wasmFolder under both LocalCache and the rolling cache location for MSFS 2024) Started MSFS with a completely empty Community folder only the A350 present, no other add-ons loaded. Crash still happens. Rebuilt the rolling cache and disabled it entirely as a separate test Verified file integrity through the Content Manager Reinstalled Navigraph data and also tested with no Navigraph data at all Tested different liveries, including the default one, to rule out a livery-specific issue Disabled all developer-mode options and any third-party tools that hook into SimConnect/WASM (FSUIPC, GSX) Tried different airports and short flights (including very simple cold & dark starts at default airports). crash still occurs within ~10 minutes Updated GPU drivers and verified MSFS 2024 itself is fully up to date Reviewed MSFS.log around the time of the crash, the only relevant entries point to the inibuilds-A350.wasm module failing in the MFD gauge Kind Regards,
  35. Yes, I have it through the default sim marketplace. I will try to uninstall and re-install the aircraft and see if that works. Thanks🙏
  36. Hi, That sounds really weird. You've said you attempted a couple different steps to trouble step the aircraft. Do you have the aircraft on the IniManager or through the Marketplace in Sim? Have you tried uninstalling and reinstalling as this sounds like a corruption issue which usually occurs during the install process. Let me know, thanks.
  37. Last week
  38. What have you tried so far? Reinstall, cleared WASM folders, startign with empty Community folder etc.?
  39. Hi iniBuilds team, I'm writing to report a critical, ongoing issue with the iniBuilds A350 in MSFS 2024 that has made the aircraft completely unusable for me for over four months now. The problem: All MFDs crash with a "WASM module crashed" error, every single flight. It happens consistently within the first 10 minutes of the session — sometimes during taxi, sometimes shortly after takeoff — and once it occurs, the entire cockpit is unusable (see attached screenshots). Error details from the screen: Package: inibuilds-aircraft-a350 Module: /SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm Gauge: MFD Topics: The latest update made things worse. Before the most recent patch the crashes were already frequent, but now they are happening even faster and more reliably. This is isolated to the A350. I fly other complex add-ons (including the Fenix A320, PMDG 777) on the same system, on the same flights, with the same scenery and add-on environment and none of them have this issue. It has been more than 4 months. I purchased this aircraft and have not been able to complete a single normal flight in it for that entire period. That's extremely frustrating, especially given how prominently this aircraft is marketed. Could you please confirm whether this MFD WASM crash is a known issue currently being tracked? Is there any workaround, beta build, or rollback I can try in the meantime? If a fix is in progress, do you have any indication of a timeframe? I really want to enjoy this aircraft — that's why I bought it — but at the moment it is simply not flyable. I would appreciate any response. Happy to provide MSFS version, system specs, full add-on list, or log files if that helps your team reproduce or diagnose the crash.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.