I've made several flights now (MSFS 2020) and each time I keep getting incomplete clearances without routing. For example, tonight I had filed KDEN SABTH2 VRONI DCT PNH J17 ABI DCT DILLO LAIKS2 KAUS. The clearance I received was as follows:
United 370 is cleared to KAUS fly runway heading climb and maintain 9 thousand expect flight level 370 10 minutes after departure squawk 2146 contact departure on 136.6
I can easily add '...as filed...' immediately after the destination readout. I seem to remember that word was dropped when we introduced the departure name (or phonetic readout of it).
United 370 cleared to KAUS as filed
, fly runway heading...
I'll add it to the next hotfix
I couldn't set up anything the FMGC since I wasn't actually cleared for the SID, nor was it clear where I could expect to resume own navigation.
You didn't have SID or STAR turned on
1/12/2021 4:12:58 PM: 800 - SID Feature is OFF
1/12/2021 4:12:58 PM: 800 - STAR Feature is OFF
In the United States, clearances are generally issued in the following order: Clearance limit, Altitude, Route, departure Frequency, Transponder code. Many pilots expect to copy clearances using the acronym CRAFT. It would be great to get PF3 to adhere to that custom for flights in the U.S. (which would entail issuing the departure frequency before the squawk code).
Not a problem, I'll change that for the next hotfix
Overall, this was not a good performance from PF3. After receiving radar vectors on the departure, I was finally cleared direct to TIKLR and resume own navigation--except that I had either already passed it or I was so close that in the time that it took me to find it and get it loaded into the FMGC,
Your first three waypoints for this flight were actually all too close together... you would have been given a friendly warning (Notam) about this but chose to ignore it
Coming into Austin (and this has been typical as well), I was never advised on the approach that I could expect, nor was I given a STAR.
On reaching the last waypoint you did receive the following:-
United 370 maintain Heading 175 expect vectors for the ILS runway 35 Right Approach
However, your last waypoint was only 5 miles from your destination which is way too close! Again you would have received a warning about this when loading the flight plan, which unfortunately you chose to ignore. I would recommend your last waypoint should be no closer than 20-25 miles from your destination.
You weren't given a STAR as you hadn't set one up
Incidentally, my flight plan included a STAR but that was ignored by ATC
Just including a STAR in your flight plan is not enough unfortunately and you have to tell PF3 you want to fly a STAR. There's a very good explanation about the use of SIDs and STARs in PF3 included in the User Guide... please see section 20.5
Finally, I was cleared for the approach and given a localizer intercept after I had already flown through the localizer, so the heading I was given would not have worked. Because I was situationally aware (as well as had the airport in sight), it was easy to recover, but the bottom line is that it seems ATC is lagging way behind in issuing instructions in a timely fashion. Perhaps some of this was MSFS and SimConnect lagging, but certainly there shouldn't be any reason to be kept in the dark about the arrival.
No, this was all due to your last waypoint only being 5 miles from the airport
Hope that helps to understand why things didn't quite go to plan