October 4, 2025Oct 4 Hi all, just upgraded to MSFS 2024, so thought I’d do the same with my P2A. Got everything up and running ok but when I try to get IFR clearance all I get is a squawk code no SID routing or initial altitude like I would in V2, also no follow on frequency for next controller and if I try again all I get is good afternoon reply. I have no doubt it’s finger trouble on my part but I’m stumped how to get it working as per V2. Any help would be appreciated.
October 4, 2025Oct 4 Commercial Member There are some recognition issues we're working on right now to fix for the next update. In the meantime, try different forms of the request if it doesn't react correctly the first time. For example, if you're saying "<CallSign> ready to copy IFR Clearance" try just "<CallSIgn> ready to copy". This should all be much better in the next update. Dave
October 4, 2025Oct 4 Author Thanks for the quick reply I’m not using voice control but using the speak button as I did on V2.
October 4, 2025Oct 4 Commercial Member Yes, and the copilot/speak button is the one having the most problems. In most cases, selecting a different phrase for the same function works. Dave
October 4, 2025Oct 4 Author I selected one of the clearance options then pressed the ptt button and it worked for clearance however when switched to the next controller for pushback it reverted to the original problem, even using the ptt button got the good afternoon reply, nothing else, no matter what pushback phrase I chose. I think I will revert to V2 till I can see updates have solved the problem. Only problem with that is I’m using the trial version, so I’m assuming after the 10day period I will not be able to check if I’m still having problems, I obviously don’t want to pay the upgrade price only to find out I can’t get it to work. I’ll keep an eye open for any updates and check the program out again. Thanks again for your prompt responses.
October 4, 2025Oct 4 Commercial Member Hopefully we'll get the update out in a day or two. If the trial expires, send a note to [email protected] and I can give you another trial period if needed. Dave
October 13, 2025Oct 13 Hi all, sorry to ask but as I have the same problem I wonder about the timeline. Is 0.2.3C the mentioned update which should solve this or is that still ongoing? I'm asking for I still have this bug with 0.2.3C. I use V2 until clarification. Thanks for a short clarification, greetings from Germany, Alexander Edited October 13, 2025Oct 13 by koch44
October 13, 2025Oct 13 Commercial Member 0.2.4 is the update that should solve this and it should be out in a few days. Dave
Create an account or sign in to comment