Marten@Stairport

Try this: aircraft.xml

Thanks, that's easy to fix. @chrispalf The configs are being updated in each official release which can be downloaded through SAM Suite. The next version (2.0.9) is scheduled for next week by latest.

Can you please try this adapted version, thanks: aircraft.xml

@chrispalf Thanks for your detailed feedback. We are already on it, expect a fix in the next version. One background information for you guys: We have different items to identify the aircraft as someone already stated. The reason why we use a combination of those rather then a single value is that they can be the same for 2 different aircrafts. Like description "A350" could cover a A350-900 or A350-1000 which might have different door configurations. Or you have the same aircraft type from 2 different developers like A320 from FlightFactor or JARDesign. In theory the doors should be in the same position but... from our experience every aircraft model is different (but nothing is like the real). All in all we have to monitor all aircrafts in that regard but to the fact that there are so many (yes we own ALL) it's hard to keep track of everytime. Therefore thank you for your help and support!

Interesting. I updated the aircraft and reconfigured it and it didn't change for me but probably a mistake on my side somewhere. We will include both just to be safe. Not at all. SAM has a fallback to any door which is configured by the aircraft author (only LF1) in case a custom SAM config couldn't be found

By using the latest XP rc version

I just tested your LTFJ scenery and those jetways are obviously too short to connect: If you send me the scenery link + gate number of your screenshot I will try to replicate your exact situation.

Can you please provide me the scenery and parking spot for a test? And you guys can test the attached xml aircraft.xml

Just tested the latest 737U (3_37_6_full_T) and it works fine. So I assume that the jetway in your scenery is configured wrong. You may contact the scenery author for a fix.

They changed the identifier tags in the acf (again). Don't ask me why they do it with every update, quite annoying. We will have to update the config with the next SAM version.

You can revert back to 2.0.7 through the details page in the SAM suite in the tab "old versions"

Only the base plugin, the extension are not affected.

Why don't you simply revert back to 2.0.7 through SAM Suite? If you have issues with jetway heights it's likely to be a wrong setup by the scenery author but if you describe your test case we might be able to check it as well.

Details -> Old Versions:

Thanks for the feedback. Please use 2.0.7 in the meantime.

In the SAM suite go to details if the base Plugin. There you can install the previous version again. Oh and please post your log file!

By telling us what aircraft at what airport and which 3rd party scenery you use? You may also open a ticket

SAM Seasons does not include objects, only vegetation and ground textures

Well then it's all fine no? I guess it's not in the highest priority but usually all replicable issues will be solved at some point. Whenever that might be

In your inbox, sent by support@stairport-sceneries.com

If you haven't open a ticket on it, no. If yes, maybe...

1-2 weeks I guess. Yes feel free to share it.

No it's all fine. The reason why there are white aircrafts is that the scenery didn't define any airlines for the parking positions, that the StaticAircraft Library contains. We have a limited numbers of repaints but continue to extend it.

You're one of the few who would even notice something like that, let alone question it. There is a (more legacy) reason for that but we are already changed it for the release of 2.0.8.