FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Nevarc on September 26, 2019, 07:53:00 pm
-
After update all is working but the push back feature, soon as brakes are released I get an error (attached) I reloaded GSX 2 same error. P3d v4.5,
-
I am experiencing the same problem. Rerun FSDT live update but still coatl crashes when brake is released for push-back. Tried with PMDG 747-8 at KSFO and QW 787-8 at KIAD.
-
I too am experiencing this issue. I used the PMDG 777 @ Dubai. Released the brakes for pushback, and the error was prompted. The log is attached below.
-
+1
couatl v3.2 (build 4262)
panic log started on Fri Sep 27 08:21:07 2019
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\common\fsm.py", line 73, in executeDoFuncToCompletion
File ".\GSX\assistanceServices\pushBack.py", line 489, in do
TypeError: 'float' object has no attribute '__getitem__'
{'Airport': 'SBRB', 'Requested assistance services at': 'Gate 5', 'User Pos': (-9.86685991297958, -67.89654088206588, 196.153 m, 2.91084 m, 326.9255370553582)}
-
I would suggest running the gsx updater, as there has been a new update yesterday with affects pushback. Then you can also see here: http://www.fsdreamteam.com/forum/index.php/topic,22059.0.html mabe it's the same error...
-
In another forum in the support area someone mentioned a similar problem through using the quick pushback feature, however I haven’t ever used this feature or edited any pushback at all, so I’m not sure that this is the problem for us, as we are all getting the same error, and I’m pretty sure it was after the last update.
-
Did a complete reload of GSX 1 and 2 yesterday same error at any airport with any aircraft. Today did another update same error at any airport with any aircraft. This is only at pushback all other functions seem to be working, also noticed that when doing update the updater is keeps updating only the pushback updates? error text attached.
-
Agreed. I’m getting the same errors and have tried a fresh reinstall. I think it’s safe to say we need to wait to hear from Umberto or someone else from FSDREAMTeam with a solution or update.
-
+1 Not using hotfix yet....
couatl v3.2 (build 4262)
panic log started on Fri Sep 27 10:40:26 2019
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\common\fsm.py", line 73, in executeDoFuncToCompletion
File ".\GSX\assistanceServices\pushBack.py", line 483, in do
ValueError: need more than 1 value to unpack
{'Airport': 'EKCH', 'Requested assistance services at': 'Gate A 4', 'User Pos': (55.626991601139885, 12.644245414628443, 7.73218 m, 2.55118 m, 89.27987372195734)}
-
I too am getting this error after the latest update.
-
I noticed that if we do the live update (of course as administrator) the 'DOWNLOADING file C:\Addon Manager\couatl\GSX\assistanceServices\pushBack.pye' keeps trying to update
Try it, update and do it again it will say its updating this same file over and over.
My Addon Manager directory has always been excluded from AV as has all my flight sims and addons since the FS9 days.
-
I guess we’re all in the waiting game until FSDREAMTEAM releases a fix or update?
-
Add me to the list. Got the error pushing back at KBOS by FlyTampa using the default pushback feature in the PMDG 737 on P3D4.5HF1. I just did the latest update. I knew I shouldn't have updated. This is what scares me about GSX. It was running great until now. >:(
-
Does anyone have an update or possible solution? We usually hear from FSDREAMTEAM usually within a few hours or maximum a day later. Not sure what’s going on but would love for this pushback issue to be fixed so I can use GSX per normal operations.
-
Seeing this as well, at both FSDT KJFK and a default airport (KPWM) at which I had no prior GSX gate/parking modifications.
Problem occurs regardless of pushback "style" (i.e. left, right, straight) and upon entering the editor. Error occurs immediately upon parking brake release.
Running 4.5 HF1. Problem persists after a GSX reinstall. Also a fresh P3D and Win10 installation; just spent the last 2 weeks rebuilding everything.
(Attached couatl.ini is actually renamed couatl.err; forums don't allow .err extensions...)
-
I get the same error. Have been for about a week now. GSX Program is unusable. I have tried adding couatl to AV/Firewall exception list, but that hasn't worked.
Here's the latest crash report:
_____________________________
couatl v3.2 (build 4262)
panic log started on Sat Sep 28 13:36:46 2019
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\common\fsm.py", line 73, in executeDoFuncToCompletion
File ".\GSX\assistanceServices\pushBack.py", line 489, in do
TypeError: 'float' object has no attribute '__getitem__'
{'Airport': 'KATL', 'Requested assistance services at': 'Gate B 34', 'User Pos': (33.64343888904141, -84.43643543111527, 315.406 m, 2.68244 m, 89.96062906360561)}
__________________________________
Help is appreciated.
-Eric Faber
-
Try updating the p3d client to latest hotfix this solved the pushback crash for me
-
Try updating the p3d client to latest hotfix this solved the pushback crash for me
I updated P3Dv4 client, content, and scenery to HF2. I still can't update pushBack.pye via Live update.
-
Update nevermind only straight pushback works then crashes quick edit pushback crashes instantly though I would hope they are busy trying to fix this as its happening to most people.
-
Same issue here! Uninstalled and reinstalled GSX, same: Crashes right after releasing breaks!
Ron
-
Why is this not being addressed? Im trying everything, roll back to old addon manager nothing working. This has frustrated me the entire day.
-
I can feel your pain and frustration. I think this is a problem all GSX users are facing after the update a few days back. And usually GSX addresses the issue within a matter of hours. I too haven’t been able to enjoy the sim as a result and hoping something gets done soon.
-
And usually GSX addresses the issue within a matter of hours.
Correct. Umberto is very much on top of at least an acknowledgement to an issue. One of the greatest customer response times anywhere.
As the days/hours pass, I'm developing 2 theories.
1) Umberto is visiting Microsoft - this would be good.
2) There is an agreement/arrangement to not fix this too quickly in order to generate more sales of UGCX - this would not be good.
Either way, I've never seen so many major updates of any FSDT product until UGCX was released and then a burst of many updates for GSX to compete with UGCX. Now we GSX users are stuck for days without pushback by GSX.
-
;D I was about to complete my order of the competition and as saved from doing so. Now Ill just wait and use Shift P 1/2. I've never had a problem with FSDreamTeam before...first for everthing i guess.
-
It's very unfortunate that the pushback feature of GSX stops working right around the same time FS2Crew releases their pushback addon. I'm not one to buy into conspiracies, but the coincidence here is definitely curious.
-
Why are you not answering these issues people are experiencing.
-
My guess is it’s the weekend and they’re not working right now? Hopefully by tomorrow they’ll be back at it, we can hope? It’s a shame because I really only have simulator time on the weekend and really haven’t been able to with this pushback problem. Praying for a fix tomorrow at this point.
-
I am also having this same problem - Pushback crashes after brake release. Please HELP!!!
-
Just had this happened at ST Barths the other day to me as well?
-
+1
-
My guess is it’s the weekend and they’re not working right now? Hopefully by tomorrow they’ll be back at it, we can hope? It’s a shame because I really only have simulator time on the weekend and really haven’t been able to with this pushback problem. Praying for a fix tomorrow at this point.
I checked the weekend theory long ago - the last response from Umberto was Thursday the 26th.
-
Note to self!
Never update before a weekend.
Never update unless absolutely necessary.
In all this madness..I will still say thank you as you try to improve your product. Wing walkers next as it happens with every flight. Thanks..
Looking forward to your fix of the push back feature. For now back to Shift+p 1/2
Valued Customer with almost every product you offer.
-
Same issue here, error when Pushback starts
Pierre
-
I’m sure it’s the latest update from GSX causing the issue but I’m kind of glad you mentioned FSCrew. I just might go check it out. Thankfully we still have the built in pushback that came with the sim. Not the best but at least it works.
-
I've learned my lesson as well...ignore updates!!!
-
+1 >:(
Just bought today the GSX2 Level 2.
P3D V4.5 + KMIA Miami default and PMDG B738F Cargo. Tried twice with the same Couatl Restart error just before "ready to pushback!". I used the FSDT Live Update between sessions, which it seems was useless.
I have GSX since its start. But this last months the updates are twice a week and quite long.
Hope there is a cure.
Regards,
Heron Jr
-
Same here
ouatl v3.2 (build 4262)
panic log started on Sun Sep 29 20:45:15 2019
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\common\fsm.py", line 73, in executeDoFuncToCompletion
File ".\GSX\assistanceServices\pushBack.py", line 489, in do
TypeError: 'float' object has no attribute '__getitem__'
{'Airport': 'PANC', 'Requested assistance services at': 'Gate C 3', 'User Pos': (61.174677778110535, -149.9841972181738, 48.7477 m, 2.40772 m, 81.96159226362627)}
-
I noticed that if we do the live update (of course as administrator) the 'DOWNLOADING file C:\Addon Manager\couatl\GSX\assistanceServices\pushBack.pye' keeps trying to update Try it, update and do it again it will say its updating this same file over and over.
This is not normal, and looks like your local Cloudflare node is not serving the updated file, that's why the updater is trying to download it again.
This is very likely what's causing the error, because if a file depends on another, and one of them is not updated, errors will surely appear. Try Live Update again, I forced a refresh of some files that might hopefully result in your local Cloudflare node being updated correctly.
-
1) Umberto is visiting Microsoft - this would be good.
2) There is an agreement/arrangement to not fix this too quickly in order to generate more sales of UGCX - this would not be good.
3) It was a weekend, and I haven't noticed this thread because I was away.
And, there must have been some kind of problem with one (or more) of the Cloudflare nodes because, of course, I couldn't replicate it here ( if I run Live Update, I'm not getting the files from the same server as other users, unless you are located close to me), because from your error log, it shows you all had outdated versions of the pushback file.
As I've said in another post, I forced a refresh, which will hopefully get you the latest files.
Unfortunately, the way Cloudflare updates (or fails to update) files is entirely outside our control. Sometimes it happens, we ask Cloudflare support, they almost invariably reply they cannot replicate the problem, and it eventually fixes itself automatically after a day or two, and usually before the Cloudflare support people have a chance to reply. Sometimes the update files are spread in minutes all over the world, sometimes they get stuck for a couple of days but only on some servers, and we don't have any way to find if there's a problem, until users in the affected node reports it or, if I'm "lucky" enough the affected node is the one closes to me, which is not easy, since there are 170 of them around the world.
-
I am not an expert, but there must be some way to ensure that the remote deployment was successful. Some kind of cheksum or similar, so that if it is not correct the update is ignored.
Just a humble idea.
Best regards
-
I am not an expert, but there must be some way to ensure that the remote deployment was successful. Some kind of cheksum or similar, so that if it is not correct the update is ignored.
Just a humble idea.
Best regards
I agree wit you!!!
Regards, Pit.
-
I am not an expert, but there must be some way to ensure that the remote deployment was successful. Some kind of cheksum or similar, so that if it is not correct the update is ignored.
Of course we use checksums, how else the updater could know if your local file hasn't been updated ? Of course the remote deployment was successful, we surely don't upload wrong stuff by mistake.
What went wrong here, is the synchronization between our own server (which surely contained the correct files), and the Cloudflare cache, which is supposed to replicate our server over the Cloudflare network, which as of today counts 194 servers:
https://www.cloudflare.com/network/
This usually works in less than a hour but, sometimes, SOME servers, get stuck with old files for even a couple of days. The only way for us to know this, other than waiting for reports from affected users, would be using a VPN to impersonate an user from a different country, and trying to connect to *each* of the 194 servers, that would be the only possible way to know if everybody really got the correct file.
There's no way we could work without Cloudflare: a single server for all the world would constantly crash each time we release an update, if the bandwidth cost wouldn't bankrupt us in the meantime...
Not that this affects only us in any way. This summer, Cloudflar went down, and took half of the whole internet with it:
https://www.datacenterdynamics.com/news/cloudflare-goes-down-outage-caused-network-performance-issues/
-
The lesson learned here should be NOT to do any kind of release or patch when you know support won't be available right after the release. Just my 2 cents.
-
Is there any new update regarding current status? Has the pushback been fixed?
-
The lesson learned here should be NOT to do any kind of release or patch when you know support won't be available right after the release. Just my 2 cents.
The issue is, it would slow down getting updates for everybody, even those NOT affected.
The most common time we finish something and have an update ready, is usually at the end of the week and, purposely delaying any update to the next Monday would prevent all those not affected by getting the latest files for no reason. And, what if we had a critical bugfix ready on a Friday evening, should we postpone the upload to the next Monday ?
-
Is there any new update regarding current status? Has the pushback been fixed?
Haven't you read my previous posts from this morning ?
There was nothing to fix in the pushback, but some users still got outdated files for it, so I explained why this happened ( Cloudflare delays in updating files on some of their servers ) and also said I forced a refresh, and hopefully you'll get the correct files now, if you were one of the affected users.
-
What would have happened if 100% of the users had an issue? NO SUPPORT.
-
What would have happened if 100% of the users had an issue? NO SUPPORT.
The forum would have crashed instead, if all users were really affected.
If it hasn't happened, it's precisely because it was something that affected only *some* users: those close to a server that was slower than normal to get the updated files, it wasn't a bug or something like that.
-
Just wanted to confirm that after running a Live Update, GSX pushback is again operating properly. Thanks for addressing!
-
Hey Pilots, lets just wait for the update... No reason to keep pushing on this.
Happy Flying! 8)
-
Hey Pilots, lets just wait for the update... No reason to keep pushing on this.
Wait ? The problem has been fixed already, for those affected by having an outdated file on their local server.
-
Right, Lets go flying! 8)