WebMaximus

Thanks. I'm just about to start a flight from gate 8 at EGNM. I'm currently parked at the gate and the jetway is attached. I'll do what you suggest and wait for 10-15 seconds after switching on the beacon light and see if the jetway will detach. One more question on automation. I have the doors also set to be operated automatically by SAM. However, now when I just launched X-Plane and loaded the flight, the door in the Zibo mod is closed. What is the trigger that will open the door? Normally I'm used to open the door manually using the Zibo EFB and the Doors icon. After this, I start the flight also using the Zibo EFB to start the sound of boarding PAX. In this case though when relying on SAM operating the doors, it feels wrong starting the flight when the door is still closed.

With the jetway limits not being the issue, do you have any idea what would cause the jetway to not attach automatically once you've parked at the gate, shut the engines down, set the parking brake, switched the beacon light off and the door has been opened? Not sure if I remember what the trigger is for the jetway to attach? I know for detach, it's the beacon light coming on, correct?

I'm 100% sure the doors were closed since I always check for any open doors on the overhead panel before I start moving the aircraft. Will do another test and will then check again to be even 110% sure

Just had a look but this seems a bit too complicated so I'll just leave it as it is and hope Orbx will fix it themselves if need be One follow-up question though. Since the jetway is attached just fine when I load a flight at this particular gate, is what you suggested above about Orbx not setting the jetway limits high enough still valid? As mentioned above, one side of the issue I have is the jetway won't detach when I switch the beacon light ON. Maybe I'm completely wrong here, but I was thinking if the values/limits were not correctly set, the jetway wouldn't be correctly attached when loading up a flight either...? Anyway, here's what it looks like when I load up a flight at gate 8 at Orbx EGNM in the Zibo mod

Cool, will give it a try!

Many thanks for the prompt and detailed support! What you say about the Orbx scenery and how the jetway didn't attach correctly (and automatically even when having SAM set to automatic operation of jetways), is that something I would be able to adjust myself to make the jetways work correctly? Or is that something that needs to be done by Orbx? I've now removed the link as suggested since I'm no scenery developer

Hmm...yep...I'm slightly confused right now The reason I figured it would be good to use option 2 was to avoid this: And the reason I chose to do this manually was to make sure everything is in place as it should be. Because before this, I didn't have a SAM_Library folder (or a link to it) in the Custom Scenery folder. And I was told that could cause issues. At least with Orbx airports. And the reason I started messing around with SAM in the first place was how the jetway wouldn't attach nor detach automatically to the Zibo mod at gate 8 at Orbx EGNM. The idea was maybe this was caused by not having SAM_Library in place. But guess the culprit is something else then after what you've just said. This is where I've discussed this for Orbx EGNM.

Just tried this which I think had the desired effect mklink /H /J SAM_Library "F:\X-Plane 11\Resources\plugins\SAM\lib\SAM_Library" I can now go to my Custom Scenery folder where I find a SAM_Library folder even when it's just a link taking me to the real SAM_Library folder.

If I would like to do this myself, what switches should I use in Windows 10 using the mklink command to make sure it works correctly? I'm guessing I should use the /J and /H switches? Here's what I get when issuing mklink /? MKLINK [[/D] | [/H] | [/J]] Link Target /D Creates a directory symbolic link. Default is a file symbolic link. /H Creates a hard link instead of a symbolic link. /J Creates a Directory Junction. Link Specifies the new symbolic link name. Target Specifies the path (relative or absolute) that the new link refers to.

Ah, thanks! I did miss that part. Or rather...I was somehow "tricked" to miss that part I guess you could say because someone over in the Orbx forum told me this is required to make things work. Which puzzled me since I couldn't recall I saw anything about it in the user doc. So, this means Orbx should do this for their airports using SAM such as EGNM to make sure they work correctly. However, since I guess there will be some time before all developers modify their products to follow this new file structure, I could do it myself to make sure all my SAM-enabled airports work correctly right away without waiting for updates from the developers. Or is there maybe more to it?

Looking at the documentation that comes with the latest version of SAM (2.0.2), it doesn't say anything about the need copying the SAM_Library folder to Custom Scenery folder. Wouldn't it be good to have that information in the documentation? Looking at the note on the download page over here, it says you can either copy the folder manually or... Option 2: Use a LinkShell Junction to drop a static link to the SAM/lib folder into your custom directory (tutorial) Where do I find the tutorial mentioned since it's not a hyperlink I can click?

Ok, thanks for confirming but still think it would be a good idea to change something in the version nr to help people understand something indeed changed. And at the same time avoid questions such as mine

I've been notified 3 times via email from Aerosoft the last 24 hours there's a new version of SAM. And looking at the download page for SAM and the file information, the updated field indeed seems to indicate that is correct. Right now it says the last update was 2 hours ago. Still the version number stays the same (1.1.0) so just trying to understand what's going on and why all these updates without the version number changing? Normally, the version number (or rather revision number) would have been something like 1.1.0->1.1.1 followed by 1.1.2 etc.