Installation problem

[carponi]

After installind addon managerX 2.9.0.3 I've got this error,

couatl v2.0 (build 2315)
panic log started on Sat Aug 04 20:29:53 2012
Traceback (most recent call last):
  File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
  File "couatl\GSX\assistanceServices\__init__.py", line 212, in do
  File "couatl\common\criticalsection.py", line 23, in _synchronized
  File "couatl\GSX\assistanceServices\__init__.py", line 79, in requestVehicles
  File "couatl\GSX\__init__.py", line 566, in prepareGate
  File "couatl\GSX\assistanceServices\__init__.py", line 838, in setGate
  File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 71, in setGate
  File "couatl\GSX\assistanceServices\baggageLoader.py", line 68, in getSimObjectModel
  File "couatl\GSX\assistanceServices\conveyorBelt.py", line 29, in __init__
  File "couatl\common\modelCustomization.py", line 90, in checkedData
  File "couatl\common\modelCustomization.py", line 81, in validationError
RuntimeError: Error validating key 'pz' of model FSDT_Baggage_Loader_OA: required key not found

and my GSX is not working

Thank you in advance

[virtuali]

You need to update your vehicles, which is not normal you don't have updated, because the Addon Manager installer should check you have outdated vehicles and download their installer automatically.

To update your vehicles, either download the full GSX installer, or the vehicles updater available here on the forum.

[Jorik]

I have the same problem now.
I did a full reinstall of GSX with the liverie update but still no go.
When I ask for service they work a few seconds and then the <unknown> addon error pops-up.

couatl v2.0 (build 2315)
panic log started on Mon Aug 06 20:29:19 2012
Traceback (most recent call last):
  File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
  File "couatl\GSX\assistanceServices\__init__.py", line 212, in do
  File "couatl\common\criticalsection.py", line 23, in _synchronized
  File "couatl\GSX\assistanceServices\__init__.py", line 79, in requestVehicles
  File "couatl\GSX\__init__.py", line 566, in prepareGate
  File "couatl\GSX\assistanceServices\__init__.py", line 838, in setGate
  File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 71, in setGate
  File "couatl\GSX\assistanceServices\baggageLoader.py", line 68, in getSimObjectModel
  File "couatl\GSX\assistanceServices\conveyorBelt.py", line 29, in __init__
  File "couatl\common\modelCustomization.py", line 90, in checkedData
  File "couatl\common\modelCustomization.py", line 81, in validationError
RuntimeError: Error validating key 'pz' of model FSDT_Baggage_Loader_Servisair: required key not found




After the last install and liveries update I get this.

couatl v2.0 (build 2315)
panic log started on Wed Aug 08 08:57:10 2012
Traceback (most recent call last):
  File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
  File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 201, in do
  File "couatl\common\simObjectMoverIK.py", line 286, in run
RuntimeError: cruise speed must be positive

[Jorik]

I just did a full uninstall of GSX with all its components.
Deleted all the registry entry's I could find and cleaned up my registry.
Did a reinstall of GSX and reactivated it.

Still the same problem after a few seconds in the services I get this error log:
couatl v2.0 (build 2315)
panic log started on Wed Aug 08 09:27:08 2012
Traceback (most recent call last):
  File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
  File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 201, in do
  File "couatl\common\simObjectMoverIK.py", line 286, in run
RuntimeError: cruise speed must be positive

I'm using the PMDG 737NGX and have few programmes running trough simconnect.
Strange that this problem popt-up with the last update from the addon manager before it worked great.

[virtuali]

RuntimeError: cruise speed must be positive

This error means the AFCAD for the scenery you use has errors. As explained, many times already, ALWAYS include ALL the following information when reporting an error:

- The airplane used

- The scenery used. If it's not default, or if you used a different AFCAD for a default scenery, clearly indicate the scenery and the AFCAD in use (which can be checked with GSX opening the scenery customization dialog)

- The gate used

- The GSX operation requested

[Jorik]

I use PMDG 737-800WL NGX on the Faro X scenery from aerosoft.
AFCAD in use aerosoft/Faro X/scenery/AF2_LPFR.bgl
This error came up when asking for deboarding.
I use AES just to operate the jetway so I have all the doors except Door1 disabled in the intelliscene.cfg.
The strange thing is, I just tried to re-enable all the doors for AES and started GSX and no problem any more. After that test I again disabled all doors except door 1 but the problem stays away.
I will see what pops-up.

On the Jerez scenery I do have about the same problem when asking for Push-Back.
Here again the B738NGX PMDG with the FreeWare AKESOFT LEJR scenery with AFCAD Addon Scenery\AKESOFT JEREZ-X FSX\scenery\AFX_LEJR.bgl in use.
On stand 5, I customized the GSX config to have pushback on the straight parking spots.
I get this error when the pushback starts:
couatl v2.0 (build 2315)
panic log started on Wed Aug 08 17:08:27 2012
Traceback (most recent call last):
  File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
  File "couatl\GSX\assistanceServices\pushBack.py", line 252, in do
KeyError: popitem(): dictionary is empty

I'm used to making AFCADS myself so can you explain me where I need to look to make the AFCAD working with GSX. 

[virtuali]

Could you check the same airplane at a default airport, please ?

[Jorik]

Could you check the same airplane at a default airport, please ?

At default airports its still working.
The error "dictionary is empty" is solved with editing the AFCAD file of the Jerez airport.
The problem was that all the  parking-spots didn't connect to the taxiways. I made some apron links myself and the error went away.
The other errors went away with uninstalling and reinstalling GSX.
Thanks for the help.