All Activity

Hi, Please select the A350 Airliner for MSFS2024 and provide your receipt. Thanks!

Thanks for your suggestion! I’ll add it to the list for consideration. As for the Commander, while we will certainly take it into consideration, we do have a process for determining what we’ll be working on in the future, which inevitably takes some time. Thanks for your understanding!

I purchased the iniBuilds A350 for MSFS 2020 through the Microsoft Flight Simulator Marketplace. The Order Transfer form does not offer an “A350 Airliner for MSFS-2020” option. Which product should I select?

Hi now that you have allmost all airbus airplanes it would be really nice to have the a330neo inibuilds could you try making it? thanks, and what happened with the turbo commander?

Hi, Are you able to provide a video or photo showing the aircraft behaving this way? I’m wondering if there may be a keybind or calibration issue causing this. Thanks!

You've been setting stabilizer trim right?

Hi, Whenever I try to make the Airbus A320Neo V2 in MSFS 2020 and 2024 make a direct to... ex. on SIDs and STARs, the aircraft can´t stay on the route. it turns too slow and veers off the route. what´s happening? This is weird, because to me the A321neo doesn´t seem to have this problem

Hi, Thanks for your suggestion! I’ll pass it along to management for further consideration. Thank you again!

Hi, Which products are you referring to? If you could provide a picture for reference, that would be great. Thanks!

Great news, enjoy!

I believe, at least in my experience, you want to have both set. Let me know if this works! Thanks!

Tested this on my end and I’m seeing the same issue as shown in your images. I’ve logged this with the Synaptic team for further investigation. Thanks again for your feedback!

Hey Kyle, maybe I am very wrong on this. But should the callout not actually be audible without DH but MDA entered? If I am wrong, please appologize the confusion. Best

Really? Could you show a screenshot of it working?

Works now, thank you very much for your help!

Hi Kyle, thank you again for logging my case internally. I would like to add one potentially useful reproduction detail after comparing my incident with other iniBuilds Airbus WASM/FMGS reports. In my case, the crash did not occur during the go-around itself. The sequence was: - go-around from the first ILS approach - aircraft stabilised at approximately 3,000 ft - active F-PLN contained MANUAL / F-PLN DISCONTINUITY / END OF F-PLN - Direct-To MJV - ARRIVAL / APPROACH was then being rebuilt in the MCDU - shortly afterwards, inibuilds-A320.wasm crashed and PFD/ND functionality was lost This seems potentially relevant because similar reports also involve ARRIVAL/ILS/STAR/transition/VIA selection or other active flight-plan modifications, sometimes even without a go-around. So the go-around itself may not be the root cause. A possible trigger area may instead be the FMGS active-flight-plan / procedure reconstruction when an existing or unusual flight-plan state is modified. A reproduction sequence that may be worth testing could therefore be: normal STAR + ILS approach → go-around → modified missed-approach / F-PLN state → MANUAL / DISCONTINUITY / END OF F-PLN where applicable → Direct-To → ARRIVAL / APPROACH re-selection or reconstruction → insert modified procedure → monitor FMGS/WASM state I am not claiming this is the confirmed root cause, but I thought this additional sequence might help narrow down the reproduction area. For reference, the related Microsoft Zendesk report is #284135. Thanks again for passing this to the team.

Hi, today I woke up and went to MSFS 2024 on PS5. I saw inibuilds planes, but when it showed the creator it did not show microsoft next to it It only showed alone inibuilds so is the third party on ps5 now???

This sounds promising. I flew the A330 recently and noticed it was extremely sensitive in rotation. The nose went up rapidly the split second I pulled back on the stick. Also, very hard to hand fly. It flew very similar to how the A350 flew when it was first released which a lot of real world pilots said was not correct.

Hello Beautiful Devs, With the new renovations made to the Pittsburgh Airport in the last few years, it has become an absolute pleasure to fly in and out of Pittsburgh International Airport. I am kindly requesting that a developer takes on the fun, but rewarding challenge of designing and developing a Pittsburgh Scenery. Not only would it open up a new major hub for vatsim traffic, but also appeal to I think a larger mass of avid flight simmers looking to expand their horizons. Thanks so much for all the work you guys do and hope to see a response!!!

Thank you, it works. I thought it happened automatically; I don’t think I’ve come across this with the other scenes I’ve bought. I’ll do the same for the others, just to be on the safe side. Thank you for your prompt reply. Kind regards.

Hi, You need to disable the default handcrafted scenery. Open the Marketplace from the main menu. Click on My Library. Search for the airport by its ICAO code or name (e.g.EGLL). Locate the specific handcrafted package or world update containing the airport. Select the item and click Disable. Restart your simulator for the changes to apply. Thanks!

Good evening, I’ve tried uninstalling and reinstalling the scene several times, but I’m still having the same problem: the airport is loaded onto the Asobo scene in the MSFS pack. Do you have a solution? Thank you.

Cool, Thanks for the information

Hi, Sorry to hear you've experienced a WASM crash. I appreciate you taking the time to provide your feedback and submit the log/bug report to Microsoft through their forums. We'll log this internally as well for the team to review. Thanks!

I experienced a very similar WASM crash in Microsoft Flight Simulator 2024 with the Microsoft/iniBuilds A320neo V2. Platform: PC – Microsoft Store Aircraft: Microsoft/iniBuilds A320neo V2 Flight: LSZH (Zurich) → LEPA (Palma de Mallorca) In my case, the crash occurred after a go-around while reprogramming the FMGS/MCDU for a second approach. Sequence immediately before the crash: Flying ILS Z RWY 24L into LEPA Go-around executed ATC instructed me to maintain 3,000 ft and cleared me toward MJV for another ILS Z RWY 24L approach After the go-around, the F-PLN showed MANUAL / F-PLN DISCONTINUITY / END OF F-PLN I entered and successfully inserted a Direct-To MJV I then started preparing/rebuilding the arrival/approach in the MCDU During this FMGS/MCDU reprogramming, the WASM module crashed Both the PFD and ND simultaneously displayed: WASM module crashed Package: microsoft-aircraft-a320neo Module: /SimObjects/Airplanes/microsoft-a320neo/attachments/inibuilds/Function_Interior/panel/inibuilds-A320.wasm Affected gauges: PFD and ND The aircraft itself remained in flight, but the loss of the primary flight displays made continuation of the flight impractical. The timing may be relevant because the crash happened directly after a go-around and during FMGS arrival/approach reprogramming. I have also reported this to Microsoft: Microsoft Flight Simulator forum – existing bug-logged thread: https://forums.flightsimulator.com/t/inibuilds-airbus-wasm-crash/737554 Microsoft Zendesk bug report: #284135 I can provide additional screenshots or test the same sequence again if that would help reproduce the issue.