All Activity

Hello all here! At a first look onto this huge airport I saw that the jetway at C18A wasn't moving: Neither through GSX Pro nor through the A32X made by FlybyWire. Thanks! Bert FS Reviews

Ok I've fixed it. Looked on my Xfinity app for my internet and what do you know. Inibuilds was being blocked. I unblocked and turned off the advanced security as an additional step. Frist time this has ever occurred. But I've successfully installed it. By the way, the new KORD airport is stunning. Spectacular would be an understatement. The details inside and out should be applauded.

Be fair and allow the post prior to this ... unredacted ... as it speaks truth. and to be fair here are 2 SS of the same livery , it took me 2 days to get the glass back to tinted

Hi, Just purchased the scenery. Prior to this version, I had been using FSDTs KORD. I selected to install the GSX profile, but did not install the multiple jetway configurator. I don't fly large jets that need 2 jetways. Yes when I spawn at KORD in either the Fenix or PMDG, there are no jetways at any gate.

I had a CTD (full sim crash) on a long haul tonight, approximately 5 hours in which are similar to the reports above. I was doing nothing at the time. Aircraft: A340 EIS 2 Passenger (HB-JME) - Default ini Livery. Simulator: FS2024 Version: V1.0.12 iniManager Navdata Method: NAVIGRAPH OFP: MMUN/12R N0476F330 NUDA1A NUDAL UV106 PODON UG765 MAXIM Y262 LULLS DCT GUCEL DCT DROWN/N0474F350 DCT JITGO Y642 GRATX/M080F350 M593 AMENO DCT 2904N05721W 34N040W/M080F370 39N030W 43N020W/M080F390 DCT PASAS DCT SIVIR DCT RIVAK/N0463F390 DCT AKEMO/N0457F400 DCT GIGOT DCT OBATO DCT RESMI/N0454F390 DCT TEPRI DCT POGZI DCT GELTA DCT MANAG DCT PEVIT DCT BLM BLM3G LSZH/14 WASM Error: Full CTD (Please see provided logs) Specs: CPU: AMD 9850X3D, GPU: Nvidia RTX 5070, RAM: 64GB Autosave File: Please see attached. I was unable to extract the report file, but do have a .dmp available if required. 1784397219.bin

The work for Career mode compatibility is still being worked on :)

Got it, I'll log this for the team then.

Hello, a workaround for this is calling GSX and then triggering the jetways to move within the jetway app for the time being, thank you.

Did you do anything different to get it working?

Not working for me. So it's not resolved.

At least for me, its working fine again. Seems like Ini or the providers have changed something and the issue is resolved^^

I am doing all that except the mode to RMT as I only used one INS unit (INS 1). I've watched some youtube videos and I am following the same steps they do, all the same since launch, except that button to "auto batch" in the nav screen which is somehow recent.

I have Spectrum internet and I was able to disable Security Shield from the app on my phone and now I am able to log in and download.

I have Spectrum internet and I was able to disable Security Shield from the app on my phone and now I am able to log in and download.

I have Spectrum internet and I was able to disable Security Shield from the app on my phone and now I am able to log in and download.

I have Spectrum internet and I was able to disable Security Shield from the app on my phone and now I am able to log in and download.

Hello Using EFB I can move as expected, both jetways at compatible gates but when Starting boarding with GSX, Jetways are not used because GSX provides the info that there is no jetways . thus passengers are coming by Bus even if in GSX parking position, jetway is active . Something you need to check to get passengers using this type of jetways with GSX Thank you

Hello iniBuilds team, I hope you're doing well. I'm a happy owner of several of your aircraft and wanted to reach out with a genuine question rather than a complaint. I've noticed that the A350 currently shows as not available in Career Mode in MSFS 2024 (the Marketplace listing displays ✗ Career), whereas it previously appeared to have Career support. I completely understand that the sim updates (SU4/SU5) introduced core changes that affected third-party aircraft eligibility, so I'm not writing to push or complain about it. I'd simply love to know whether restoring Career Mode compatibility for the A350 is something you're planning to revisit in a future update, or whether it's currently on hold. Any insight into your thinking would be appreciated – even a rough "yes it's planned" / "not for now" would help me decide how I fly it. For context: I genuinely enjoy your aircraft. Your A320 and A330 are among my favourites, and the quality and attention to detail is what makes me want to fly the A350 in Career Mode too. So this is really just the enthusiasm of a fan hoping to use it there again. Thank you very much for your time, and for the great work you do.

Hi, You said you are on SU6 Beta, it's possible some behavior or unintended change as a result of SU6 could be causing an affect here. I don't have a HC Bravo but I will raise this to the team. Does this occur in current SU5?

Following on from above 15 min after the above WASM crash: I removed Inibuild Hamad Doha scenery. (the only thing that had changed in the last two weeks. I'd never had a WASM failure after many any flights before. I replicated exactly the same steps for departure. A350 returned to normal. No WASM on preflight. Normal departure and cruise. The only factor was the inibuilds Doha scenery.

Just recognized, after using the 300 after a longer time, that I'm not be able anymore getting the landing gear lever up and in the middle position. I use HC bravo and I'm flying in 2024, beta 6. The softwarelever stays in down position while the hardwarelever of the HC went up. It vibrates and bumps in that down position as if it tries to go up, but it doesn't can do it. Fortunately in the plane the gears are going up, only the lever in VC doesn't go up. For that reason I'm not able to arm autobreakes. I know it works before; I put the lever in the middle position with the mouse, but for that the lever has to reach the up- position before. What can I do here?

Follow on from above. 15 minutes later I tried the same flight same airport, same gate. I deleted WASM folder. Second ever WASM after many many A350 flights. This time inputting SID getting ready for departure at Inibuilds OTHH. Buying inibuilds OTHH is the only change I'm made to my system is several weeks. A350 has never failed before today after many many flights Autosave file attached this time Same details as above re specs and versions. 1784389413.bin 1784390016.bin 1784390619.bin

I've had the A350 since release and its always been excellent. I've never had a WASM issue until today. Aircraft: A350-100 QATAR airlines (A7-ANH) v1.2.6 Simulator: FS2024 1.7.35.0 Navdata Method: navigraph via inibuild a350 EFB OFP: attahec Using new installed scenery Inibuild Hamad Doha for the second time. parked at gate. prepping fro departure WASM Error: Orange screens. Had loaded pax, was refueling using EFB. Had finished init, flight plan, cockpit prep. Went back to update ZFWCG. bang! orange Specs: attached Autosave file: Unavailable . OTHHSBGR_PDF_1784386781.ae3443e7.pdf

I'll ask pass this along to the team, I know the PA message was an optional ECAM MSG if memory serves correctly.

Logged for the team, thank you