Marten@Stairport

Can you please upload the sam.xml located in the scenery folder of that scenery? I might have an idea.

Can you please upload your log from plugins/SAM/logs as well.

Can you please test any default airport in that regard? I don't have that scenery so I can't really follow up with it.

That scenery is a mess. They included old SAM jetway objects that don't work properly anymore. Developers must not include any SAM content in their scenery except the sam.xml.

Which airport/scenery and gate?

Most likely because your browser is changing the http format into secured https. Make sure it's using the non-secured http upfront.

This is my default KDEN airport in the Felis 742 at B38W (there is no plain B38 for me?). Your scenery looks slightly different, confirm it's the default one? For debugging purposes you can enable the debug mode in the SAM base plugin settings and take a screenshot like this: The green arrows indicate the jetway calculation, I wonder which color these have in your case. However I found a really big issue in your log: SAM 1.0.8 loaded Loaded: Custom Scenery/KPDX - Portland International/plugins/SAM/win_x64/SAM.xpl (com.stairport-sceneries.sam). Looks like this scenery is shipping a SAM version which is the worst thing you could have. The old version "fighting" against the new version. You must only have ONE SAM installation and definitely NOT inside a scenery folder.

Please try this directly downloaded version and extract it manually: http://sam-suite.com/sam3/seasons/1.0.6/SAM_Seasons.zip

My bad, the link was wrong but now is correct. Please try again.

KLAX 132 doesn't look like suitable at all

What did you changed? We didn't change the logic in that regard since SAM2.

You can directly download it here: http://sam-suite.com/sam3/seasons/1.0.6/SAM_Seasons.zip

There is actually no difference between the files in that regard. WorldJetways uses EXACTLY the same textures like the default X-Plane jetways. Do you have the same issue with other aircrafts? Maybe the Felis 742 in combination causes this issue.

Besides the fact that you're installing SAM2 which is legacy (find latest version here) a complete uninstall of SAM followed by a clean installation should probably fix it.

It's still available:https://forums.x-plane.org/index.php?/files/file/59782-scenery-animation-manager-suite/ But you should rather share your SAM log and report the airport and parking position so we can fix it.

At Aerosoft or X-Plane.org for example: https://www.aerosoft.com/de/flugsimulation/x-plane-11/tools/2884/sam-worldjetways-xp?number=AS14817

We're waiting for XP12 beta to see how we could integrate that because the whole system probably needs a major refactor. But marshallers by default are planned for sure.

The incorrect jetway connection is most likely caused by an incorrect jetway arrangement/config. Did you test multiple airports? Give us a detailed test case with a default scenery (with worldjetways if you have) if possible. The variables for various SAM actions are the same like in SAM2. What is your actual problem in that regard?

Not yet.

Okay, we need to investigate more in here. Could you please provide content-manager-log.txt from X-Plane 11\Resources\plugins\SAM\content_manager as well as your last log.txt from X-Plane root directory.

Please download the latest version here and overwrite all files. Then run the content manager as administrator again. https://cdn1.aerosoft.com/sam-suite/download.php?version=SAM_3.0.12.zip

Sounds good, welcome any time.

In fact there was no change between SAM2 and 3 regarding the connection modes. You can find the description in the PREFLIGHT section here: https://stairportscenerieshelp.freshdesk.com/support/solutions/articles/77000004368-how-to-use But you are right, we forgot to migrate the manual door override setting Will put that back in, thanks for the tipoff.

No there isn't. We're on Ubuntu as well afaik which works well. In fact it's not a direct problem with our plugin because that runs well on Linux. It's a problem with the steam authentication dll which is broken on Linux to some extent. That's why we can't solve the issue atm. Did you buy the extensions at steam? If so it might help if we convert your purchase into a native license key to skip the steam check.

This issue is only happening on specific Linux distributions and as we can't support them all this incompatibility can only be solved by using another environment.