Handling of XXX waypoints has been fixed in a recent beta (2-3 weeks ago).1. During oceanic ops, reports were made at or mentioning the waypoint "XXX", which isn't a real waypoint, but something PF3 adds, as far as I recall.
This happens at each waypoint and you had two only 14NM apart. With real OP they are where you cross meridians, so they are farther apart.2. I'm not sure about this, as I wasn't sitting in front of the computer for the whole flight, but I think some position reports were made twice, or at least with very little time in between.
Regular ATIS frequencies would not work, because of the distances involved.3. While in oceanic airspace, I couldn't ask for flight level changes, or the weather (ATIS) for KIAD. In my understanding, real pilots are able to do both.
I think (but haven't verified) aircraft can receive them in text form via their FMC (similar to the ACARS ATIS in PF3), but I don't think this is implemented in PF3.
I see the hotkey for requesting a lower altitude in the logs, but it seems PF3 ignored that. I filed a bug report for that in the beta forum.
No idea about that. I would suggest reporting it again if it happens when using the next release. I don't have a release date, but Dave already has many fixes and new things implemented since 3.3.04. At the exit point PRAWN, PF3 fell into a loop. If I remember correctly, my VC, who was handling ATC since receiving taxi instructions, got the instruction to contact Gander Center on 132.2. He confirmed, then - on the right frequency 132.2 - went ahead and contacted Gander Oceanic, who confirmed with SelCal and all, then immediately told us to contact Gander Center again, which is where the loop began. After 5 - 10 times of going back and forth, I took over ATC and tried a few things. What seems to have broken the loop is me issuing a position report on 132.2 (hotkey 9), and then making contact (0). After that, ATC seemed to be normal again, and my FO Travis resumed his ATC duties.
FL320 was your cruising alt before requesting a higher one. It seems that this wasn't communicated across the pond5. The flight was planned by SimBrief for FL320 initially. I changed the altitude of certain STAR waypoints in PF3, as well as the waypoints before and after, to reflect the constraints of the according charts (HYPER7), and to ensure a stable descent.
During the flight, when reaching 320, the FMC recommended 360, so I asked for and received that flight level (that was before the entry point NORVA). After a few hours, I wanted to step climb to 380 or 400, but PF3 didn't let me - see point 3 above. About around leaving oceanic airspace, my VC then started to amend his ATC calls with "out of FL360 for FL320".
I filed a bug report for this, too.
This could be a followup problem. I would recommend trying this again when the previous problem has been fixed.Nearing Dulles there were no descent orders from ATC. I also couldn't manually ask for them (Ctrl+Shft+L+8), there was no reaction from ATC. So I started to descend (albeit way too late and high for the constraints), which triggered ATC, who asked me to remain at 360. I received no further instructions like vectors or speeds, and I also couldn't ask for a runway, so we manually reported to Dulles Tower as soon as we were established on 01R, and from there on PF3 was almost back to normal.
Until then it is probably better to stick to the cruising altitude from the flight plan.
Your impressions were correct, thank you for reporting them in such detail.I have attached the logs. Again, I would like to request a second, non-encrypted set of logs, so I can verify or debunk the impressions I got during the flight, so as to bother you only with the real issues.
I have attached the decrypted debug log, so you can take a look, too. (Dave, please tell me if I should not do this in the future, but I think this detailed bug report earned him an exception)
