FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: DaBeLG on September 18, 2022, 11:39:24 am
-
Hi,
After i quick edit pushback the walker says disable parking brake and ready to start engines but no push back is started.
if i stop the pushback , then restart GSX pro and do pushback on pre edited pushback route it starts
Regards,
-
Maybe you closed the toolbar menu, if you re-open it, you should have a "Continue pushback" option.
-
Maybe you closed the toolbar menu, if you re-open it, you should have a "Continue pushback" option.
tried it doesn't work need to abort pushback and start again after the editor something happens why push back isn't starting (note i use marketplace airports)
-
Please provide reproduction steps, indicating the airplane used, the airport used and post your GSX profile as well. If you are using a Marketplace airport, it could be helpful if it was an FSDT airport.
-
Ok
steps
load airport + departure
Marketplace FSD Basel
LFSB gate 20 plane B738 or fenx a320 or FBW A32N
use flightsim.to GSX profile https://flightsim.to/file/39956/gsx-profile-lfsb-airport-basel-mlhausen-fsdt
reposition aircraft at current gate
do pre-flight checks (flightplan ,...)
request boarding
enter fuel
request pushback
do custom push back (move camera with xbox controller) move green plane arrow keys + num 1 and num 3
press enter
release parking brake
starting pushback + you can start engines ...
nothing happens (in outside view you see plane with the editor green dots)
-
nothing happens (in outside view you see plane with the editor green dots)
I tried following the same procedure, and can't see any problems, pushback completes normally, both without a GSX profile and with the GSX profile on flightsim.to
Since this is an FSDT Marketplace airport, be sure you run an "Update" on GSX Pro, so it would detect its installation in the Official folder and will download the unencrypted version of the airport in the GSX profiles folder, so it stays together with the .INI file.
-
nothing happens (in outside view you see plane with the editor green dots)
I tried following the same procedure, and can't see any problems, pushback completes normally, both without a GSX profile and with the GSX profile on flightsim.to
Since this is an FSDT Marketplace airport, be sure you run an "Update" on GSX Pro, so it would detect its installation in the Official folder and will download the unencrypted version of the airport in the GSX profiles folder, so it stays together with the .INI file.
Hi,
any idea what can mess up the pushback ( any way to log this ?) ? updates are done already and see your BGL files
Regards,
-
I have exactly the same problem when editing and the pushback line/points do not disappear, they are behind the aircraft
-
If you still see the green dots of the QuickEdit pushback, but GSX is still working ( this could happen if there was an error, but than GSX would have stopped ), the only possible reason I can think of, is another add-on sending too much traffic over Simconnect, so the sim doesn't have enough time to "talk" with GSX which is trying to remove those objects when exiting the editor.
-
If you still see the green dots of the QuickEdit pushback, but GSX is still working ( this could happen if there was an error, but than GSX would have stopped ), the only possible reason I can think of, is another add-on sending too much traffic over Simconnect, so the sim doesn't have enough time to "talk" with GSX which is trying to remove those objects when exiting the editor.
could be i have AIG spad.next pro-atc , etc as addons . i'll try to just use aircaraft and GSX
-
I tried it with the 737 in cold and dark and with all systems up without vatsim, then its working, does vatsim something to do with simconnect?
-
I tried it with the 737 in cold and dark and with all systems up without vatsim, then its working, does vatsim something to do with simconnect?
without AIG traffic injection and vatsim idd it works here also !!! very weird
-
any solution?
-
I can confirm this too unfortunately, seems to only happen when quick editing (in addition I have only tested default left/right so far and this works)
- Aircraft: PMDG 738 / Fenix A320
- Airport: Hamburg (EDDH - Marketplace) / Splid (LDSP - OrbX Central)
- Environment: Vatsim / Offline
Reproduce:
- Spawn at gate (doesn't seem to matter which one)
- Request pushback and wait for connection
- Quick Edit (final position doesn't seem to matter too)
- Editing dots remain
- Release parking brake
- No pushback
Might this be related with SU10? I can't tell exactly when this stopped working but I think it might've been around SU10 release for me.
Behaviour is as stated above: The editing dots don't disappear and pushback will not start after releasing the parking brakes.[/list]
-
Behaviour is as stated above: The editing dots don't disappear and pushback will not start after releasing the parking brakes.
The only common pattern from users reporting the editing dots not disappearing, was always in combination with some other product that creates lots of extra objects, like AIG traffic injector, but it might not be the only one, and it's usually happening more frequently at more dense airports, because there seems to be a limit (not documented anywhere, of course) on the maximum number of objects in the sim, after which Simconnect just breaks and stops creating new objects.
The thing is: Simconnect *does* have an error code called "TOO MANY OBJECTS", but nowhere is documented how it works or how large the limit ( assuming there is one ) is, or if the limit is the overall number of objects visible in a scene, or the maximum number of objects created in a given time, nothing in the SDK ever suggest anything like that, they mostly insist of using multiple LODs level, something we do extensively already.
If this is the case, I don't see any solution other than lowering all settings that might affect the number of objects displayed, like all traffic density sliders.
-
If this is the case, I don't see any solution other than lowering all settings that might affect the number of objects displayed, like all traffic density sliders
The thing is that there were no other objects in my offline test, I was alone at the airport.
I do have AIG but only the models which are only injected by swift for Vatsim, which has been offline.
2 or 3 weeks ago everything worked even with quick edit pushbacks. I had AIG and used it on vatsim at this time.
The only thing that changed are GSX updates and SU10.
Oh and I have set all these sliders to 0, so no default objects injected
Edit: I did a bit of extensive testing and while I managed to have the quick edit working once (with some addons active), even when disabling all custom addons that could spawn objects (sceneries, liveries like AIG or FSLTL) the quick edit pushback failed again.
I basically just had enabled: Fenix, PMDG 737/738, Aerosoft VDGS (don't use it actually), navigraph, spad.next bridge.
Even with only GSX, Navigraph and 4 or 5 marketplace sceneries installed the quick edit pushback failed.
I am a bit confused here what is going on. Is there a log we could provide? It seems there are some users affected but not all. But after disabling all the addons (that worked with GSX in the past by the way) and still having this issue with quick edit pushbacks I'm a bit clueless where to check next.
Edit 2: It seems as if somehow GSX is not "closing" the quick edit properly. When using the customization menu ("customize this parking position") and editing the "quick edit" pushback the movement markings / dots remain. Once I close the menu the dots disappear and I can use the saved quick edit. Unfortunately this menu is not available once the tug is connected otherwise we could use this as a workaround.
-
Same conclusion here.
edited push back works when AIG fsTLT and vatsim disabled . (but not 100%)
it has to do that pushing enter on edited pushback creates som simconnect error
what i do as workaround is edit parking stand and put my pushback in there then do apply and start then connecting to vatsim hoping no one is on my stand
regards,
-
GSX is not failing or forgetting to "close" the editor, since if it really did that, it should always happen, in any situation, to everybody.
What really seems to be happening, if you don't see the quick edit dots being removed, is Simconnect just not accepting commands from GSX anymore, and this seem to be related to the total number of object in the scene.
I managed to reproduce this by going to an airport with lots of individual objects ( default EGLL ), and turning on FSLT traffic injection OR even plain FSLT traffic with no injection, and in some cases, GSX couldn't even create its own Traffic Cones, and this without *ANY* error logged anywhere, neither in GSX nor in the DevMode Console.
The only indication something was wrong, was in the "Simobjects" menu option of the DevMode, where you can see all Simobjects that have been created, and the missing ones are labeled as "Invalid", as if the sim reached the maximum number of objects, so it started to refuse to either ADD but even REMOVE existing ones, that's why you still see the QuickEdit dots.
-
GSX is not failing or forgetting to "close" the editor, since if it really did that, it should always happen, in any situation, to everybody.
I wasn't referring to the editor not closing but the edit action itself. If you use the editor to edit the quick edit and then close the editor (as when you're finished with editing) the remaining dots also vanish. As there is no editor with quick editing this doesn't work.
What really seems to be happening, if you don't see the quick edit dots being removed, is Simconnect just not accepting commands from GSX anymore, and this seem to be related to the total number of object in the scene.
As stated in one of my edits I have this problem even with everything removed from my community folder. It was completely empty.
What I think is weird is that it worked with all those addons and AIG traffic with vatsim just 2 - 4 weeks ago. If it would only be a problem with too many objects this should've occured all the time shouldn't it?
And shouldn't the editor be affected the same way when to many objects are present? I'm trying to wrap my head around this.
Is there anything that could be done to re-fire commands to simconnect? After editing the progress seems to go on with "release parking brakes" "commence push"
-
I wasn't referring to the editor not closing but the edit action itself. If you use the editor to edit the quick edit and then close the editor (as when you're finished with editing) the remaining dots also vanish. As there is no editor with quick editing this doesn't work.
Not sure what do you mean with "editor" opposed to "edit action itself", regardless if you start QuickEdit from the GSX menu in the middle of a Pushback, or you start it from the 2D Editor Dialog, the code is exactly the same.
Of course, since this threads reports the issue has possibly happening during a Pushback, that's what I tried now and, I can see no issues, it works just fine UNLESS in the case explained before: a detailed airport with lots of AI. But in that case, the problem is not even the Pushback or the QuickEdit, it starts with GSX not even able to create its starting objects on gate, like Traffic cones.
What I think is weird is that it worked with all those addons and AIG traffic with vatsim just 2 - 4 weeks ago. If it would only be a problem with too many objects this should've occured all the time shouldn't it?
There has been SU10 update in between, maybe we just uncovered a Simconnect issue.
In any case, today we released an update, which allows to optionally install a Lightweight version of the Jetway replacement files without extra Ground clutter, and this should help maintain the overall number of objects under control, especially on big airports.
-
Not sure what do you mean with "editor" opposed to "edit action itself", regardless if you start QuickEdit from the GSX menu in the middle of a Pushback, or you start it from the 2D Editor Dialog, the code is exactly the same.
I'm referring to the 2D editor (edit action: quick edit from the GSX menu) where you can also edit the quick edit pushback (I know doesn't make much sense :D ). When the quick edit is saved there and then called via the GSX menu with "use saved quick edit" it works. So it only struggles when using quick edit from the GSX menu without the 2D editor.
But in that case, the problem is not even the Pushback or the QuickEdit, it starts with GSX not even able to create its starting objects on gate, like Traffic cones.
For me everything from GSX loads within milliseconds even with every addon and traffic enabled.
Now for the big BUT.
What is totally baffeling me after another hour of testing is this: When using the quick edit just with the green plane it stalls. When adding one additional step (blue circle with numbers) even if the pushback way is not altered it works several times in a row (every 3rd party I have enabled with ~ 10.000 liveries according to swift sitting in the community folder - so not actually injected).
I tried to confirm and used the quick edit without additional waypoints a second time -> stalls. After using additional waypoints again -> works every time.
-
So it only struggles when using quick edit from the GSX menu without the 2D editor.
That's why I said I tested this case, and it works.
When using the quick edit just with the green plane it stalls.
Please clarify which airplane you used, because I can't replicate this, using both the default Asobo A320 and the PMDG 737.
-
Nice find i'll try this today keep you posted
-
That's why I said I tested this case, and it works.
I know :) I just wanted to point out that (in my /our case) the observation with the remaining green dots is the same for quick edit and the 2D editor (editing the quick edit there). With the 2D editor the green dots vanish once the 2D editor is closed and the edited push back can be used.
I know you cannot really reproduce this, it's just an observation in thise whole matter.
When using the quick edit just with the green plane it stalls.
Please clarify which airplane you used, because I can't replicate this, using both the default Asobo A320 and the PMDG 737.
I've used Fenix A320. I'll test again tomorrow if I can reproduce this "workaround" once again and use other planes. I'll just make a video to summarize my observations and for you to be able to actually see what is going on
-
I also have this problem, both with the Fenix A320 and with the PMDG 737-800 at any airport.
The problem only arises when choosing pushback mode with the 2D editor. As has already been written, after using the enter key, I notice that the green points of the pushback trajectory remain in the scenery. No problem with other pushback modes.
To solve the problem, Couatl has to be stopped, restarted and then I choose to pushback using the previously saved trajectory.
-
I just made a test and tried both methods: Saved from the edtor or just Quick edit, with the PMDG 737, and they both work with no issues, see the following videos:
Using the editor to SAVE a Quick Edit:
https://youtu.be/7wIzDBJG60k (https://youtu.be/7wIzDBJG60k)
Creating a new Quick Edit in during the pushback, even with intermediate waypoints:
https://youtu.be/Sxpk7-7fSDU (https://youtu.be/Sxpk7-7fSDU)
-
Now for the big BUT.
What is totally baffeling me after another hour of testing is this: When using the quick edit just with the green plane it stalls. When adding one additional step (blue circle with numbers) even if the pushback way is not altered it works several times in a row
ok this indeed seems to work as work around if you press f6 to add pushback waypoint the pushback works
all pushbacks 10 yesterday worked with this senario 0 worked without the waypoint
Regards,
-
When using the quick edit just with the green plane it stalls. When adding one additional step (blue circle with numbers) even if the pushback way is not altered it works several times in a row
That's precisely why I made the two tests in slightly different ways, one without waypoints, another with, so you could also see that it works. You haven't said which airplane you used, so I tried the PMDG 737, because others that posted here said it doesn't work with that one.
-
That's precisely why I made the two tests in slightly different ways, one without waypoints, another with, so you could also see that it works. You haven't said which airplane you used, so I tried the PMDG 737, because others that posted here said it doesn't work with that one.
I've watched the videos and I noticed that you didn't use a quick edit without additional waypoints from the GSX menu (not the 2D editor). Maybe there was a misunderstanding, using no waypoints with the 2D editor works (for us) but not when using the GSX menu (Gauge version), there additional waypoints are needed.
As promised I just uploaded my video showing our problem, maybe it is a bit clearer with it. I've recorded Fenix A320 and PMDG B738 with and without additional waypoints. The last part is showing that using the 2D editor and closing it will actually remove the pushback path dots and using the saved quick edit will work as expected (this is not viable for Vatsim as the time to actually start the pushback is too long).
I've also tested the default Asobo A320neo with the same behaviour as shown with the two planes in the video.
-
Nice movie
100% what i'm experiencing
-
I've watched the videos and I noticed that you didn't use a quick edit without additional waypoints from the GSX menu
Here's with just QuickEdit and no waypoints, still works the same:
Is this happening on a particular airport ? It's a marketplace airport ?
-
Like I said only have MP airports also jetways are disabled for the payware airports i see you did'nt do that on EDDS
-
Is this happening on a particular airport ? It's a marketplace airport ?
Negative. I tested EDLP, EDDM and EDDH of which only EDDH is from the marketplace and the two others are 3rd party in the community folder. EDLP being the freeware airport from Aerosoft.
What gets me wondering is why the additional waypoint get's the pushback to magically work for us.
-
Like I said only have MP airports
GSX really can't work well on those, until the new Navdata update is completed but, since other users reported this on non-Marketplace airports, I don't think this is the issue.
also jetways are disabled for the payware airports i see you did'nt do that on EDDS
Disabling jetways or not can't have any effect on Pushback, but I'll do another video on a 3rd party scenery with GSX jetways disabled.
-
Hello everyone.
Same issue here.
My workaround is to do the custom pushback in the "customize airport positions".
Take care,
Moun.
-
This is one of the many problems I have with the latest build of GSX (5th Oct).
Other problems are GSX not working after landing (spinner), showing quickedit dots and crashing.
-
GSX is not failing or forgetting to "close" the editor, since if it really did that, it should always happen, in any situation, to everybody.
What really seems to be happening, if you don't see the quick edit dots being removed, is Simconnect just not accepting commands from GSX anymore, and this seem to be related to the total number of object in the scene.
I managed to reproduce this by going to an airport with lots of individual objects ( default EGLL ), and turning on FSLT traffic injection OR even plain FSLT traffic with no injection, and in some cases, GSX couldn't even create its own Traffic Cones, and this without *ANY* error logged anywhere, neither in GSX nor in the DevMode Console.
The only indication something was wrong, was in the "Simobjects" menu option of the DevMode, where you can see all Simobjects that have been created, and the missing ones are labeled as "Invalid", as if the sim reached the maximum number of objects, so it started to refuse to either ADD but even REMOVE existing ones, that's why you still see the QuickEdit dots.
When can we expect a fix for GSX for this problem?
-
This is one of the many problems I have with the latest build of GSX (5th Oct).
Just to clarify, this is what I have running every time I fly:
- MSFS
- Navigraph
- Volanta
- vPilot
- VAT-Spy
This happens to me randomly. Sometimes it works at LOWW, sometimes it doesn't. Same for all other payware airports, Marketplace, Contrail, Orbx, whatever, e.g. EFHK, EDDM, LOWS, LOWI, EGKK, EGLL, etc. No rhyme or reason that I have found.
-
couatl v4.8 (build 5027)
panic log started on Thu Oct 13 19:20:00 2022
problem raised by engine or unspecified addon
{'Airport': 'EFHK', 'Requested assistance services at': 'Gate 13', 'User Pos': (60.31597231486203, 24.972919693564723, 50.7375 m, 2.48042 m, 243.0471050342983, 0.017812153324484825, 0.024434609338641167, -0.0006545280639710057, 2.553919111633301, 1.0)}
emulateText_MSFS [GSX] Parking editor activated at Gate 13 4
MSFS always use CheckIcingConditionsSimple() + surface condition
Icing test = 0 10.9745483398 False
Error: exception UNRECOGNIZED_ID in call RemoveClientEvent param #2 '839846864'
{'Airport': 'EFHK', 'Requested assistance services at': 'Gate 13', 'User Pos': (60.31597231486203, 24.972919693564723, 50.811 m, 2.55392 m, 243.0471050342983, 0.024434609338641167, 0.024434609338641167, -0.0006545280639710057, 2.553919111633301, 1.0)}
emulateMenu_MSFS
emulateMenu_MSFS CHOICE -1
channel.balance = -1
disconnected from SimConnect.
SharedMemInterface created
Couatl is restarting gracefully
Here's what I found in the couatl.err file.
-
More data in after a failed pushback at EFRO this time in the attached file.
This didn't happen to me before the Oct 5 update. Now it happens on every flight. Can you upload an older build for the people with these problems to use?
-
This didn't happen to me before the Oct 5 update. Now it happens on every flight. Can you upload an older build for the people with these problems to use?
I'm sorry but, I still cannot reproduce that error and, nothing in the last updates could possibly have caused this. Your log shows something very unclear, like once you tried to open the airport customization page while a service was running, but that's not really the issue.
It seems as Simconnect comminication was somehow bugged, this can possibly be caused by other add-ons running at the same time and the sim cannot keep up with all of them, try to disable EVERY other add-on, except GSX, which might use Simconnect.
-
Thing is, GSX worked reasonably well for me since the beginning but since this last update it's a nightmare. Nothing else has changed in my setup.
-
Thing is, GSX worked reasonably well for me since the beginning but since this last update it's a nightmare. Nothing else has changed in my setup.
Since the ONLY things changed in the Last update are:
GSX Pro NEW: Added Jetway Floor heights data for iniBuilds KLAX.
GSX Pro Fix: Error when activating parking editor.
GSX Pro Fix: Ladder showing incorrectly on Fuel Hydrant.
FSDT Installer: Hotkey customization not saving the Alt modifier.
All of them being extremely minor changes that would only be noticed in very specific situation, and none of them had any relationship with the Pushback.
-
I'm having the same issue where if I use the quick edit, the dotted lines don't disappear and the push never starts. Workaround for me has been to customize the pushback through the customize airport position menu beforehand.
-
I'm having the same issue where if I use the quick edit, the dotted lines don't disappear and the push never starts. Workaround for me has been to customize the pushback through the customize airport position menu beforehand.
Just to let you know I found another workaround some posts above that it works when you add at least one additional waypoint with F6.
@virtuali
I can confirm this behavior for a friend who isn't here in the forum also with an unchanged Sim (so no additional addons but it worked before)
In my case I completely emptied my community folder and am still experiencing the problem.
-
Just to be sure, do you switch to drone yourself before doing the custom pushback?
It happened to me after I had switched to drone before clicking on quick edit.
Reloaded couatl and tried again, letting GSX switching to drone mode, maybe it was a coincidence though.
But I can say I NEVER had this issue befoe last GSX update, very annoying when flying on Vatsim, I use Pushback helper when it happens, so not great as I bought GSX for custom pushback.
-
Just to be sure, do you switch to drone yourself before doing the custom pushback?
I didn't change to drone camera before quick editing and had the problems.
-
for now like Phil said use the f6 key to add custom waypoint and it works ....
this is a very good workaround
-
Hello - also experienced this issue twice yesterday with the Fenix while using QuickEdit. Happened to me once at MSK Productions OMSJ (marketplace version/Navdata API enabled), and again at FlyTampa EKCH (non-marketplace/Navdata API disabled). Running vPilot (w/ FSLTL VMR), FSRealistic, Spad.Next, Volanta, Fenix.
Steps to reproduce and symptoms (green dots not disappearing) are 100% consistent with the below video. Something seems to have changed in the last week or two, as it was working 100% reliably for me previously (including post-SU10, suggesting it was a GSX update and not a sim change that broke it).
I will give the F6 workaround a shot but this is the single most important function for me in GSX so really hoping for a fix asap.
-
Hey I'm experiencing also the exact same issue seen in the video above. The only workaround I found was to just restart couatl then ask again for the pushback and just say to use the saved quick edit which is the one I've made obviously before the issue happened....and it works as intended. But I agree with some previous comment, I've never had such issues since the two last GSX updates.
I'll try the F6 idea, if it can avoid me to restart everytime Couatl I'll take it.
-
Happened to me once at MSK Productions OMSJ (marketplace version/Navdata API enabled), and again at FlyTampa EKCH (non-marketplace/Navdata API disabled). Running vPilot (w/ FSLTL VMR), FSRealistic, Spad.Next, Volanta, Fenix.
Steps to reproduce and symptoms (green dots not disappearing) are 100% consistent with the below video.
As I've said, and shown in the video, nothing in the GSX updates can possibly affected this. But with all these add-ons using Simconnect you are running at the same time, it's possible Simconnect is not able to keep up with all of them.
The clear indication of this is the pushback dots not disappearing. Since they normally do, as I shown in my previous video, meaning GSX is surely asking the sim to remove the dots, if the sim doesn't respond because it's overwhelmed by request by other add-ons, it has probably stopped the connection with GSX, resulting in its code not being run anymore, since it needs Simconnect to call it back at regular intervals.
-
As I've said, and shown in the video, nothing in the GSX updates can possibly affected this. But with all these add-ons using Simconnect you are running at the same time, it's possible Simconnect is not able to keep up with all of them.
The clear indication of this is the pushback dots not disappearing. Since they normally do, as I shown in my previous video, meaning GSX is surely asking the sim to remove the dots, if the sim doesn't respond because it's overwhelmed by request by other add-ons, it has probably stopped the connection with GSX, resulting in its code not being run anymore, since it needs Simconnect to call it back at regular intervals.
I understand that it could be related to too much simconnect connections (addons), but shouldn't that then also apply for the additional waypoint? As the additional waypoint works as a workaround every time it should also be affected if this was caused by too many connections, shouldn't it?
Does GSX calculate or send commands in another way when there's an additional point so the overall commands are reduced / split?
As you said it might be caused by too many addons I tested this and emptied my entire community folder so no addons at all where present and I still had this problem.
-
but shouldn't that then also apply for the additional waypoint? As the additional waypoint works as a workaround every time it should also be affected if this was caused by too many connections, shouldn't it?
Last video I posted shows no problems, even with with no waypoints.
-
Last video I posted shows no problems, even with with no waypoints.
Yeah I've watched it but undoubtedly some users are affected and to test as I've said I removed all addons to be sure there aren't just too many connections and it still failed.
My question was if this is connected to too many simconnect connections shouldn't the problem be the same when using an additional waypoint?
-
My question was if this is connected to too many simconnect connections shouldn't the problem be the same when using an additional waypoint?
If anything, it should be worse, since additional waypoints have an extra Simobject for each waypoint, and each extra object adds some extra connections to handle its creation/removal. But as I've said, I couldn't find any difference using waypoints or not.
-
If it helps, I have the same issue, in ORBX LEAS, with AIG but no aircraft on the platform and just three in the area covered by AIG. No more other add-ons, so I can't figure out a reason for simconect to be that busy, but who knows. In case it helps
-
with AIG but no aircraft on the platform and just three in the area covered by AIG. No more other add-ons, so I can't figure out a reason for simconect to be that busy, but who knows.
The first test would be trying without AIG, regardless how many planes has created.
-
Hi all,
I have the same problem - but only with Fenix A320. Maddog MD82 & Inibuilds A310 seem to work OK.
With Fenix, the green dots never disappear and the pushback never starts.