FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Driver170 on October 14, 2015, 12:46:58 am
-
I have two error reports because of GSx crashing at the gate when using the services at - FSDT LSGG and UK2000 airport EGGP.
I use FSX, 737 NGX, windows 7 and the latest GSX software.
couatl v3.0 (build 3187)
panic log started on Fri Oct 09 18:20:02 2015
problem raised by addon <unknown>
Traceback (most recent call last):
File "couatl\common\fsm.py", line 61, in switchToState
File "couatl\GSX\assistanceServices\__init__.py", line 1038, in enter
AttributeError: 'NoneType' object has no attribute 'playGUI'
{'Airport': 'LSGG', 'Requested assistance services at': 'Gate 42', 'User Pos': (46.232440844482895, 6.10672405705358, 432.525 m, 2.4554 m, 89.91941093510161)}
couatl v3.0 (build 3187)
panic log started on Tue Oct 13 23:39:16 2015
problem raised by addon <unknown>
Traceback (most recent call last):
File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
File "couatl\GSX\assistanceServices\baggageTrain.py", line 272, in do
File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 222, in do
File "couatl\common\simObjectMoverIK.py", line 390, in run
RuntimeError: cruise speed must be positive
{'Airport': 'EGGP', 'Requested assistance services at': 'Gate A 11', 'Requested parking services to': 'Gate 5', 'User Pos': (53.33654861221754, -2.8571525367016273, 26.8506 m, 2.4666 m, 355.5953589356847)}
-
RuntimeError: cruise speed must be positive
{'Airport': 'EGGP', 'Requested assistance services at': 'Gate A 11', 'Requested parking services to': 'Gate 5', 'User Pos': (53.33654861221754, -2.8571525367016273, 26.8506 m, 2.4666 m, 355.5953589356847)}
This is surely a scenery error.
This error usually indicates the scenery AFCAD has an error, like overlapping nodes, orphaned nodes, unconnected links, unreachable parkings, etc. You might try to fix it using the ADE or AFX "Fault Finder" options, or at least having an idea what's wrong with the AFCAD, and report it to the developers.
-
Well LSGG is from FSDT ?
-
Well LSGG is from FSDT ?
I'm referring ONLY to the quoted error at EGGP, because it happened yesterday, so I assumed it was this one you were referring to.
The other error is from 5 days ago, it's NOT the "cruise speed must be positive", and it doesn't have anything to do with the scenery, it seems like something that might happen if you press the GSX keys too quickly in sequence.
And besides "GSX keeps on crashing", is a bit too strong, when you only had an error 5 days ago, and a *different* one, caused by a problem with the scenery, yesterday.
-
This is from UK2000 developer...
Not sure what we can do as its GSX that is crashing out, not our scenery or FSX.
It looks like it's sensitive to AFCAD problems, but that a design issue with GSX it should be able to deal with any AFCAD issue it finds, by skipping the data it doesn't like, crashing out means no one programed it to expect the unexpected . I know Norman uses some special methods in some AFCADs to speed up traffic flow, these are reported as faults by ADE, but are totally by design. We cant base our AFCADs on the design requirements of another addon.
-
Not sure what we can do as its GSX that is crashing out, not our scenery or FSX.
If FSX doesn't crash, if doesn't mean the AFCAD doesn't have errors. It might have AI issues that might go unnoticed, maybe because they happen far from your position.
And, GSX hasn't "crashed" either. It has produced a clean error report, which has been made for the precise reason to report of potential problems in the AFCAD that might not be noticed otherwise.
I know Norman uses some special methods in some AFCADs to speed up traffic flow, these are reported as faults by ADE, but are totally by design. We cant base our AFCADs on the design requirements of another addon.
The error USUALLY means there are orphaned nodes, overlapping nodes, or unreachable parkings, and none of these can be justified to be by design.
If you could send me the AFCAD, I can easily check if those are true errors or not.
-
To be honest i'm all confused with all this and need professional help to solve what the issue is!
I will send the AFCAD tomorrow night. How do i go about sending the right one? And is it for both airports?
-
More from the producer -
I have checked Stand 11, and Stand 5, there is nothing wrong with it, it uses a IN/OUT Plumbing system.
If there's a specific item that's identified as causing a crash to all GSX users all the time at Liverpool , than yes we can look at it, but I find nothing wrong with it. I suspect this is GSX not used to seeing this AFCAD Layout, and crashing for some users, but not all
The fact it also crashes using your other airport addon, backs up the fact GSX should expect the unexpected and make the program more robust, if FSX can read and process our AFCADs then GSX should also read then them without crashing.
-
I have checked Stand 11, and Stand 5, there is nothing wrong with it, it uses a IN/OUT Plumbing system.
The "plumbing system" it's surely not standard, but that doesn't mean much, such AFCAD might still be correct and possibly usable by GSX, provided it doesn't have the other errors I indicated. The problem might not necessarily related to those stands so, checking them only, wouldn't help much.
The fact it also crashes using your other airport addon, backs up the fact GSX should expect the unexpected and make the program more robust, if FSX can read and process our AFCADs then GSX should also read then them without crashing.
The error you had LSGG doens't have ANYTHING to do with this or the scenery, it's an entirely differnet issue that I arlready explained to you in my previous post and might probably happen everywhere, if it was just an issue of pressing keys too fast.
-
Ok so i'll just send EGGP AFCAD ?
-
Ok so i'll just send EGGP AFCAD ?
I have absolutely no problems with UK2000 scenery and GSX. In fact I use UK2000 EGGP as my default airport.
I am using the AFCAD eggp_afx_UK2xTRM.BGL.
-
Well i have no idea whats going on!
-
Ok so i'll just send EGGP AFCAD ?
That's what I asked. Best if you use email. Email address is on the "Contact Us" page of this site.
-
sent and i hope i have sent the correct one ?
-
another crash
couatl v3.0 (build 3187)
panic log started on Sat Oct 31 14:17:30 2015
problem raised by addon <unknown>
Traceback (most recent call last):
File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
File "couatl\GSX\assistanceServices\baggageTrain.py", line 272, in do
File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 222, in do
File "couatl\common\simObjectMoverIK.py", line 390, in run
RuntimeError: cruise speed must be positive
{'Airport': 'EGKK', 'Requested assistance services at': 'Gate 5', 'Requested parking services to': 'Gate 10', 'User Pos': (51.15390851843792, -0.16624042152068016, 62.2077 m, 2.46767 m, 192.05619659652174)}
-
this happened at EGKK
-
another crash
I'm sorry, but you cannot expect that GSX would work with such out of standard AFCADs, like those using this "plumbing" system.
ADE and AFX reports many faults with it, even if they might not be "real" faults (according to the developers), because it's very difficult for any program that would need to read that file, to know what is legit and what is an error, ESPECIALLY (as in GSX), since it contains A LOT of code to defend itself against things that are definitely errors (like overlapping nodes, for example).
So, if we "fixed" GSX to ignore such errors, it might work on airports that use the "plumbing" method (assuming they don't have *other* errors), it would then stop to detect and defend itself against real errors found in thousands of freeware (and commercial) AFCADs.
-
So what should i do then?
-
So what should i do then?
There's nothing you can do and, we cannot be sure if that AFCAD has a *real* error, or it's just using non-standard practices like plumbing.
The issue is, you sent me an AFCAD for EGPP by email some days ago, which also uses the plumbing system and crashed GSX, but I tried it, and I didn't had any crashes.
Please clearly indicate a reproduction case, by email, referring to the file you sent by email, because it's impossible to even test if the problem CAN be fixed, if you don't provide an exact report we can reproduce.
So, please, by EMAIL, indicate all the following, in relationship to the file you sent previously:
- The airplane used
- The gate used
- The GSX operation you selected
If you want to report about THIS error happening on EGKK you are reporting here now, then send by email its AFCAD too.
-
The thing is its happening randomly. So its hard for me to reproduce the error again, because once it happens it doesn't return at that gate.