Hi Bryan,
there seems to be a glitch in the latest beta and the previous one:

FBW A32NX Developer
FS2Crew latest Public Beta 4 (2.0.0.45 - dated 9.11.)  ... Button Control

Descent Checklist ... OK
Flaps 1 ... OK
Flaps 2 ... OK
Gear down ... OK
Flaps 3 ... OK
Flaps 4 ... OK

BUT: then I triggered the "Landing Checklist" ... the F/O calles GoAround - Gear Up -Flaps 1

I tried three flights recently (yesterday and today) always the same problem.
Didn't have the problem before, FS2Crew worked in Botton Control fine for me!

15 minutes ago, Rene Billiani said:

Hi Bryan,
there seems to be a glitch in the latest beta and the previous one:

FBW A32NX Developer
FS2Crew latest Public Beta 4 (2.0.0.45 - dated 9.11.)  ... Button Control

Descent Checklist ... OK
Flaps 1 ... OK
Flaps 2 ... OK
Gear down ... OK
Flaps 3 ... OK
Flaps 4 ... OK

BUT: then I triggered the "Landing Checklist" ... the F/O calles GoAround - Gear Up -Flaps 1

I tried three flights recently (yesterday and today) always the same problem.
Didn't have the problem before, FS2Crew worked in Botton Control fine for me!

I just tried to reproduce it.  No problems on my side.

The "Go around" call can be triggered by pressing the Secondary Button in Button Control.

Make sure the Secondary and Main button are not sharing the same keyboard/joystick assignment.

Also ensure your throttles are not in the TOGA detent.

 

Thanks for your fast reply, I will check the button config next time!

You were right, the secondary button was assigned, not the first ... sorry!

3 hours ago, Rene Billiani said:

You were right, the secondary button was assigned, not the first ... sorry!

No worries, it happens to best of us 😉

I have just performed a Go Around by pressing the secondary button I set (not same as main button) and then went to TOGA and the autopilot disengaged.  It is supposed to stay activated during Go Around. I also tried Go Around without FS2Crew and everything worked correctly ie autopilot stayed engaged. Am I doing something wrong?    

Edited December 19, 20214 yr by Glyn907

That's aircraft behavior not FS2Crew.

In the Scarebus, if 1 autopilot is on, it will disengage when you go around.

That's why it's a good idea to have both autopilots on during the approach, so you'll have at least 1 autopilot for the Go around.

Thanks but as I said autopilot disengaging only happens when FS2Crew open and GA selected.  Under normal circumstances the autopilot is supposed to remain on in Go Around, which it does without FS2Crew. Autopilot remains engaged without FS2Crew - as it should. I have a video of what happens if that is any help

31 minutes ago, Glyn907 said:

Thanks but as I said autopilot disengaging only happens when FS2Crew open and GA selected.  Under normal circumstances the autopilot is supposed to remain on in Go Around, which it does without FS2Crew. Autopilot remains engaged without FS2Crew - as it should. I have a video of what happens if that is any help

FS2Crew doesn't send any commands to the autopilot when you engage go around mode.

Make sure you have both autopilots on.. both channels.

It's Airbus logic for 1 autopilot to drop when GA triggered.

Edited December 19, 20214 yr by byork

Can I PM you as don't want to take up this thread discussing this? 🙂

 

You can send a support ticket via: www.fs2crew.com

Cheers,

 

I want to send you 2 videos if that is ok. If OK how do I send them?

6 minutes ago, Glyn907 said:

I want to send you 2 videos if that is ok. If OK how do I send them?

Upload them to Youtube.

But do you have both autopilots engaged when triggering the go around?  Or do you just have 1 autopilot on?

 

Easyjetsimpilot - Go Around Video     FS2Crew Go Around video example 

According to the A32NX FBW experts (Easyjetsimpilot) only AP1 required for Go Around & autopilot stays engaged throughout. No requirement to have both engaged unless performing autoland. See attached videos. Support Ticket raised with reference to this page.

Edited December 19, 20214 yr by Glyn907

Those videos are set to private.

FS2Crew is not turning off the autopilot when you go around.  

Please try it again without using FS2Crew.

But I'm pretty sure one when you go engage go around mode in an A320, one autopilot automatically drops out.

That's why you'd engage both autopilots even for a CAT I so you have an autopilot in case of a GA.

I have a TR in the A320 (real world, many years ago, but my memory is very rusty), and that's what they taught us.  But there a lot of equipment options in the Airbus, so maybe it can vary.

 

Maybe someone else can chime in.