All Activity

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.

That's how it works, the terrain button just turns the display on, it has nothing to do with the map server. You can either put it in the sim EXE.html for auto-start or manually start the map-server.exe after the sim fully loads. The command window must stay open, just minimize it.

Hi, Yes, if you're using our multi-jetway tool with GSX, there is currently a limitation that prevents passengers from appearing. We've reached out to the GSX team in hopes of getting this resolved, but unfortunately, we have yet to hear back. Thanks for your patience and understanding!

Any chance you'd be able to join the Synaptic discord? They may be able to offer further troubleshooting. Thanks!

I can confirm: I connect the two jetways to the A350 via the EFB, but when I start boarding with GSX, it doesn't see them as connected—it reports "bad jetway data."

Hi, Thanks for your feedback! I'll test this and report back. I'm also curious to see whether this issue is localized to our liveries or if it's happening with third-party liveries as well. Thanks again!

Hi Liam, Thanks for your feedback. I'll test this in the morning and report back with my findings. Thanks again!

Hi everyone, I'll make sure this gets passed along to the team. While I can't provide a timeline for any updates, I can assure you that your feedback has been received and will be shared with the team. Thank you!

Hi, Within the iniManager app, on the left hand side column, you should see a tab called GSX Profiles. Hope this helps, thanks!

Please ini give us callouts!

Hi Howard, Sorry to hear you're having issues with the L1011. From what I can gather, this sounds like it may be a hardware issue, as I haven't seen any other reports of this behaviour. If you run into the issue again, I'd recommend unplugging and then reconnecting your throttle hardware to see if that resolves it. Thanks!

thank you so mutch

Morning! I've been enjoying the L1011. Haven't really experienced any issues until today. During cruise about 600NM from TOD I realize that my aircraft is beginning to slow down. I look and the throttles are fully retarded. I have the autothrottle in TM mode and have for the entire flight. It's commanding M.082 cruise... however we're now nose high and slowly descending. I can't get the throttles to do anything. So I disconnect the AT but the throttles do not respond to my joystick imputs. Testing in the settings it's working correctly, but no movement from the throttles. So I program keyboard commands for throttle increase/decrease and I can see the throttles respond a milimeter or two but not fully increase. They just instantly return to idle as if there's a lock. I can't find anyway to get the aircraft to increase thrust at all - so I had to exit my flight. Any suggestions on how to prevent this or correct it if it's happening? Using the default united paint and version 1.0.8.

Hi, Yes, I can updated this thread if we decide to make the Turbocommander. Thanks!

if they tell you yes could you tell me?

Hi, Thanks for your suggestion. I'll pass it along for future considerations. Thanks again!