Jump to content

Marten@Stairport

Developer
  • Posts

    691
  • Joined

  • Last visited

  • Days Won

    48

Everything posted by Marten@Stairport

  1. Did you changed the airport multiple times in the same session before loading EGCC? It can happen that the system gets confused by multiple reloads. If not, at which gate exactly does it happen?
  2. Correct, the org store has some trouble with their email system. You can contact them directly to request the code of course.
  3. The mentioned sleeping issue, on which airports and stands is that happening? In manual and automatic mode? The issue on your GCLP Screenshot is that the rotation limits of the Jetway prevents a connection. We already tuned them for the next update to cover more scenarios.
  4. It has been provided in an update and is described in the manual as well. Please try the following: Delete the sam_settings.xml in X-Plane/Output/Preferences. Then all settings are back on default and so should be the jetway status indicator. If you then switch it off it should be permanently hidden.
  5. You're referring to a 1+ year old thread. The current version of SAM requires 10.14+.
  6. It's working fine for me so I guess you forgot to select the appropriate template?
  7. Hi Josh, generally yes. However the WorldJetway jetways are usually not designed to lower that much to the ground (the CRJ door is pretty low). That's probably why they don't work. You could try it with a parking position far outside on a long extended jetway. In worst case you could manipulate the WorldJetway values to lower it but that causes visual glitches so I will only describe you that if you really like to know it Greets Marten
  8. Please contact the scenery author. Probably the Jetway limits are not sufficient for your parking position.
  9. Is the SAM_WorldJetways folder present in plugins/SAM/lib? And please upload the full log
  10. Those entries are automatically added by the Plugin. If you delete them they will be added on next startup again. So you can keep them as they are. Yes, the WED preview is already adapted to the latest WED beta release and will be published within the next week I hope.
  11. Hi, we haven't heared of such a problem yet. We use the FF A320 ourselfs and don't have any issue so far. I personally just updated to 1.0.1 and can load a flight as usual. So whenever your crash happens you have to post your log.txt so we can see what happened before.
  12. Generally speaking developers should set up a wider range for each jetway to cover all possibilities and test it out with as many aircrafts as they have. I can assure you that it is not a general SAM issue otherwise the entire x-plane crowd would have gone crazy already
  13. SAM stores its files in the Plugin directory. It is not necessary to have any sam directory in the custom scenery folder anymore.
  14. We forgot to increase the version number in the last update. I have just uploaded a hotfix to 2.0.2. If you redownload it now it should be fine. The versioning in the forum download pages is the same like the core SAM Library. All extensions have their own internal numbers. WorldJetways is on 1.0.0 and Seasons on 1.0.1.
  15. It does! You have a custom mesh which could lead to a different positioning of Jetways. Try without and see if that works fine.
  16. I'm not sure what you try to say with that link. If you would like to take full control over the ini then disable the automatic library addition in the aos settings page in SAM.
  17. Yes. I switched off beacon and engine cuttof (although not visible in replay). b738 - 2019-12-20 14.35.13.avi
  18. You don't have the reference because it is generated upon xplane startup only. Why do you need to see the library in xorganizer? I use it myself but don't see any good reason.
  19. Does that only happen for the zibo? It's working all fine for me in the latest version
×
×
  • Create New...

Important Information

Please read the Terms of Use