FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Ciderman on October 27, 2017, 12:30:15 am
-
After updating to P3D 4.1 I'm getting the same error whenever I try to use GSX:
couatl v3.2 (build 3852)
panic log started on Fri Oct 27 00:30:23 2017
problem raised by addon <unknown>
Traceback (most recent call last):
File "couatl\common\fsm.py", line 67, in switchToState
File "couatl\GSX\assistanceServices\__init__.py", line 674, in enter
File "couatl\common\criticalsection.py", line 23, in _synchronized
File "couatl\GSX\assistanceServices\__init__.py", line 144, in requestVehicles
File "couatl\GSX\__init__.py", line 907, in prepareGate
File "couatl\GSX\assistanceServices\__init__.py", line 2018, in setGate
File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 145, in setGate
File "couatl\GSX\assistanceServices\baggageLoader.py", line 80, in getSimObjectModel
File "couatl\GSX\assistanceServices\conveyorBelt.py", line 57, in __init__
IndexError: list index out of range
{'Airport': 'KPWM', 'Requested assistance services at': 'Gate 8', 'User Pos': (43.64666971860855, -70.31070425109495, 14.4632 m, 3.49022 m, 5.89000923270236)}
Uninstalling and reinstalling GSX didn't help. The airport doesn't seem to matter either. However, it appears to be aircraft related although this A320 used to work perfectly until recently.
Thanks for your support
Martin
-
However, it appears to be aircraft related although this A320 used to work perfectly until recently.
If you noticed is related to the aircraft, you should have indicated which specific aircraft you used, since there are many A320s out there, GSX supports several, but not all.
-
It's the A320 by Project Airbus. But as I said it did work for years with GSX. Maybe the latest 2.x update broke it?
-
It's the A320 by Project Airbus. But as I said it did work for years with GSX. Maybe the latest 2.x update broke it?
That's not supported by GSX so, you are surely using a custom configuration. Please post your GSX.CFG, so we can check it.
-
I do and I have just fixed the problem. After deleting gsx.cfg AND the intelliscene.cfg file I rearranged the service positions and the new gsx.cfg file works perfectly fine. Something in the old one seemed to have bothered the new version of GSX. Here is the new and working file for your reference:
[aircraft]
nosegear = 11.30
refueling = 1
iscargo = 0
trafficcones = 1
preferredexit = 0
wingrootpos = 1.70 0.68 -0.15
wingtippos = 17.14 -4.69 0.96
fuelpos = 2.00 0.00 -1.00
waterpos = -0.50 -19.75 0.78
lavatorypos = -0.50 -19.75 0.78
engine1pos = -5.78 4.11 -1.56
engine2pos = 5.78 4.11 -1.56
engine3pos = 0.00 0.00 0.00
engine4pos = 0.00 0.00 0.00
[exit1]
pos = -1.83 11.58 -0.15 0.00
code = 1
name = Exit 1
[exit2]
remove = 1
[exit3]
remove = 1
[exit4]
pos = -1.75 -13.00 -0.04 0.00
code = 0
[service1]
flip = 1
code = 0
[service2]
flip = 4
code = 0
[cargo1]
pos = 1.63 8.35 -1.35 0.00
code = 2
name = Exit 2
uldcode = AUTO
[cargo2]
pos = 1.38 -6.15 -1.52 0.00
code = 2
name = Exit 2
uldcode = AUTO
[cargomain]
remove = 1