Kimp1lot

Oh, it's the payware version since autosaves are not available on the free one as far as I know.

I can give you an autosave with a default aircraft so you can try to reproduce and spare 35 euros ahah. However, I always reloaded with the FSLabs and never with a default aircraft.

It just makes the sim freeze and crash. No error on screen.

One could argue the use of softmuting in flight of course, but still makes the sim crash and iit's reproducible so should be an easy fix if it's not just me 😄

Hello,

Whenever I load an FSUIPC autosave, if I press the key assigned to "Sync propeller (on/off)", my sim crashes.
Reproducible 100% of the time.

Fair enough.

Just one question : what would happen if the update is released while I'm flying ? Will I be able to use UGCX until my next sim restart ?

So I take that the update is still mandatory ?

Devs do weird things with their AFCAD, I swear...

14 hours ago, byork said:

1.4 will be out soon.

Will it be a mandatory update ? I will most likely update but in case there is a big bug preventing to use the version I would like to stay on 1.3 rather than using Shift+P or GSX.

Yes exactly ! It could apply for all other steps in the procedure but I didn't notice anything with the other steps, seems fair.

I only noticed the pin disconnect because, flying the A320, we have an ECAM message to testify that the pin is inserted. It disappears instantly after saying "brakes set" 😛

2 hours ago, Manuel82 said:

Hey,

Initiallly it was intented for be a fast pushback procedure, because it varies in each country. However, there are some places were the ground crew waits for the engine startup finishes after pushing back prior to disconnecting the pin then the towbar. I don't know if the ramp agent asks the crew when they finish engine startup, which this delays the disconnect procedure.

Cheers,

Manuel

I understand, it's not really about the procedure itself, it's just that when I say "parking brake" set, less than 1 sec after the pin is removed, feels very robotic and not human. I would assume that it would at least take randomly few secs for the reaction time ?

Yes sorry, I meant when you say "parking brake set" the pin is instantly removed.

Hello,

So far, when you tell to the ground crew to disconnect, the pin is instantly disconnected. There is no random delay.

Is it intended ? I guess they're pretty quick IRL to remove it but they'll surely take at least few secs ?

Btw Manuel I don't know if you understood but I meant :

On 10/29/2019 at 4:07 PM, Kimp1lot said:

Yes you are correct actually, although what I would like to do is the following :

- Request the Pushback sequence
- User defined pushback route
*Ground connects*
Hello, parking brake set.
- After ground is connected, create the pushback route I want whenever I want to
- Say that I'm ready for push.
Brakes released. Starting push.

Currently, we select the route before !

"Whenever I want to" would be the missing part, because being forced to chose my route after TUG is connected with an unclosable window would not fix the issue 😄

Thanks for looking into it, no hurries - would be a really nice addition tho !

Alex.

Yes you are correct actually, although what I would like to do is the following :

- Request the Pushback sequence
- User defined pushback route
*Ground connects*
Hello, parking brake set.
- After ground is connected, create the pushback route I want.
- Say that I'm ready for push.
Brakes released. Starting push.

Currently, we select the route before !

@Manuel82 Sorry I don't want to hijack the thread but it's about custom routes. Did you consider giving the possibility to chose a custom route "on the fly" in v1.4 after the ground crew connects tug and everything ? I reported somewhere else but I don't find the thread anymore so I don't remember your answer.

As I said, it would be more realistic for those flying online as sometimes you can be given an unexpected push due to traffic etc.

Hello,

I think you fixed the fact that UGCX was listening in the air. I think you could go further.

Currently, UGCX listens (as in looks for voice commands) when you trigger a sequence and until the end of it (until everything disappears).

Could you make it listen only when the ground crew is connected to the interphone system ? So for instance, when he disconnects and waves with the pin or walks away in the tug, it wouldn't listen anymore (which is currently the case - making UGCX say "go ahead cockpit") ?

Thanks!

5 hours ago, alfy said:

I disagee it's part of your ckeck list the ground crew ask if brakes released

So IRL if somehow the brakes are not released when the tug tries to push the plane flips around ? 🙂

@byork Ticket "7PY-S4H-XH73". Could I have the very last 1.3 where there is no stutter upon landing or should I raise another ticket ? Manuel said that I have the wrong 1.3 apparently 😄

Not yet fernandito, we are waiting 😄

Maybe only when the menu is called ? Anyway, if it's fixed (hopefully it is because as you know we mainly fly to land and if it freezes upon landing it's a no-go for me) it's ok.

Hope it's soon released!

Roger, I received the beta 09th of October 0421z so I guess I don't have the correct one!

Although why does it have to load things ? GSX does not as far as I know for example.

I tried the 1.3 beta and the stutter on landing is still here, less than before supposedly, but still here.

Any chance you can stop making your software load things when he's not required ? A on/off button would be great, as suggested somewhere else.

Ok then I sent you a ticket @byork

I don't want to go back to GSX 😞

@byork Thanks, although according to your yesterday's post the update should be out in 3 hours max now so I will wait

Cool thanks ! 🙂

Yep, was just saying ; although, it's already at 4.

I don't have stutters after landing, I only have a pause near/upon touchdown. Will see if v1.3 fixes.

I already have this to 0 and still have the stutter upon landing.