All Activity

Issues regarding the panel states are known

Hi, just to verify, when being fully configured to land and then subsequently landing does not automatically deploy spoilers unless you press the button which is actually designed to disarm them? Can you upload a video either on google drive or youtube so I can see just to make sure I got it right, thank you

Hi Seems like V1.0.3 is unusable for me. The ON APU or READY FOR TAKEOFF panel states don't work as they seem to stall and get stuck around "APU initialisation" or "waiting for RPM target", before it times out. Am I doing anything wrong? Was looking forward to the fixes in 1.0.3. and rather disappointed I cannot even start from an easy state...

Good afternoon I don't know if this question has been asked before, and if so, I apologize for asking it again. Seeing what inibuilds has recreated in the past, with their work on the A340 and A350, which continue to be updated, adding new features and making corrections, ultimately evolving the product, I would like to know if there are plans, or at least if it's being considered, to develop an A330. The A330 shares systems with the A340, even a very similar structure; they share the fuselage and wings, with modifications, for example, to the landing gear or the engine pods. It seems strange that, having developed an A340, they couldn't develop an A330 based on it, knowing that they would share common elements, meaning at least part of it would already be done. I know that there is a recreation of the A330 in the simulator, which, for a package aircraft, is quite complete. In fact, I was surprised by how much interactivity it had compared to other package aircraft that ASOBO and Microsoft developed. I know that Ini developed this aircraft for them, and that they cannot upgrade it themselves, but I understand that they would have total freedom to develop one that would do justice to the A330. A version of the -200 and -300 model with the P2F variant, similar to the work done on the A300, would surely provide many flight hours for the sim flight community. Is it possible, then, that an A330 could be developed? Have the developers at IniBuilds considered this possibility? That's all, greetings

Aircraft: A300-600 PW Simulator: FS2024 Version: Inimanager latest a300 Navdata Method: NAVIGRAPH OFP: attached WASM Error: WASM: Error during Systems_gauge_update execution. Error code : 0xc0000005 WASM: Module vfs://inibuilds-aircraft-a300/SimObjects/Airplanes/A300-600/attachments/inibuilds/Function_Interior_Passenger/panel/inibuilds-A300.wasm is now dirty Specs: AMD RYZEN 7 7800X3D, ASUS DUAL RADEON RX 9060 XT, Crucial 32GB DDR5-6000 KIT Autosave File: Please include the latest ".bin" autosave file prior to your crash. Step 9. Where possible, include on your report I was editing my approach runway. Cant share autosave as directory explained is not showing any autosave: BR, Robin EDDFEFOU_PDF_1776875737.12974a46.pdf

As there is no update here, and probably never will be, I advise anyone with this problem to download muxp and create a correctly profiled version of the runway based on published elevation data.

Xbox Series X

iniBuilds A340 Airliner V1.0.11 Update 🚀 The A340 Airliner v1.0.11 update brings a strong focus on overall stability and performance within the MSFS WASM environment, alongside a range of targeted fixes across core aircraft systems. Following extensive internal work and testing, this update introduces under-the-hood improvements to memory handling, data efficiency, and system robustness, resulting in noticeably improved consistency, particularly during high-load and demanding scenarios. In addition to these foundational enhancements, this update addresses several system-level issues affecting day-to-day operations, including corrections to flight deck indications, trim and hydraulic logic, navigation behaviour, and MCDU interactions. Together, these changes help deliver a more stable, predictable, and refined experience across all phases of flight, with a reduced likelihood of WASM-related instability. We’re excited to say that after considerable work and a strong focus on improving overall WASM stability, the team have implemented a range of under-the-hood optimisations throughout the latest testing phase. Many of our testers have already reported noticeable improvements in performance and consistency, particularly in more demanding scenarios. These changes target memory handling, data efficiency, and system robustness within the MSFS WASM environment, helping deliver a much more stable experience overall. Here's what we've done: Optimised WASM performance and memory handling by reducing unnecessary data copying in key systems, lowering transient memory usage and improving overall efficiency within the MSFS WASM environment. Refined data access patterns to reduce unnecessary temporary copies, helping lower stack pressure and improve runtime consistency, particularly during high-load scenarios Added additional safety checks across critical memory pathways to guard against invalid states and edge cases As mentioned above, these changes significantly improve overall stability and reduce the likelihood of WASM-related crashes, so be sure to download the latest updates, especially ahead of a busy Cross The Pond, coming this weekend! This update can be downloaded via the iniManager. V1.0.11SYSTEMS ⚙️ FIXED Deviation indication when no course tuned in VOR FIXED Trim can be moved without hydraulic pressure FIXED Issues with clearing scratchpad FIXED Fix page formatting issues FIXED Manually tuned navaids not resetting after landing FIXED THS should be +4 deviation on cold and dark load iniBuilds Team ❤️

