Standalone GSX V2 crash

[vekant]

hello, i recently installed gsx V2 but when i start boarding i have an errator saying to download and install standalone. except that there is more standalone with V2 ... I have installed in admin, and excludes the antivirus file adonmanager. Here is the log: couatl v3.2 (build 4032)
panic log started on Sat Sep 8 22:38:51 2018

problem raised by addon <unknown>
Traceback (most recent call last):
   File ". \ Common \ fsm.py", line 73, in executeDoFuncToCompletion
   File ". \ GSX \ assistanceServices \ __ init__.py", line 1210, in do
   File ". \ GSX \ assistanceServices \ __ init__.py", line 653, in createPassengers
AttributeError: 'Jetway' object has no attribute 'door'
{'Airport': 'LFPG', 'Requested assistance services at': 'Gate E 20', 'User Pos': (49.00137777838771, 2.5760944443796276, 123.707 m, 4.22636 m, 354.64595058005904)}
 
Can you help me ? thank you

[virtuali]

Please give more details about the airplane used, the number of passengers, the gate, etc.

[vekant]

PMDG 777, 305 passengers, I tried several door Terminal 2E Paris CDG

[virtuali]

Which kind of jetway this scenery use originally ? And, have you customized it in GSX ?

[vekant]

these are the jetway of Paris CDG SODE Taxi2gates,
A dakar scene of FSDG everything works well, On Paris CDG scene of Taxi2gates in gates no jetway everything works well with the A330 BBS, I have to do another test and I'll let you know
Thank you

[vekant]

with the 777 PMDG on jetway I get the error message on any airport without jetway everything works fine

[vekant]

I found the solution, I use TAB + S to have gateways, but when I ask GSX boarding, it crashes. If I call the gateways with GSX and not TAB + S the passengers come and it does not crash

[virtuali]

We found what was causing it, and put a safeguard against the crash. Note that, even if you won't see the problem anymore, it's best NOT to call 3rd party SODE jetways with TAB-S, if you use GSX. The reason why, has been explained here:

http://www.fsdreamteam.com/forum/index.php/topic,18371.msg128201.html#msg128201

The fix is online now, run Live Update to get it.

[vekant]

thanks a lot for your help ! I will test in the week =)