hello

found a couple of bugs on the fenix:

1-FO doesnt recognise seatbelts signs switch position during CHK reading (thinks its off when its on)

2-when giving'wipers on' order it also triggers GPWS test

also if i asked for 'BIRD ON' the FO replies but does nothing

during taxi flow fo sets autobrake to MED instead of MAX 

whenever i remember or identify a new bug ill post it here

On 1/14/2025 at 2:09 PM, ayousry said:

hello

found a couple of bugs on the fenix:

1-FO doesnt recognise seatbelts signs switch position during CHK reading (thinks its off when its on)

2-when giving'wipers on' order it also triggers GPWS test

Thanks.

This switch is very labour intensive, with so many airbuses supported, some with off-auto-on (3 position switch), others with just off-on and some changing from one version of the aircraft to another depending on which model it was based.

In this case, the FO was reading '1' and thought it was in "Auto" (he was expecting '2'.

Now that you reported it, it will be easy to fix for this specific plane.........until it eventually breaks 🙂

I swear I heard the trigger for the GPS on the first command when the plane just started. This was a one off and couldn't replicate.

In fact, ASOBO has some little documented generic triggers for things like GPWS test.

With Fenix, we aren't calling those and instead manipulate the Fenix custom Lvar for this item. What the plane does beyond that we have no control over.

If it keeps happening often, let us know. 

Patch for this and other items will come out tomorrow evening UK time

 

thanks 

can you have a look on those too pls?

 

1- if i asked for 'BIRD ON' the FO replies but does nothing

2-during taxi flow fo sets autobrake to MED instead of MAX 

Edited January 22, 20251 yr by ayousry

7 hours ago, ayousry said:

2-during taxi flow fo sets autobrake to MED instead of MAX 

Mine no longer sets anything at that call

@ayousry & crab

Please get the latest patch and manually replace all files (V3.1.15). Thanks

 

On 1/14/2025 at 2:09 PM, ayousry said:

2-when giving'wipers on' order it also triggers GPWS test

Apologies for this one.

It was caused by SImco64_Ldr.exe

Please re-download the patch.

On the bright side, should have FsLabs A321 external lights as well as some EFIS buttons responding to commands.

 

many thanks

i get flow cancel or flow on hold a lot , what triggers this behaviour?

15 hours ago, ayousry said:

many thanks

i get flow cancel or flow on hold a lot , what triggers this behaviour?

There should be only 2 reasons for this to happen.

Either a detected "pause flow", "suspend flow", "cancel" flow"

A "Pause" command inserted into a flow where the option "Wait until I tell to continue" is ticked. In that case, when Fo executes te flow and gets to that line, he'll notify that it is suspended and wait until you say

resume the flow

resume flow

carry on with the flow

continue the flow

....a few other speech variations.

Now, if this started happening recently without you having made new flows, it could be because you relocated your PC to a different rom with completely different ambient noise conditions, or swapped headset.

The speech profile will then become inadequate and perhaps picks up those short commands "pause flow" by accident.

In that case, I suggest you create a brand new speech profile via Windows Control Panel, <speech recognition> applet, make it active, calibrate the mike then train it from scratch using our aviation jargon speech trainer.

Windows Start->Multi Crew Experience->Speech training.