Jump to content

FlyJSim 732 and IXEG 733 not work with SAM?


Recommended Posts

I'm not exaggerating when I say that 9+ out of 10 times when I pull up to a SAM equipped jetway, the bridge does not extend to my aircraft when flying the FJS 732 or IXEG 733.

Oddly enough, often if I load into a SAM equipped airport as the start point, the jet bridge will show it is connected about 4 out of 5 times, and it will disconnect appropriately when I shut off the appropriate light switch. This occurs at both payware and freeware airports.

What can be done to get SAM to work consistently with these two popular aircraft for X-Plane?

  • Like 1
Link to comment
Share on other sites

I just checked back with SAM 2.1.2 (default EDDH, gate 4)

  • IXEG 733 -> Works perfectly fine. Might be an issue with the scenery that you used for testing. The jetway icon on the left screen edge should get blue when you are in connection range to a jetway.
  • FlyJSim 732 v3.41 -> Wasn't perfectly and door control was not working. Will be fixed in SAM 2.1.3



Edited by Marten@Stairport
Link to comment
Share on other sites

Thanks for your reply Marten, the airports I have with SAM that I constantly have issues with are FlyTapma KLAS, Drzewiecki Design Chicago Airports (KORD & KMDW), Imaginesim KAUS, StableSystem's (ZeroDollarPayware) KSDF, and a few others I can't think of.

I am using the IXEG v1.33, and FJS 732 v3.41.

I am willing to provide additional data from flights into these airports during instances SAM does not work in the IXEG or FJS, just let me know what I should upload to help.

Thank you.

  • Like 1
Link to comment
Share on other sites

Chiming in to add my experience as well since I've done some pretty extensive testing with SAM 2 & The FlyJSim planes.

At the time of writing this, I am running the most current version of SAM + World Jetways, as well as the latest version of both the FlyJSim 727, and FlyJSim 737-200. I've tested across a nice list of both payware & freeware sceneries, as well as X-Plane Gateway/Default scenery with World Jetways enabled, and have come to the same conclusion that, regardless of the type of airport, the SAM jetways are simply not capable of lowering themselves down low enough to recognize where the door is on any FlyJSim plane at this time, both in Manual mode as well as Auto. In all cases, the indicator that comes up on the side of the screen when approaching a SAM equipped gate does not appear, nor does it appear on first load in when loading the plane.


In some specific & very rare cases, it is possible to trick/force the jetway to connect to the 727 specifically by going into the SAM Jetway control menu, then fast clicking the Manual/Auto swap button in the top right on the window. But because the 727 is very CG sensitive, this only seems to apply when the CG is on center, or far aft making the nose gear (and thus, the door,) be raised up higher than a loaded, or especially heavy 727. This trick does not work on the 737-200 in my experience.

Although, as a user of SAM since basically the beginning, I remember SAM v1 never having any sort of issue with low to the ground aircraft like these, and the jetways would happily lower themselves to the required height to attach to the door. (Though the wheels on the struts would sink into the ground to accomplish this.) In my opinion, letting the jetway sink into the ground a few inches like it used to would be MUCH preferable over the quite literally 1% success rate they have now.


I don't have much experience with the IXEG 733 + SAM even though I do have that plane installed, I just don't wish to fly it any time soon, and haven't in quite some time, but considering it is the same height as the FlyJSim 732, I wouldn't be surprised if it had the same failure rate.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Don't have an account?

    An account is required to interact with and download content from the Threshold Forum.
    Forum is currently also locked down for guests because of heavy bot invasions. Sorry about that.

  • image.png.5d3ebd5638179a05dc5cfa67eaf4bf3a.png

  • Create New...

Important Information

Please read the Terms of Use