February 15Feb 15 I've conducted numerous commercial IFR flights using P2A V3.0.0 EA in X-Plane. I also performed these flights in parallel using P2A V2.7.0.3. I was unable to complete any of the flights in P2A V3 successfully because the connection to the controller was repeatedly lost, even though the aircraft's position was displayed correctly in P2A at all times. I suspect that the new IP connection to X-Plane 12 is unreliable. This makes flying with P2A V3 anything but enjoyable. For example, you can attempt a short flight from LEBL to LEPA. You will not be able to complete it successfully. At the latest, halfway through the short flight, the controller stops responding, or the automatic frequency change by the copilot during handover simply doesn't occur. It's frustrating. Detlef Fenske
February 23Feb 23 Author Another flight from EDDN to EDDW is driving me to sheer despair. The utterly incompetent controller doesn't recognize the TOD and keeps trying to send me back to cruising altitude after I, in desperation, initiated a descent on my own to avoid missing the airport. Despite this, I'm eventually assigned an approach procedure for no apparent reason. I want to emphasize that this happens on almost every flight. There seems to be virtually no support. I'm done with P2ATC V3 for now. Have fun with a completely unfinished product. Detlef Fenske
Create an account or sign in to comment