FYI I have a thread over here on this same issue. Maybe if we keep pestering we will get a list of LVars!

Looks like GPS jamming, you can disable this feature in OIS menu if you like

ok please let me know if theres is any fixes to this

Hi all, i don't understand this problem ! Help please !

Hi, Sorry as sometimes life keeps us busy. We are working on a build now with refinements to our Auto Pilot and Flight Modeling. I don't have an estimated time for a delivery as of yet, but work is being done. Thank you for patience 🙂

Thanks team is working on pressurisation system/controller related issues.

Appreciate the feedback. so I didn’t realise on the GARMIN GPS you had to change from GOS to L LOC. I’ve done that and with update 1.0.2 all is working. Really great aircraft by the way. Will continue to monitor things as more flights take off 🙂

There is clearly some logical linkage in the code between the autopilot state and the autothrottle logic. My understanding is that the two are not mutually dependent in the real aircraft, so even if you CAN get the correct EPR value with the AP on, that shouldn't be a necessary step.

Known issue being worked on, thank you.

Yeah it's an ongoing issue with the map provider, no real ETA but I can ask around and see what's new if anything regarding information

Hi, do you mean visually viewable passengers in the cabin? I don't believe so but you can load PAX via the OIS/EFB for W&B purposes

I found a reference photo of an L-1011 with an LTN-92. That would be amazing if we could use this unit, since it uses a navigation database similar to a modern FMS. The LTN-72 is cool, but let’s be honest, entering those coordinates and being limited to only nine is a pain in the neck. Besides, as far as I know, coordinate systems like the CIVA and LTN-72 were mainly used for oceanic crossings. I also think modeling an LTN-92 would attract more people to buy this plane, since it’s a step closer to how a modern FMS works. No need to enter coordinates and instead use navigation fix names. Something for iniBuilds to think about. 😉

Hey, Yes Brake Temperature is WIP for a future update. As for autobrake, you can confirm by looking at the pedals themselves, they should depress when autobrakes are active. The more objective way to check is via the Debug Aircraft Wheels window. For that, you'll need to enable Developer Mode (Settings > Advanced Options), then navigate via the toolbar at top to Debug > Aircraft > Wheels. (Click to enlarge images) Could you please record a similar video with the Debug Aircraft Wheels Window open? Mainly concerned with the BRAKE INPUT and BRAKE EFFECT fields at the very top. For MIN and MED braking they won't show a constant input, but for MAX or RTO they will. And also mention the Airport, Landing Weight and Autobrake Setting used so we can try to reproduce it. While they have worked every time for me on my previous flights, perhaps there are some specific conditions where its failing. 2026-04-22 15-53-37.mp4 Note 2: Just a quick demonstrative video I recorded by spawning on runway and then conducting a high-speed RTO, please do only try this at home 😅 Additionally, per the documentation - take note that on the L1011 the autobrakes are not a substitute for manual braking. You should not use them to full-stop. The MIN and MED settings are targeting 4 and 6 ft/s² deceleration rate, whereas MAX (and RTO) is giving full application. Thanks!

Hi, so I think what I've gathered the issue into (so I can forward to team); The A350 on Xbox Navigraph Update gets stuck and then will show the current cycle in the OIS and then still is on what, the first airac you used it seems? Feel free to correct me and attach anything need be in a google drive link or youtube link so that both I can better understand the issue and present it to the team. Thanks.

I've done some research and apparently you can load default passengers into the a350 using EFB, but it doest seem to be working. Is there something I am missing or a setting i need to turn on for this to work? Or does this not work entirely?

Don't think that the missing STARs is Ini Builds fault. I just did a test, loaded the sim with the default LIMC scenery and all the arrivals are there, then I loaded the sim with the Aerosoft LIMC and all the arrivals and approaches are now gone. So for this issue I'd go and bother Aerosoft 😛

Hey, The fuel jettison feature is currently in development and planned for a future update. It isn’t included in v1.0.3 yet, as noted on page 80 of the manual.