vitor2308 Posted February 28, 2021 Share Posted February 28, 2021 (edited) Edited March 2, 2021 by vitor2308 Link to comment Share on other sites More sharing options...
Marten@Stairport Posted February 28, 2021 Share Posted February 28, 2021 Please only write in english. Did you test SAM 2.2.2? Link to comment Share on other sites More sharing options...
Fortes Posted March 2, 2021 Share Posted March 2, 2021 (edited) SAM is not connecting the jetways to the zibo at any airport, I tried in several places and only with the Zibo this problem occurs, even starting a flight with the plane off on the Jetway, it does not connect. I tried in manual mode and there is no option to connect. ZIBO V3.46.9 SAM 2.2.2 Edited March 2, 2021 by Fortes Link to comment Share on other sites More sharing options...
Marten@Stairport Posted March 2, 2021 Share Posted March 2, 2021 Post the log in Sam/logs Link to comment Share on other sites More sharing options...
Fortes Posted March 4, 2021 Share Posted March 4, 2021 2021.03.04-14.45.53-log.txt this is my Sam Log Link to comment Share on other sites More sharing options...
flyillini06 Posted March 8, 2021 Share Posted March 8, 2021 I am having the same issue with the latest Zibo (3.46.11) as well as the last few versions. I start a flight at a default scenery airport with engines not running, and the SAM jetway starts connected and then retracts away! World Jetways 1.0.4 with Sam2 suite 1.4.2. Nothing in the log file. Link to comment Share on other sites More sharing options...
flyillini06 Posted March 8, 2021 Share Posted March 8, 2021 (edited) I noticed that the door location was different in the default 737-800 and the 737-800X XML files. I changed the B737-800X XML file to have the same door coordinates as the default 737-800.xml. This resulted in the jetway connecting at KLAS default scenery gate B19. Top is the original and bottom is the edited. Could it be that the Zibo 737 XML definition shipped with SAM just needs some tweaking? ➜ aircraft diff 737-800X.orig.xml 737-800X.xml 3c3 < <door position="LF1" x="-1.72599995" y="-0.579999983" z="-13.6000004" psi="13.0500002" opendref="laminar/B738/door/fwd_L_toggle" openvalue="1" opendelay="5" closedref="laminar/B738/door/fwd_L_toggle" closevalue="0" closedelay="10" type="1" /> --- > <door position="LF1" x="-1.61600006" y="0.2133600120" z="-13.9110003" psi="11.5600004" opendref="laminar/B738/door/fwd_L_toggle" openvalue="1" opendelay="5" closedref="laminar/B738/door/fwd_L_toggle" closevalue="0" closedelay="10" type="1" /> Edited March 8, 2021 by flyillini06 Link to comment Share on other sites More sharing options...
BrentBorg Posted March 10, 2021 Share Posted March 10, 2021 I noticed on the last few versions of the Zibo that the aircraft loads with the anti-collision light set to "on" when starting from the Turnaround state and this caused the jet bridge to retract when starting up the Zibo. I fixed it by saving a new turnaround state with the into-collision light set to "off". Maybe that is affecting your situation? Link to comment Share on other sites More sharing options...
Marten@Stairport Posted March 10, 2021 Share Posted March 10, 2021 I honestly can't confirm that. Neither the beacon-on spawning nor the incorrect door coordinates (using the 737-800X.xml included in SAM 2.2.2). You're free to change the coordinates of course. Default KLAS B19 Link to comment Share on other sites More sharing options...
flyillini06 Posted March 10, 2021 Share Posted March 10, 2021 Thanks Martin. Is the the latest version of Zibo? 3.46.11? Some users have reported troubles with the Zibo and World Jetways since earlier ones (3.44.XX and later). There was a theory that perhaps some reference coordinates, CG, geometry information, or something got changed between versions. I spawn to a "cold and dark" state with beacon off, so I haven't seen it spawn with beacon on. Sometimes, I can fix the issue in the plugin control menu by disabling auto mode and re-enabling it back from manual to auto. Then, the jetway will connect. I also would say that ~25% of the time when arriving at a new airport with the Zibo, and trying to dock, I do not get the docking guidance icon (grey vs green) on the screen. I'll try the changed coordinates for a while and see if that helps. Maybe it's an architecture related issue as I'm a Mac user. Link to comment Share on other sites More sharing options...
Marten@Stairport Posted March 10, 2021 Share Posted March 10, 2021 It is 3.46.1, will check out the latest build. Link to comment Share on other sites More sharing options...
flyillini06 Posted March 10, 2021 Share Posted March 10, 2021 I’ve had issues since well before that version, so I don’t think that’s it. Link to comment Share on other sites More sharing options...
Marten@Stairport Posted March 10, 2021 Share Posted March 10, 2021 just checked 3.46.11 without any issues as well. Besides a complete SAM reinstallation from scratch I'm currently out of ideas. Link to comment Share on other sites More sharing options...
cjreed Posted March 29, 2021 Share Posted March 29, 2021 FWIW I've been flying with v3.47.3 of the Zibo Mod and SAM has been working well for me. 1 Link to comment Share on other sites More sharing options...
TheAlpine Posted May 10, 2021 Share Posted May 10, 2021 3.47.8, Jetways has not been working since purchased in February. Have only used Zibo, but very disappointing nontheless. Link to comment Share on other sites More sharing options...
Marten@Stairport Posted May 10, 2021 Share Posted May 10, 2021 4 hours ago, TheAlpine said: 3.47.8, Jetways has not been working since purchased in February. Have only used Zibo, but very disappointing nontheless. This most likely doesn't have anything to do with the named aircraft. Did you contact the support staff? Link to comment Share on other sites More sharing options...
ItamarMazor Posted May 13, 2021 Share Posted May 13, 2021 Had this problem too. Easy fix. The aircraft xml for the 737-800x (zibo) is wrong. The Y- value is completely off. This makes AM rhink the door is way lower than it actually is, and consequently the jetway cannot reach. Replace the Y value in this file with the one in the regular 737-800 and all is fixed. @Marten@Stairport perhaps something you can address in an update? Zibo actually attaches a corrected xml file in the update packages now. IM Link to comment Share on other sites More sharing options...
mmeares Posted May 13, 2021 Share Posted May 13, 2021 (edited) Mine does but I never updated each time the Zibo released. Try updating SAM or reinstalling it. Also could be some plugin conflict. But I know mine work fine Edited May 13, 2021 by mmeares Link to comment Share on other sites More sharing options...
TheAlpine Posted May 17, 2021 Share Posted May 17, 2021 Thank you for the tips. I will explore and report back. I should have clarified that it does work depending on the airport and/or gate. Link to comment Share on other sites More sharing options...
dipperdolphin Posted June 21, 2021 Share Posted June 21, 2021 (edited) Having this issue with only the Zibo and the WW which is based of the Zibo. The levelup and all other aircraft work perfectly fine. Both are latest versions, and I recall SAM working fine with this version of the WW before I updated SAM to the latest version. Edited June 21, 2021 by dipperdolphin Link to comment Share on other sites More sharing options...
Recommended Posts