HI @Dave-Pilot2ATC,

testing 0.23 I found some bugs :

- with Fenix a320 in msfs the comms are little bit messy. It used to work with 0.15B as far as remember and fsuipc 7.5.2 ou maybe 7.5.3. When I connect the standby comm on Fenix 1 is not the same as in P2A : pin Fenix active atis stdy ? And in P2a atis and del. When swapping in fenix del appears in Fenix rmp and in active in P2a but del stay in stby so. It’s like P2A reflects Fenix freq in active but not really tuned to this one and keep stby as previously. Even with del “printed” in P2a active atc doesn’t understand. (2 pictures (24 and 25) and the log in the link below). I am not sure to be clear 🙂 it seems to interact but only on a visual way

- freeze when request taxi as already said 🙂

- atc report an error when copilot redadback a freq like 121.775. Copilot says : one two one decimal seven seven. Atc says : negative frequency is 121.775. Copilot doesn’t say five but it used to be ok (picture 28)

Pictures and log

 

Edited September 22, 2025Sep 22 by watin

The Taxi freeze and another issue with taxi requests is now fixed in 0.2.3A.

I'll check on the readback being considered incorrect when the 5 is left off.  That should be accepted.

Not sure why the standby frequency display is bad.  Are you changing frequencies in the cockpit or in P2A?

Dave

Forgot to ask you.  Did you try changing aircraft to a standard SIM aircraft to see if the frequency display was normal?  It could be an issue with how the Fenix interacts with external programs.  Maybe a setting in the aircraft to allow external interaction needs to be enabled.

Dave

I’ll will Check that

Well it works with a msfs genuine aircraft. So something has changed with the Fenix as it used to work…