With the current Beta, I have several Gates (EDDF/D4 shown) where the UGCX pushback sequence doesn't initiate, see the attached video. You can see the pushback truck appearing for a split second, then the sequence is just stuck (no Go Ahead call, etc.). Do you have any idea what is causing this ?

I have already uninstalled and reinstalled the beta, also recreated the database. Doesn't help.

Video

https://www.dropbox.com/s/cyo8et0aqx86m8l/Lockheed Martin® Prepar3D® v5 2021-08-06 09-19-19.mp4?dl=0

Logfile

https://www.dropbox.com/s/c9yik6qjwyme7dy/Ultimate Ground Crew X.LOG?dl=0

Edited August 6, 20214 yr by mikealpha

Any idea, Bryan ?

But you don't have this issue at other gates at EDDF?  Just some of them?

Just at some airports and some gates. It is really weird. Just visually there is more than enough space for the pushback truck and I am always using the same plane (FSLabs) 

Does the log file reveal any problem? 

The log doesn't offer any clues I'm afraid.

If it only happens at some gates, but not others, it's hard hard to guess.  The scenery designer must have done something strange with those gates.

 

It happens only in the UGCX Beta though, not in the latest release version. Could be it reads something wrong in the database ?

I'll pass the mic over to Manuel... maybe he has an idea.

Hey Mike,

Just watched the video, I think I know what is happening. However, it's weird that it happens on some parkings but not in others, if you have GSX active. The problem is that on last BETA, GSX kills every simobject of type "ground vehicle". Let me show you the entire picture. In previous versions from last BETA, UGCX models (say: tugs, towbars, humans, etc.) were created in the simulation as "AI aircrafts", this was the initial behaivor, the problem with this approach/way to create simobjects in the simulation is that some 3rd party tools like World of Traffic, etc, or even more popular: FSUIPC, has a function ability that zaps (kills) every simobject specially "AI Aircraft" types around from the user aircraft (your plane). That's why even before BETA, we attempted to start working on making all our simobjects as "ground vehicles" so they would be "invisible" for these 3rd party tools, ensuring their lifetime of them in the simulation during pushbacks. Now, when we released BETA, we found out, (to our bad luck), GSX also kills every simboject of type "ground vehicles", I noticed that GSX tug is behind or aside in your video, so I'm suspecting it's GSX killing all our objects, once they appear, that explains why they disappear. You can experiment it by disabling GSX and allowing UGCX alone to do all it's ops once you finish using GSX. I know this changes everything, because our previous approach (making all our objects as "AI aircraft" made our tool compatible with GSX but not for other 3rd party tools, now we tried to make our tool compatible with the other 3rd party tools but now it's not with GSX...you know what I mean?).

Cheers,

Manuel

Hi Manuel,

thanks for the idea and the extensive explanation. I'll follow your advice to deactivate GSX for testing over the upcoming weekend.

It's bad news for me though. The complete GSX flow is nicely integrated into FSLabs A320 operation, with UGCX being nicely integrated as well, up to the Beta.  So I would not really like to loose GSX.

Add to that it seems unpredictable when UGCX gets killed now, I'm all the time caught by surprise. It's around a dozen airports with only some gates, where it happens. But I find more almost on a daily basis.

Regarding your attempt for compatibility, I think GSX is the more common 3rd party tool. I have FSUIPC as well, never had a problem with previous UGCX versions, and I use UGCX from day one.

Maybe you could rethink this decision !

Mike

Hey Mike,

However, there could be a probable fix into this, that is making an option to allow creating all objects as "AI aircraft" or "ground vehicle", either way will get killed by some 3rd party tools, but at least would give you the option to choose which, This has been in plans since some quite time, but i'm trying to find sometime to try to add this. Hopefully wont make much time, but I'm thinking in how much less fix would it involve so it doesn't needs much coding.

Cheers,

Manuel

Hi Manuel,

that would be great and certainly the best solution !

Mike

Hi Manuel,

just to confirm your suspicion. It's indeed GSX. One can leave GSX active, when doing nothing with it the problem but does not occur. But as soon as you do anything with GSX, e.g.  disconnecting the Jetway, UGCX later gets killed then.

Mike

Hey Mike,

Yes, it's GSX, I hope that probably I can find out sometime soon, as we has finished some MSFS projects, and I'll indeed come back to look at UGCX, to study then implement this small fix, because it was previously working.

Cheers,

Manuel

On 8/14/2021 at 6:35 PM, Manuel82 said:

Hey Mike,

Yes, it's GSX, I hope that probably I can find out sometime soon, as we has finished some MSFS projects, and I'll indeed come back to look at UGCX, to study then implement this small fix, because it was previously working.

Cheers,

Manuel

Yes please...

Thank you and Regards,

Richard.

On 8/14/2021 at 6:35 PM, Manuel82 said:

Hey Mike,

Yes, it's GSX, I hope that probably I can find out sometime soon, as we has finished some MSFS projects, and I'll indeed come back to look at UGCX, to study then implement this small fix, because it was previously working.

Hey Manuel,

just thought after some months I might ask again. Is there any time slot for that in sight ?

Regards, Mike