Folko

Hi, could you please elaborate what doesn't work? Are you trying it on a supported airport? Which one? And what exactly doesn't work?

Or maybe it doesn't touch the dataref at all so that it will keep the value from the previously selected aircraft? Then it would depend on which aircraft you used in the previous flight of the same session.

You can actually place jetways and marshaller on default airports, it's just not possible to do this automatically or use the default jetways. But you could create a custom overlay for the stock airports and place anything you want there.

Thanks, the empty scenery issues is already known and will be fixed in the next version. Apart from that, did it work on the next start (i.e. after X-Plane generated the ini)?

According to the log, X-Plane loaded the plugin successfully, but it had an error during the initialization phase. Did it create a sam.log file in the plugin directory? Since it even put the version correctly into the log, the version of your OS seems to be supported, otherwise it would have failed sooner.

That part would be easy. But allowing that would make jetways intersect with each other. For example, imagine two jetways on one gate that are configured like that. SAM would have to make sure that the jetways don't intersect when one connects to LF1 and the other one to LF2. By enforcing one door per jetway, the scenery author has control over this.