All Activity

Hi Kyle, Any updates?

PC! I looked in the utilities section of the manager (the natural place for it, I would say) and couldn't see it

And LOD 150 gets you 2nm of draw distance, is this a joke?

Ok so LOD 150 works, which is unusable for me. Let me get this straight though, I need LOD 150 to see the airport from 1nm? I cant afford to run LOD 150... how can you sell an aiport and not advertise the fact you need a NASA computer. What a joke

Very disappointed... tried with PG on/off, increased LOD, config settings are all enabled except for static aircraft... no idea

So yesterday I spawned in at Gate 305 GSX repositioned the A380 and multi Jetways worked first time. Today however.... No changes made to anything since yesterday and yet no matter what I try jetways will not connect. I've uninstalled EGLL and the MJtool reinstalled both. Restared GSX numerous times. spawned at gate, taxied to gate. been towed to gate and re-positioned at gate. I've tried gates 301, 303, 305, 307, 405, 406 and then I gave up. went back to main menu spawned in at OMDB and they worked straight away. Back to main menu and back to EGLL G305 it all works fine 🤷 Clearly there is something weird going on but what is now beyond me.

Thanks for your response. So if I understand you correctly, Inibuilds has to enter a licensing agreement with, I guess the airlines depicted in the livery packs? And I assume the work that goes into securing these licenses is too bitter of a pill to swallow? So how does that work for developers like Captain Sim, who push truckloads of livery packs to the marketplace, are they just good pals with the airlines or with Microsoft? And also, if Microsoft were to allow free livery packs on the Marketplace, would that also solve the licensing issue?

I have exactly the same problems with the jetways on the iniBuilds A350, on all versions, A359, A35K the same. I have both GSX Pro, and the A350, as well as the simulator 2024 up to date. I have tested it at different airports and gates. The following problems always occur. I don't have these problems with any other airliner in the simulator, neither with all the internal iniBuilds Airbuses, nor with the A340 from iniBuilds that I also purchased. The jetways work perfectly with all of them!Tested Airports/Gates: Both at medium As and large gates, Jetway does not reach the aircraft: Airport: EDDM-München-Gate 110 -Gross Airport: EDDF-Frankfurt -Gate B34-Mittleres Gate KORD-Chicago Gate: L2-A-Mittleres Gate Airport: KORD-Chicago Gate:- M2-Mittleres Gate At small gates, the jetway usually reaches the aircraft and docks. Door opens!! Nevertheless message: No Jetway Not close enough!! and the stairs , not the jetway is used by GSX!!! Airport:EDDF-Frankfurt - B47-Kleines Gate The problem is: The jetways always "target" the 2nd door on the aircraft instead of the 1st door as with other aircraft. It doesn't matter whether I start the jetway from the EFB of the A 360 or via GSX "Operate Jetway" or via GSX "Request Boarding" Whether they reach the door and dock depends on the size of the gates. With the large and medium gates, they do not reach the fuselage/door at all, but simply stop a few meters in front of it. Only at the small gates, which are actually not suitable for the A350 family, do they usually reach the 2nd door and dock. Nevertheless, even at the small gates there is NO boarding via the jetway. The JETWAY is obviously not recognized by GSX during boarding, because the GSX message comes: "Jetway not close enough to a door" and the stairs and the bus are approached for boarding. I have already tried to set door 1 as the default in the GSX Aircraft Editor. But that didn't solve the problem either, the jetway still drives towards door 2 and doesn't reach it!! It's really a shame that the A350 from inBuilds is actually a really great aircraft Please help!!

To add, I am now also the proud owner of IniBuilds Dubai International Airport (OMDB) and IniBuilds New York JFK International Airport (KJFK).😋🥰 It looks gooood. Well done, IniBuilds Team.

That is of course your choice Correct at the moment passengers cannot be boarded Again your choice GSX at the moment doesnt do Multijetways so the only way inibuilds could incorporate them was to do their own thing. They are I believe working with FSDT to resolve this minor issue It hasn't been designed specifically to NOT use GSX. GSXZ isn't compatible at the moment with multijetways and so inibuilds A380 and 350 cannot be showcased properly without multijetways. None of the above detracts from my original point which was it doesn't stop your from doing your flight. If as you correctly say it's only "a visual" thing then it really doens't matter whether jetways connect or not. Just fly from point A to point B after all it's a flight sim not an airport handling sim.

