FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: MUC034 on October 09, 2020, 10:14:02 pm
-
Hello,
i use the a320 from fslabs with the aoc interface to control GSX. But i got the following message
"no traceback available" and this error log
couatl v4.0 (build 4471)
panic log started on Fri Oct 9 21:56:25 2020
problem raised by addon <no traceback available>
TypeError: No registered converter was able to extract a C++ reference to type struct FrameEventParam from this Python object of type EventParam
{'Airport': 'EDDM', 'Requested assistance services at': 'Gate 101', 'User Pos': (48.3580958723297, 11.782201651317411, 457.691 m, 4.45489 m, 83.52721243287762)}
after the failure massage i can restat the couatl- and then it works. can you help me to eliminate the error message?
THX
Tobi
-
It would be best if you enabled logging in the GSX troubleshooting settings, which will give a more detailed log in the %APPDATA%\Virtuali\Couatl.LOG file, which might help us understand the problem.
-
It would be best if you enabled logging in the GSX troubleshooting settings, which will give a more detailed log in the %APPDATA%\Virtuali\Couatl.LOG file, which might help us understand the problem.
I am having the same problem and it really is very annoying as data is lost in FSL case
-
I am having the same problem and it really is very annoying as data is lost in FSL case
Since you quoted my previous instructions to a more detailed report, where's yours ?
-
I am having the same problem and it really is very annoying as data is lost in FSL case
Since you quoted my previous instructions to a more detailed report, where's yours ?
couatl v4.0 (build 4473)
panic log started on Wed Oct 14 18:39:26 2020
problem raised by addon <no traceback available>
TypeError: No registered converter was able to extract a C++ reference to type struct FrameEventParam from this Python object of type EventParam
{'Airport': 'SKRG', 'Requested assistance services at': 'Gate J 7', 'User Pos': (6.172925019339975, -75.42769493435155, 2145.33 m, 4.41995 m, 212.3082380796253)}
it is happening to me with all airports
-
You both posted the non-detailed log. I'll repeat again the instructions I gave in my previous post about creating a detailed one:
It would be best if you enabled logging in the GSX troubleshooting settings, which will give a more detailed log in the %APPDATA%\Virtuali\Couatl.LOG file, which might help us understand the problem.
-
The detailed log you posted is from a session you didn't had the error, so it's not very useful to us. However, it shows you haven't the latest version, so first run the FSDT Live update to get it.
-
I already attached the file sorry for not having made the full report
-
In the last few days Couatl has sometimes been crashing when I arrive at a gate and request deboarding (or the FSLabs requests it automatically). I have run the live update but this does not seem to resolve the issue. It doesn't happen all the time and is worse with P3D default airports rather than addon scenery. It happens both when I specify a gate before I park and when I just park at a gate and request deboarding. If I restart Couatl GSX then works.
I'm using latest version of P3D4.5 and the latest version of the FSLabs A319 on Windows 10 Home with all updates installed.
I attach the error log.
-
The same here!
-
Any idea?? ???
-
Any idea?? ???
We should give virtuali a chance to have a look - I don't expect support at the weekend :)
I had another crash today at LOWW when I requested catering after spawning. Can supply the log if that helps.
When I was at LFPG later on, GSX worked without issue.
-
Ok, we'll check this. Does it happen if you use GSX manually, not from the airplane integration ?
-
Hi,
Sorry, I don't have full logging enabled, but I will enable it next time I start the sim. I will also run the Live Update, although I did just run it a day or two ago.
I have been getting similar error messages when trying to use the FSLabs A320/321 GSX integration. I have not received these messages before using the FSLabs integration. Yesterday I received it a couple of times when pressing the "INT" button at the gate before departure, and today I got one when I switched off the beacon light, which should have enabled the jetway to connect automatically. I guess that's why the error occurred, because something happened in the communication between the A321/GSX and SODE. My parking brake was on, engines were off, and to get the jetway to connect I turned off the beacon light, and at that second I received the following error message:
couatl v4.0 (build 4473)
panic log started on Tue Oct 20 00:18:47 2020
problem raised by addon <no traceback available>
TypeError: No registered converter was able to extract a C++ reference to type struct FrameEventParam from this Python object of type EventParam
{'Airport': 'CYUL', 'Requested assistance services at': 'Gate A 4', 'Requested parking services to': 'Gate 4', 'User Pos': (45.457845804649345, -73.74585250226104, 40.3729 m, 4.40694 m, 355.478972667635)}
Thanks,
-
I have not received these messages before using the FSLabs integration. Does it happen if you use GSX manually, not from the airplane integration ?
That's not what I asked. I asked if it happens if you use GSX manually and not from the airplane integration, possibly with another plane. Your answer will help us UNDERSTAND where the error is coming from.
-
No
-
I have not received these messages before using the FSLabs integration. Does it happen if you use GSX manually, not from the airplane integration ?
That's not what I asked. I asked if it happens if you use GSX manually and not from the airplane integration, possibly with another plane. Your answer will help us UNDERSTAND where the error is coming from.
It happens to me is with integration and also manual
-
Please try the FSDT Live Update now, and see if the error goes away.
-
Hello,
I received the error again today, using the FSLabs A321, and again it occurred the second I switched off the beacon light, which should initiate the connection of the jetway. All other events with the FSLabs A320 and A321 are working with GSX using the inbuilt functons on the aircraft, and I have never seen this issue apart from when I switch the beacon light off in the A320 or A321. I ran Live Update today before I started the flight, but it made no difference.
I had a quick look at the coautl log and it seems it has only recorded the events after the error, as I restarted couatl and GSX when prompted and connected the jetway manually and requested deboarding.
Please find the log file attached.
Thanks,
-
I just completed another flight under the same circumstances as the first time I had the crash, but this time it worked OK. I shut down at Gate 4 at CYUL and when I switched off the beacon light I was prompted to connect the jetway, which I did, then the deboarding started automatically, as it should.
"Unfortunately" ;) I was trying to get it to fail again so I could get a log file with the error, but the damn thing worked :D .
If it fails again I will be sure to grab the error log before restarting couatl.
Thanks,
-
I have this same problem also, today I used live update, still had the problem. Downloaded the full GSX installer. Still have the problem. It's when I use the intergration. If I restart Coautl and then do it manually it does not crash. But this has been happening since BEFORE the latest FSL update, so that is not causing it. It started happening a few days the update.
-
I have just done some testing and I think I am narrowing down some of the conditions that cause a crash for me.
Using the FSLabs A319 and A320 (both latest version) at LOWW airport (default scenery with FTX Global).
I ran FSDT Live Update first a couple of hours ago.
If I spawn at Gate G34 and move to Gate G37 and request catering through the FSL integration I reliably get a crash (I have 5 logs I can send).
If I spawn at Gate G34 and move to Gate G37 and request catering through the GSX menu, no problem.
If I spawn at Gate G37 and request catering through the FSL integration, no problem.
I have tested this on both the A319 and A320.
So it seems to be only when the aircraft is moved and when using the FSL integration straight afterwards that causes a crash for me today. I will continue testing to see if I can provoke a crash using the GSX menu.
Hope this helps you track down the issue.
-
Another Couatl crash this morning - boarding was fine as I spawned at the gate and the aircraft did not move. The crash happened when the FSLabs requested deboarding at EGBB (UK2000) Gate 1. Log attached.
-
Another Couatl crash this morning - boarding was fine as I spawned at the gate and the aircraft did not move. The crash happened when the FSLabs requested deboarding at EGBB (UK2000) Gate 1. Log attached.
It's nothing to do with the FSL latest version. This was happening to me, with the FSL, before I updated it on Monday.
Aaron
-oOo-
-
Another Couatl crash this morning - boarding was fine as I spawned at the gate and the aircraft did not move. The crash happened when the FSLabs requested deboarding at EGBB (UK2000) Gate 1. Log attached.
It's nothing to do with the FSL latest version. This was happening to me, with the FSL, before I updated it on Monday.
Aaron
-oOo-
I agree, it was also happening to me before the FSLabs was updated to v5.0.1.114
-
Same issue, always when arrived to some place. Yesterday it was LFMN and LOWW, both logs are attached.
Both times aircraft was FS Labs A320, latest version.
GSX is also updated to latest version.
-
We are checking on this.
-
Could you please try the Live Update now ? We had a small update that might fix this.
-
Could you please try the Live Update now ? We had a small update that might fix this.
I've run Live Update and tested the 'order catering' scenario that was reliably causing a crash previously - it is now working fine. Hopefully this has fixed it, I'll do more testing tomorrow in particular arriving at a gate and requesting deboarding.
-
Success here!!! Thankyou Umberto, that seems to have worked. I just completed a flight from KMBS to KMSP and upon applying the parking brake, shutting down the engines, and switching off the beacon light, the jetway was attached and deboarding started automatically. I was flying the FSLabs A320 with IAE engines.
Cheers,
-
fixed here thanks ;D ;D
-
thanks for the feedback, I'll mark it as solved.
-
Confirm no more crashes, however now GSX does not work properly with FS Labs auto logic when arrived to a gate (i.e. you need to select deboarding rather than deboarding starts automatically when on blocks).
-
Confirm no more crashes, however now GSX does not work properly with FS Labs auto logic when arrived to a gate (i.e. you need to select deboarding rather than deboarding starts automatically when on blocks).
It has been working for me (P3DV4.5, FSLabs A320/321). Steps needed are engines shut down, parking brake set, beacon light off. For me the jetway then automatically connects and deboarding begins.
-
Since the new FsLabs build I encounter the same problem as described, I run the live update but nothing changed. It only happens on airplane integration and not manually. I will enable the logging and post a detailed log after the next segment.
Thank you for your support
[EDIT] I now completed a flight form EDDH to EDDL with FSLabs A319 IAE Variant. Everything works fine until arriving at the gate in EDDL when the ACFT tries to automatically engage deboarding sequence and couatl crashes as mentioned above. I reloaded the couatl engine and was able to deboard the plane manually. It has something to do with the automation of FSLabs acft. I attached the enhanced log file form yesterdays session.
-
push - up. The Edit of my last post with new information regarding the problem didnt push the thread up, so I add this answer.
-
Confirm no more crashes, however now GSX does not work properly with FS Labs auto logic when arrived to a gate (i.e. you need to select deboarding rather than deboarding starts automatically when on blocks).
It has been working for me (P3DV4.5, FSLabs A320/321). Steps needed are engines shut down, parking brake set, beacon light off. For me the jetway then automatically connects and deboarding begins.
Yes, I know these steps but when I do parking brake on, engines off and beacon lights off - it simply brings me a general GSX menu where I can choose "Request deboarding" but GSX does not start deboarding automatically like it used to do before the latest fix.