FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: RikvanOosterhout on December 31, 2012, 10:06:43 am
-
Hi there,
Since yesterday i got a very annoying problem which happened by a lot more of you i saw.
This is my error in the .err file. It are a lot of errors...
I have already reinstalled the addon manager and gsx
couatl v2.0 (build 2322)
panic log started on Sun Dec 30 11:28:32 2012
Traceback (most recent call last):
File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
File "couatl\GSX\assistanceServices\catering.py", line 191, in do
File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 205, in do
File "couatl\common\simObjectMoverIK.py", line 286, in run
RuntimeError: cruise speed must be positive
-
That's not a GSX problem and, as was already explained on the forum, it's caused by an error in the AFCAD of the scenery you are using, like orphaned nodes, overlapping nodes, not connected parkings, etc.
I guess it all works normally at default airports and the problem is shown on a specific scenery. If this is the case, it would be better if you said which scenery is.
-
Ok, I got it at VRMM from aerosoft. Has somebody a fixed afcad for it.
Rik
-
Ok, I got it at VRMM from aerosoft. Has somebody a fixed afcad for it.
If it happens only there, it's very likely the AFCAD has errors, like overlapping nodes or orphaned nodes or unlinked parking spots, or perhaps they did something not very standard to accomodate unusual things in the airport, like having AI seaplanes for example. We might have a look at it and see if it's at least possible to better defend GSX against such non-standard AFCADs.