So far I only know that this happens with FlightFactor 777. It has been bugging me for ages, and thought it was a stray controller binding... But I have discovered it's P2A.

Even with CO-PILOT SETS XPDR "OFF", the co-pilot keeps switching the FF777 to XPNDR even when switching it to TA/RA... it just springs back to XPNDR again!!!

Please could this be fixed. Thank you.

Is this co-pilot even qualified and fit for the job? Or is he maybe just stubborn, or deaf?

If it only happens with the one aircraft, it sounds like it could be the value the FF 777 sets that data reference to when you set the mode to TA/RA.  There was an issue in an earlier version with the mode not being set correctly, but this should be fixed in version 0.2.6.

P2A interacts with the XPDR based on what SIM you are using and displays the XPDR mode based on the value of that data reference/offset.  If you have the Copilot Sets XPDR option turned off, then P2A will not be changing the transponder mode or code for you.

Dave 

On 11/24/2025 at 2:25 PM, Dave-Pilot2ATC said:

If it only happens with the one aircraft, it sounds like it could be the value the FF 777 sets that data reference to when you set the mode to TA/RA.  There was an issue in an earlier version with the mode not being set correctly, but this should be fixed in version 0.2.6.

P2A interacts with the XPDR based on what SIM you are using and displays the XPDR mode based on the value of that data reference/offset.  If you have the Copilot Sets XPDR option turned off, then P2A will not be changing the transponder mode or code for you.

Dave 

Well P2A is definitely doing it. I tested. I set transponder to TARA with P2A disconnected, and it's fine. As soon as I connect P2A, it is switched to XPDR, and will not let me set it to TARA.

Seems to have been sorted...