FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: MiguelSantos on January 01, 2025, 02:39:15 pm
-
Hi guys,
Since last update I'm getting a coualt crash jus after pushback and disconnecting the tug.
It's been about 5 or 6 flights in a row, with different airplanes and different airports.
After restart continues to work normally and finish the flight.
Log attached.
Thanks
Happy New Year
Cheers
Miguel
-
Same issue, every flight since the latest update. Appears to be wing walkers causing the issue in the logs? I've had this in FSLabs A321, PMDG 777, TFDi MD-11, at various airports either with or without custom profiles. Only thing I did since the update was turn wing walkers off in the options.
emulateText_MSFS [GSX] Commencing push. All engines clear. Start at will 2.0
emulateText_MSFS [GSX] In position, please set parking brakes 6
Pushback Detach entered
wingmanOperate
wingmanOperate towbaropen
emulateText_MSFS [GSX] Unlocking gear 6
pushbackArmsOpened notify
Pushback Detach self.sema.join()
moveTruck()
Traceback (most recent call last):
File ".\common\fsm.py", line 73, in executeDoFuncToCompletion
File ".\GSX\assistanceServices\pushBack.py", line 1630, in do
File ".\GSX\assistanceServices\pushBack.py", line 350, in wingwalkersGoAway
AttributeError: 'NoneType' object has no attribute 'speedAdjust'
{'Airport': 'YPPH', 'Requested assistance services at': 'Gate 204', 'User Pos': (-31.943719359814544, 115.96963427197302, 21.7621 m, 4.37034 m, 103.35992608909525, -0.005046610056488598, -0.0, -0.00044544866756505665, 4.572, 1.0)}
-
Just tried with the option of wing walkers enabled and it worked fine.
So option disabled as issues. In fact the wing walkers continue to show up even with the option disabled.
Hope it helps.
Cheers
Miguel
-
+1
See log attached.
-
Just had this occur with wing walkers enabled this time and it still crashes at the push disconnect.
-
+1
-
+1
Sur MSFS 2024 aussi
-
I experience the same issue, plus the positions of the Horizon Simulations Boeing 787-9 are all messed up, except the front left passenger door.
Is it possible to roll back to the previous version?
-
Is it possible to roll back to the previous version?
You would have to back up the Add-on Manager folder before updating it in order to roll it back. That way, you just simply copy the backed up files back in. Once you've updated it, it's not possible to roll it back if you don't already have a backup of the Add-on Manager folder.
-
The same issue for me - have had wing walkers turned off but they still appear at the start.
Happening at various airfields all with Fenix aircraft for me (not tried others).
Ian
-
Hi,
the same issue here. Using Fly-By-Wire Mod for the Asobo Airbus A320neo (A32NX) at various airports. Wing Walkers disabled. Worked before Update with no problems.
Regards
Hans
-
Just flown again. Heathrow WITH wing walkers, no crash.
-
Same here!
Wing walkers can not be disabled. However they appear next to the aircraft even with option off, I don't need them at all.
I have nothing to do with wing walkers in Europe, however nice to have them for US area and so on...
-
Same here!
Wing walkers can not be disabled. However they appear next to the aircraft even with option off, I don't need them at all.
I have nothing to do with wing walkers in Europe, however nice to have them for US area and so on...
Yes, i also have the same problem. Its a bit anoying, but im sure they are on it already.
-
Got the same issue here every pushback
-
Please clarify if this happens ONLY if you explicitly Disabled Wing walkers (they are Enabled by default), since I can't see how it could possibly happen with wingwalkers Enabled.
If it really happens with Wing walkers enabled, please provide precise, exact, reproduction steps.
-
For me, this issue occured every flight when setting wingwalkers OFF in the global settings, and never occured with wingwalkers ON in global settings
-
Confirm! wing walkers off crashes coualt.
-
Confirm! wing walkers off crashes coualt.
Confirm!
Crash with wingwalker disabled; here is the log :
couatl v4.8 (build 5565)
panic log started on Tue Jan 7 17:57:54 2025
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\common\fsm.py", line 73, in executeDoFuncToCompletion
File ".\GSX\assistanceServices\pushBack.py", line 1630, in do
File ".\GSX\assistanceServices\pushBack.py", line 350, in wingwalkersGoAway
AttributeError: 'NoneType' object has no attribute 'speedAdjust'
{'Airport': 'ZSPD', 'Requested assistance services at': 'Gate 16', 'User Pos': (31.149646452142644, 121.79592385002483, 8.46129 m, 4.23178 m, 342.09057561894235, 0.008112615131122174, 0.007853982038795948, -0.0001178963225301212, 4.129735134887696, 1.0)}
-
Only when option is OFF for me.
Thks
MS
-
confirmed,
wingwalkers OFF -> crash on disconnect.
wingwalkers ON -> tutto bene.
-
Thanks to everybody, I only needed that confirmation. The fix is already online now, just run an update CHECK in the FSDT Installer, the version number won't change, but you should get the updated pushback code.
-
I really, really don't get why updates are being pushed without a version number bump. We're all on the same version number, and some of us have the fix, some of us don't. Makes no sense.
Are people supposed to know to just click Check once in a while, in case fixes have been pushed without a version bump?
-
I really, really don't get why updates are being pushed without a version number bump. We're all on the same version number, and some of us have the fix, some of us don't. Makes no sense.
Because this is NOT an "update", it's an hotfix which fixes just this single problem which has been discussed in this very thread, where I clearly said in THIS case there will be no version change so, users reporting and reading this thread would KNOW the version won't change in THIS case, because I just said so.
Are people supposed to know to just click Check once in a while, in case fixes have been pushed without a version bump?
Again, you are in this thread, the only one that discussed this problem, and you read it, so you know it's an hotfix and the version won't change. Since we release real updates very quickly, the version number will change anyway in a few days, so the point would be moot very quickly.
-
Has anyone installed the latest update ver 3.3.3 and can confirm if the issues intro'ed by 3.3.2 in MFS 2020 are resolved?
-
Has anyone installed the latest update ver 3.3.3 and can confirm if the issues intro'ed by 3.3.2 in MFS 2020 are resolved?
If you are referring to one discussed in this thread, they were already fixed with an hotfix released as soon it was reported
-
I was still getting error and crashing Coualt 2 days ago after push back using ver 3.3.2. Are you referring to a hotfix released with/after 3.3.3?