DrSoftware

With XPlane 12.4.0, I experience instability (i.e. xplane hang that requires restart) when P2A_XPLink is installed. I can reliably reproduce the issue with starting cold & dark with toLiss A320 neo airplane model.

Another example: On BRIXX4 arrival to KSJC between CORKK and BRIXX. BRIXX has a hard altitude of 12,000 ft and a hard speed of 250K. Yet, ATC says "maintain 17000 feet" (needless to say I was already well on my way down to 12,000)

Update: cold & dark start seems to affect the ATIS. Today I connected P2ATC with the radios fully powered up and the ATIS started right away.

In a recent flight with P2ATC 0.2.7A and X-Plane I went missed because I was set up to land on one runway and I was cleared for the approach on another. (hmmm.... maybe ATC could have said something?) Somewhere along the line while trying not to crash I forgot to communicate what I was doing (aviate, navigate, communicate!). Ultimately, I came back around and landed on a parallel runway without clearance. I was unable at that point to get P2ATC to respond to me, such as reporting clear of runway, requesting taxi to parking/gate, etc. And I even had the copilot make these calls for me in its well-formatted syntax. Yes, I know I landed without clearance, but does that give P2ATC the right to ghost me? Seems that if I miss a critical handoff, and then get back to it later, P2ATC is still thinking I am back were I was 15-30+ minutes ago, and does not react to the current situation,e.g. on the runway or taxiway or at the ramp. At least it should respond and call out a possible pilot deviation for landing without clearance, etc... Also, I find it hard to get to get ATIS once P2ATC is started. With the xplane ATC on, I get atis as soon as I hit the atis frequency. With P2ATC atis, I have to switch back and forth to other frequencies and then finally back to ATIS before the ATIS broadcast starts. Seems to me that when P2ATC connects, it should look at the radio settings and if ATIS is up, it should start the ATIS immediately. Also, on a recent landing I turned the wrong way off the runway. I got my taxi clearance, but had to turn around and go back the other way. P2ATC couldn't really tell that I was on the wrong side of the runway, wouldn't give me permission to cross the runway again (and basically ghosted me again)

Using X-Plane 12.3.3 and AIRAC 2513 with 0.2.7A PIlotATC FMS plan generated from Simbrief is: I 1100 Version CYCLE 2513 ADEP KMFR DEPRWY RW14 SID JKSN1 ADES KSEA DESRWY RW16R STAR HAWKZ8 STARTRANS BTG NUMENR 6 1 KMFR ADEP 1335.000000 42.374964 -122.873289 3 OED DRCT 17000.000000 42.479575 -122.912933 11 CUTTR V595 17000.000000 42.689275 -122.728519 11 RENAA DRCT 33000.000000 43.441561 -122.411128 3 BTG DRCT 34000.000000 45.747811 -122.591536 1 KSEA ADES 2900.000000 47.449889 -122.311778 Actual Kawkz approach: https://www.1800wxbrief.com/Website/aip/tpp/00582HAWKZ.pdf https://www.1800wxbrief.com/Website/aip/tpp/00582HAWKZ_C.pdf Actual target altitude assignments on import of the .fms file: R14: 1335 alt 1800:2100 int: 4000 OED: 7200 CUTTR: 17999 (show alt restrictions between 10500-17999; in reality it is MEA 10500 northbound, but the limit of 17999 appears to be because it is a waypoint on IFR low charts; IMO there should be no upper restriction here; note LNM also shows this restriction.)(?) RENAA: FL 340 BTG: FL 340 PTERA: FL340 TOD: FL 340 KRIEG: 6000 (MEA is 10000) HAWKZ: 6000 (crossing restriction is A12000) LIINE: 6000 PIKEZ: 15000 (A12000/B15000) COFAY: 6000 BREVE: 11000 (A10000/B11000) NETTZ: 6000 (A8000) KWEST: 6000 (A7000) VASHN: 6000 (6000 hard) KSEA: 432 The database seems to have the crossing altitude restrictions right, but P2ATC seems to only respect the Below constraints (if started out above, it will go to at least the below constraint). If there is no constraint, it seems to pick the hard altitude at the end of the arrival. (In reality wouldn't the restriction on COFAY be A(min(prev.waypt,next.waypt))/B(max(prev.waypt,next.waypt)) ? Above constraints aren't respected at all, and it doesn't seem to interpolate the target altitude for a straight line distance between the two waypoints which is what I would expect. I can't seem to override the target altitudes. When I do, it just goes and lighlights the "alt" line above. How can I fix P2ATC to get a better descent profile?

I don't quite understand. The top trip on the upper right of the UI, not sure what it is called reads: CALLSIGN ALTIMETER SQUAWK CODE ASSIGNED CTLR ASSIGNED ALT Lynch Air 5019 29.97 5665 Detroit Approach 124.050 8000 The next line ALTIMETER DESTINATION APPROACH 29.97 KDTW ILS-Z - RW22R - VALLI So if I am cleared for the approach, why does the top line still show an assigned altitude? Should that box not be cleared?

Got it. Replaying the scenario I got the "..turn to heading xxx to intercept course" version.

Version: P2ATC v3 0.2.7A On departure, after receiving a heading to follow, the heading restriction is never cleared. I expect "proceed to <FIX>" or "resume own naviation" or something like that. Instead, ATC just assumes I'm going to decide to self-navigate on my own.

Version: P2ATC v3 0.2.7A When ATC gives an approach clearance, the UI is not updated to remove the altitude restriction.