UGCX and Fscaptain

[flyasa]

is there any setting that would prevent USGX from pushing my back correctly? UGSC vehicles and wing walkers  always freeze in place During pushback.

www.twitch.tv/videos/909134809

[peter]

Hello Flyasa,

it is possible that FSCaptain interferes with USGX, depending on your settings and the way you use FSCaptain. For instance, there is a vehicle zapper, which doesn't do anything unless you enable it. It then clears your path, and that would be one possible explanation for what happens. Another one is FSCaptain's own pushback system. Normally, it should do nothing unless you click on pushback, but maybe you have some settings that do that automatically. Furthermore, FSCaptain has features that enable it to set/monitor GSX loading and pushback services. We have never used USGX, so we don't know if you GSX settings in FSCaptain could create problems with USGX.

We can try to get to the bottom of your problems, but we need more information. Can you send us (see blue link below) a zip file with your FSCaptain\Data\Log folder? Please send the email to all of us and copy the address of this thread into your message so that everyone on the FSCaptain team knows what the logs are for.

Cheers,
Peter

[Travis]

Hello Flyasa,

Sorry for my delay - an annoying sciatica flareup kept me from the flight deck for a few days.

From what I see in your video, I expect that our AI Freeze Ray is freezing / unfreezing your UGCX SimObjects.

The first view of the FCDU (at 0:24) shows the screen number in the upper-left corner as green.  (That's #22.)  It being green means the AI Freezer is not active - which it would not be prior to going OUT.

Now at your video's 0:40, the pushback tug and one of the walkers have been frozen.  The FCDU screen number (#23) is red, indicating that one or more SimObjects are being frozen by us.

Because we don't know that a third-party pushback is underway, our AI Freezer is free to activate....

FSCaptain 1.8.3 will have an aircraft configuration value (named "OUT_Velocity") to indicate an aircraft's pushback speed.  I see that your pushback is being recorded at 2kts, so when you get you hands on 1.8.3, you can set your aircraft's value to 3kts or more... depending on how fast it can get.  Doing that will also keep your Block Time Clock from starting while you're under the OUT_Velocity speed.

BUT FOR NOW... if you check your options.cfg file and set USE_LIGHTS_TO_FREEZE_AI to "=1" then you can also control your AI Freeze Ray with your Taxi / Recognition / Landing lights.  Turn them all off, and the Freezer won't activate. (As long as we have an interface to your aircraft's lights.)

I see that your tug and walkers 'unfroze' once they weren't part of our "Protection Angle / Height / Zone" which also can be adjusted in your options.cfg file.

That reinforces my opinion that our Freezer is responsible.

Please let us know if you can manage to 'un-stick' your pushback crew with this suggestion.

If it doesn't work for you, I'll try to ping Bryan again to see if there's a way we can interface with UGCX.

Best regards,

[Travis]

If nothing I've mentioned helps, you can disable the Freezer completely (for all aircraft and all flights) by setting the option DISABLE_PROTECT=1.

Best,

[flyasa]

Feb 17, 2021 11:25:28 GMT -5 Travis said:

If nothing I've mentioned helps, you can disable the Freezer completely (for all aircraft and all flights) by setting the option DISABLE_PROTECT=1.

Best,

Ok I'll give that a try. Thank you for your help.

[flyasa]

Feb 17, 2021 11:25:28 GMT -5 Travis said:

If nothing I've mentioned helps, you can disable the Freezer completely (for all aircraft and all flights) by setting the option DISABLE_PROTECT=1.

Best,

that was the culprit. thank you

[Travis]

I will soon ping Bryan again to see if there's a way we can know UGCX is in play.

Until then, continue with this.

But if you want to try 1.8.3 Alpha 1 - hopefully within two weeks - you can adjust some settings and use UGCX while we protect you from rampaging AI aircraft.

Best,