Hi Steve, No, I don't use trim function - only manually during set up procedure. As I said I only use the main & secondary buttons on FS2Crew.

When I select TOGA during GA the autopilot doesn't disengage so there is no binding issue there. I have just checked all my key bindings to see if any selections use 'M' (my secondary key) and the only one was for the 'Magneto'  I have just removed that binding but can't see how that would impact on autopilot. 

I have just taken off and pressed the 'M' button (secondary key) and autopilot stays engaged.

Edited December 21, 20214 yr by Glyn907

25 minutes ago, stevegreenspan said:

I'm using Voice Control so there is a difference there, no other hardware inputs from me other than pushing the throttles to TOGA manually and then back to LVR CLB.  I am using the Thrustmaster TCA pack as well.

The FO moves the flaps up one notch, from Full to Flaps 3.  

Do your hardware bindings for the GA and TOGA have any other flight control selections, such as trim?  

 

Steve

Steve, can you please try it in Button Control mode.

 

I tried the same approach using Button Control.  I'm a Voice Control guy, so I am a bit rusty in using Button, but was successful for the entire flight  

On approach I went to GA using the mapped secondary key and it followed the GA procedure to start the level off and then climb at TOGA.  AP stayed on.  However flaps stayed at Full, expected the FO to move to Flaps 3 .  

 

 

1 hour ago, stevegreenspan said:

I tried the same approach using Button Control.  I'm a Voice Control guy, so I am a bit rusty in using Button, but was successful for the entire flight  

On approach I went to GA using the mapped secondary key and it followed the GA procedure to start the level off and then climb at TOGA.  AP stayed on.  However flaps stayed at Full, expected the FO to move to Flaps 3 .  

 

 

Did you hear: "Go Around Flaps"?

Are you using Hardware for the flaps?  Hardware will override any flap signals FS2Crew sends.

I heard the FO speak at the initiation of the GA although the higher engine noise on my speakers drowns him out, so not sure what was said, assuming the start of the GA process.  In any event the Go Around followed the steps above successfully although I had to manually retract the flaps in stages through the sim itself and not on my hardware.

I do have hardware for flaps, the Thrustmaster TCA quadrant and addons.  However they are not used for the A320NX since the FO controls flaps on my command using Voice Control.  I did not disable them in the settings for Button Control since I was not aware that I may have had to do that, hence the reason there may have been a hardware conflict and no flap retraction.

My testing and results using Button Control show that in my configuration, the AP and AT remain on during the Go Around process.

 

Steve

 

Steve/Bryan, that's interesting then and it looks like something in my setup is causing the autopilot to disengage. Appreciate you checking the process out. 

As I previously said, I have checked no key bindings affecting my secondary assigned button and as you can see in my video as soon as I press the secondary button to GA the autopilot disengages. If i dont use FS2Crew autopilot doesn't disengage. Hopefully someone using FS2Crew in button mode can offer an explanation. Thanks for helping though.

I am going to try again using the non-beta version to see if it makes any difference.

 

Edited December 22, 20214 yr by Glyn907

Glyn,

Can you try using a different secondary key mapping to see if the issue follows to the new key. I think you mentioned that you use "M" now for secondary.  See if we can isolate this....

Steve

 

Steve, You must have read my mind as I have just done that  - before seeing this post🙂 It made no difference at all as did reverting to pre-beta FS2Crew. Stumped!!!

Would you be able to provide a video showing your GA with button control to make sure I am doing everything correctly? That would be really helpful

Edited December 22, 20214 yr by Glyn907

I will see what I can do.  I haven't created or posted videos, typically only screenshots.

Steve

That would be a real help if you could. I think I must be doing something wrong so would like to check the full button GA process

Bryan, Is there any way to log the FS2Crew events as I execute the button control GA?

We do have a log.

Look in the INFO CENTER section pls.

 

Thanks Bryan, Looked for log but can't find any for last couple of days

Please look at the Log after triggering the go around.  The log updates live in game.

Glyn and Bryan,

Happy Holidays to you both....

After a couple of attempts to find the issue for the AP1 turning off at Go Around, I finally got it to fail, and confirm that there is something going on, possibly in my procedures or possibly in the A320NX itself.

Again, I use Voice Control primarily for my flights and never Button Control, so I had to reintroduce myself to Button with a few practice flights.  I was able to figure out how to record videos, but my results were sort of blurry, so apologies.

What's interesting in the video is that upon engaging Go Around with the secondary button, I heard Manual Flight called out and the AP1 turned off.  I did not press to disconnect.

(Continued next post...)

 

 

Edited December 25, 20214 yr by stevegreenspan