December 3, 20214 yr Hi Dave i did a flight today from EGCN to EGCC i could request the IFR clearance and get the response i then used the copilot to repeat back atc then gave me the barrow and to tell them when i am ready to taxi again copilot responds when i say i am ready to taxi i get no response i used say it and still no response i all so asked for a radio check using say it and still no response i restarted P2A 3 times and got the same result every time all with different voices i have emailed all 3 logs to you i am on version 2.6.2.3_x64_r2 and Navigraph AIRAC cycle 2112
December 3, 20214 yr Commercial Member It sounds like it was working at other airports, is that correct? If so, what changed? It looks like something may be wrong with your call sign. When you call for clearance, you use Eight One Eight Niner Four and it works. the other times, you are using pip 8 9 4. I would try changing the call sign to something else, like the default GA call sign with Beech in the Mfg box and a valid tail number. If that doesn't work, try it from other airports. Also, you could try installing the Public Beta 2b that fixes quite a few bugs. Perhaps you're hitting one of them. Dave
December 3, 20214 yr Author thanks will try the beta and call sign have used p2a a lot from the airport with no problems in the past what was getting me was no reply when using say it tho i could hear the co pilot ask the question
December 3, 20214 yr Commercial Member I suspect that it is the Call Sign since the long version of it worked and when using the pip version, it did not. Let us know what happens. Dave
December 3, 20214 yr Author i up dated to the beta 2b and changed the call sign to Arrow 581 i still had some problems asking for taxi took ages to respond but it did near the end of the flight it stopped responding again after a few minuets i got an error message grammer had timed out clicking ok and p2a came back to lift and told me to descend to 2000 feet via the NQY1 transition but after that it never spoke again and on trying to shut it down after the flight i just got not responding i have sent the log file my ram usage was at 50% when it stopped responding according to task manager i have 32 gig of 3600 memory
December 3, 20214 yr Commercial Member I see the Speech Engine Error in the log file. I suspect the program just couldn't recover after that. The dialogs that played after that error seem to have been already queued up. I didn't find any more Speech Recognition after that. But, looks like changing the call sign fixed the problem. You should be good on your next flight. Dave
December 4, 20214 yr Author hi dave tried a new flight this morning first attempt p2a did not respond to me talking so a restart 2nd time it worked until handed off to the tower then stopped responding again to me and to say it i have sent you both logs on a side not when i got to shut p2a down on the beta its taking a couple of minutes to close and says not responding on top
Archived
This topic is now archived and is closed to further replies.