Jump to content

Griff

Business class
  • Posts

    13
  • Joined

  • Last visited

Everything posted by Griff

  1. Eventually sorted it by reinstalling the whole suite, reactivating World Jetways, and arranging xOrganizer to set the SAM libraries as high priority.
  2. I just purchased SAM World Jetways to add jetways to my existing default sceneries. I understand the program will only work with scenery that uses default Xplane jetway objects. I have tried with global airports as well as with airport packs downloaded from the Xplane Gateway (which should only have default jetways in the scenery). Anyway, I have activated World Jetways, the SAM library is installed, the plugin is installed, etc. I'm using SAM2 Suite ver 1.4.0 and with SAM plugin 2.2.6/World Jetways 1.0.4. SAM works at 3rd party airports with correct SAM gates, but default does not work (tried with Toliss and Zibo aircraft). What am I missing? No icon appears at airports to attach the jetways. I use xOrganizer as well and SAM normally works. Thanks for any assistance.
  3. I updated to SAM Suite 1.4.0 and was able to update to SAM version 2.1.3 without any error messages. Thanks for fixing the issue on Windows.
  4. Okay, well, I have set it for admin for future installs (it never mattered before) but now, 2.1.3 is not showing as available in the Sam Suite. I'm assuming it was pulled?
  5. I saw version 2.1.3 was released through the SAM suite. I chose to download it and while it will download, it installs to 100% and the install hangs. I can't close the SAM suite and the install doesn't seem to complete. I uninstalled, re-installed 2.1.2, and all was fine. Once I attempt to update to 2.1.3, the same thing happens. Any ideas?
  6. A few dump files were sent through the ticket system.
  7. I updated to version 2.0.9 today along with X-Plane 11.50 B17 and my sim would crash whenever I loaded a scenery with SAM jetways. I reverted back to 2.0.7 and my sim is now able to load and the jetways work. Last line of log.txt indicated the sim crashed because of plugin: AOS. Thanks..........
  8. I posted on the Flightbeam forums so hopefully it will prompt a response.
  9. Okay, thanks. I found X-Slew and was able to position the aircraft further up and the icon turned blue. Then, I was able to manually connected the jetway. I appreciate the help.
  10. This is what I see with manual mode activated. If I set it to "auto," there is an "A" on the grey tab and no door placement shown on the aircraft icon. Closing the doors manually with the Toliss doesn't change things. Thanks.
  11. Thanks for the reply but even after doing that, I can't get the jetways to work at Flightbeam's KPDX with version 2.0. I've tried the Toliss A319 (which the manual indicates should work in full auto mode) as well as the FF A320 which I know requires manual mode. I've tried "auto" and "manual" and the jetways are static and won't move and there is no indication of a jetway to connect via the controls window. I'll contact the developer to see if there is something to do on his end.
  12. Quick question regarding Sam version 2.0 and old versions. Flightbeam's KPDX for XP11 has a plug-in folder installed in the scenery folder itself and it contains an older version of SAM. When in the simulation, it shows 2 versions of SAM running and the jetways don't work (automatically or via manual mode). Does the scenery itself need to be updated to work with version 2.0? I tried removing the SAM folder from within the KPDX plug-in folder and nothing happened. Thanks in advance.....
×
×
  • Create New...

Important Information

Please read the Terms of Use