Hello,

I normally fly in VR. So when I am ready to request clearance to copy an IFR flight plan, I am in the cockpit in 3D - TBM 930 - and without an easy connection to the rest of the desktop. When Clearance gives me the squawk code I enter it on the MFD and it shows there. But P2A doesn't see the transponder as active, so every radio contact starts with a request to Squawk XXXX. I have to leave MSFS minimized to get a mouse that will let me go into P2A and make the transponder active. From that point on, it works fine.

I am trying to load P2A again to describe more detail and it says that another instance of the program is still running. Task manager doesn't show it. MSFS crashed with one of it's CTDs and seems to have affected P2A as well. I'll reboot and try again....

EDIT: OK, I rebooted and started anew. When P2A gives me instructions, I enter the squawk code into the MFD and press enter. It shows on the P2A screen, but then in the plane I can choose from Standby, Altitude, or Ident. None of them do anything. P2A shows the code but Mode shows Off. Nothing that I do in the plane turns it on until I leave MSFS and use the XPDR settings in P2A. From then on all is well.

IS ANYONE ELSE HAVING THIS PROBLEM????

 

Edited March 3, 20215 yr by Quijote

This may be an MSFS SimConnect issue which is causing FSUIPC to be unable to sense changes in the aircraft XPDR Mode.

This does happen in some aircraft in other SIMs that have non-standard transponder implementations, so it might be worth checking other aircraft to see if they have the same problem.  If so, then it is likely the MSFS problem.

Also, you might report it to the FSUIPC team so they can add it to their list of items they're working with Assobo on to get fixed.

Dave

I am sure you just need to click on the Mode to change it, from off to standby to active. I had the same issue when I started off until I realised that changing the Transponder mode in the A/c did not affect the MFD. You need to change it manually by clicking on the Mode button.

I went back and tried again in the TBM930. I very carefully set the XPDR that P2A gave me and tried all three of the options - standby, on, and alt. None affected what was seen by P2A. P2A correctly received the code itself, but the mode didn't change, leaving the XPDR in P2A off. If I leave MSFS and click Mode in P2A I can set it and all is well, but cannot do it from within the plane (VR). Ident also has no effect. I will try this in other planes because the TBM G3000 system is modded by the WorkingTitle mod and it may be their problem as well.

OK, I loaded the DA62 with the WorkingTitle G1000 mod. Loaded FSUIPC7 and then P2A. I entered a flight plan and submitted it to ATC. I received the squawk code and entered it on the PFD. It showed up on P2A, but no combination of On, Stby, Alt, or Ident could change the P2A mode setting of Off.

So I removed the G1000 mod and restarted using the plain Asobo DA62. Same story. So I am no longer blaming Working Title at least.

Edited March 5, 20215 yr by Quijote

P2A does not use Ident, so there won't be any affect there.

As a workaround, you can set P2A's XPDR to Active when you connect and then not worry about it since the plane's mode change doesn't affect P2A.

I suspect this will be the case for all MSFS planes.

Dave