Has anyone else been having issues with the engines shutting down repeatedly? Mostly during taxi? I’m on Xbox X with the Thrustmaster tca throttle packs (4 engine extension) There seems to be a conflict somewhere when going to idle, the start leavers for engines 2 and 3 toggle off and I loose engines 2 3 AND 4. There is then a wait for cooling before I can attempt to start them again. It was also happening during flight from time to time. I found an old Inibuilds thread on the fa forums mentioning a bug with bindings conflicts for the mixture, and I have cleared all those including keyboard assignments but am still having the issues.

Just had a totally unsatisfactory flight, STEP climbs were ignored as was the pause at TOD, even though both options were selected. Was operating a 12 hour flight at 4x and came back to the computer and was circling the destination at FL400.

I have no desire to use the multi jetway tool. It is a visual only thing as far as I’m aware, no passengers can be boarded via the jetways. I don’t want to be downloading and running extra stuff, there is already so much extra software to be utilised in flight sim and I would rather not to add to this list. GSX is the standard ground operations add-on that so many people use. I have never ever before come across an airport that doesn’t allow GSX to connect jetways. I think it’s very poor form that an airport scenery has been specifically designed where one can’t use GSX, and I’ve no desire to support something like that, I would rather just fly somewhere else.

Hi, Thanks for your feedback, as always! I will note this for the team to review. Thanks again!

Interesting, I'm not entirely sure. I've never had this issue trying to update the AIRAC. I'll look around the Synaptic discord for any others having issues. Thanks for your patience!

Are you on PC or console? Thanks!

Greetings, teams I have been testing the A380 across various gross weights on both v1.0.0 and v1.0.1 (streamed and downloaded versions) and both RR and EA Versions. I’m experiencing consistent pitch and rate-of-descent issues specifically during Flaps 3 landings with All Engines Operating (AEO), occurring on both manual and automatic approaches (single or dual AP). Observed Behavior: Pitch Oscillation (Flaps 3 AEO): Passing 800 ft AGL: The aircraft begins oscillating ~0.5° (ANU/AND). Passing 500 ft AGL: Oscillation increases to ~1.0°. Passing 300 ft AGL: Oscillation worsens to ~2.0°–2.5°. VSI/Pitch Discrepancy Below 1,000 ft: Hand-flying (having Manual Approaches) below 1,000 ft at a constant 2.5° ANU initially gives a normal 700–800 fpm descent. Upon passing 400 ft, without any pitch input change, the rate of descent unexpectedly spikes to 1,000–1,200 fpm (triggering GPWS sink rate alerts 😂). Passing 250 ft, the VSI drops back to 900 fpm, and stabilizes back around 700–800 fpm below 100 ft—all while holding the exact same pitch attitude. Note: This behavior does not occur in Flaps FULL under identical conditions (manual or autoland). Could you please look into the pitch stability and ground effect/flight dynamics modeling for Flaps 3 approaches? Many Thanks, Cheers! ~HaveASafeFlight!

Hi! How do those of us who have bought the sceneries via the marketplace get this tool?

SOLVED! , Delete WASM File and let it rebuild on sim start up :)

Dear @iniKyle, this also happens with me, trying to play downloaded version, trying to update 5 times. Also try to delete on WASM folder, but still not working. Once the download started, but stopped at 42% and tried 3 times with failed update. Anything to help, please? Many Thanks. HaveASafeFlight!

I'm not entirely sure. I will forward this question to the team for further clarification. I know our goal is to always improve the end users experience, this would definitely align with that. Thanks!

I guess the next question would be...is there at least something in the works to try and push a few more liveries to console or is this basically it. I mean I am missing the DHL livery on the A300F for 2024. It was there for 2020. I wish we ( console users ) hard more variety in the " special " liveries than the bog standard one's. It would be nice. I would definitely pay extra for those.

It's automatic on the EIS2 and manual with the EIS1, per the manual.

Read further down: