bobsleigh44

I've discovered that it's the RSG G500 that is the issue. As soon as I disable the G500 plugin, the course OBS button works again. I've submitted a ticket to X-Aviation.

Did you ever manage to solve this? What aircraft are you using? I’m having the same problem on m my Twin Comanche

I found a fix for this today, switch your units in your settings from 'hybrid' to 'US'. For some reason Asobo's really mucked up their Km/h to knots calculation. Once you put it back to US Imperial, the wind speed you set (in knots) will be what you actually get. Also, the wind speed doubles once you get above 1000 AGL, which I gather from other forum posts as Asobo's simulation of ground friction on reducing wind speed (which apparently isn't particularly accurate?).

@Dave-Pilot2ATC This time I flew from Iceland to Heathrow, the same issue happened even without the use of time compression. The only thing in common each time has been the Manchester Center ATC. Each time P2A just seems to stop working right after the STAR is assigned by Manchester Center, at which point the yellow 'suggested text' for the automatic co-pilot readback appears, the voice is heard, but no green 'recognised' text appears for the co-pilot readback. At this point, pretty much every request to Manchester ATC stops working, and Manchester ATC does not give any further instructions as far as I remember. A re-connection and re-filing of flight plan fixes this (i.e. by saying 'without you at flight level XXX'), but it seems like a bit of an inelegant 'fix'... Is it possible that something is just specifically wrong with Manchester Center ATC? I know it sounds a bit strange since in theory all the ATC is based on the same code, but what do you think?

Hi Dave. I just reflew the same STAR and approach this time but from Paris CDG (so I didn't use time compression). This time, ATC continued to work. I also use Amazon Polly voices - perhaps during time compression the communications were so quick, added with the latency from an internet voice (to the point that they were cutting each other short) that the ATC code just went a bit haywire?

Hi Dave. Sorry, I actually meant that this behavior occured at around the top of descent point, so it's definitely within the range of Heathrow Radar Controller (which I presume is what they call their approach). It just seems to suddenly go 'lame' at roughly the time the STAR is issued, at which point you can no longer talk to ATC and they don't give you any vectors to final approach (even though it was selected in the approach box and approach assignments are turned off). Is it possible to attach any P2A log files or something for you to have a look?

ATC just stops responding to any request except for 'radio check'. Although the audio of the co-pilot is when pressing 'say it', the words don't repeat in green. This happened every time I did a flight from KFJK to EGLL. I used time compression / ground speed compression. Could this be the cause of it? Because it's getting a bit strange now that every time this route ATC just stops working completely. @Dave-Pilot2ATC

@Dave-Pilot2ATC Hi Dave, is the behavior in the picture below meant to be correct? STAR is BED1H, RW27R, BEDEK Transition, approach transition is OCK. On the Zibomod ND, the path is correct. The line is also correct on Navigraph Charts. But on P2A, it appears that the OCK 7nm radial waypoint is drawn in the wrong place (straight north). P2A: https://drive.google.com/file/d/1ElS48Rk-kyznvSk7jWluHcNkzQ_Fq1pd/view?usp=sharing Navigraph Charts: https://drive.google.com/file/d/1KsIi5O8OJPqaunH-0XRu7-Y_FJH5o28U/view?usp=sharing 737 ND: https://drive.google.com/file/d/16HAR7ov9Fv7KnX_Fq87-3WlO2gUYTCCM/view?usp=sharing Thanks again Dave.

Understood. Thanks a lot Dave.

I think I'm having similar issues, but it's even weirder: Polly works generally but NEVER when it comes to IFR Clearance and the readback. God knows what's going on...

Has anyone had issues with Polly processing longer sentences like Clearance delivery? It's really odd because every other bit seems to work, it's just clearance delivery which fails to TTS.

@Dave-Pilot2ATC thanks for replying. Just a point of clarification: On the JFK VOR part of what you said, are you saying that Pilot2ATC's data says that, after the pilot performs the e.g. Canarsie climb himself, he will be given vectors for JFK VOR and then direct to MERIT? I'm just a bit confused about this part because from my understanding of the SID charts for the MERIT or KENNEDY departure, we are not supposed to fly to JFK VOR, but rather the procedure is: e.g. 31R Canarsie climb, then radar vectors to MERIT (without first going to JFK VOR) then PUT then as filed. Currently, Pilot2ATC says something like KJFK 31R then JFK VOR then MERIT. Thanks again!

@Dave-Pilot2ATC

I'm not sure if I'm doing something wrong, but for some reason when I choose e.g. the MERIT departure from KJFK (MERIT 6, RW31L, PUT), Pilot2ATC puts in the JFK VOR as a waypoint, then to MERIT. By contrast. the charts say turn left before R039 of CRI and climb via Breezy Point / Canarsie - with no relevant mention of JFK VOR). So when I flew the takeoff, I think the whole thing wasn't working right since I didn't get any takeoff heading or vectors at all, resulting in me just flying the Breezy Point climb myself with no directions from ATC. Can someone please help? Thanks a lot!