Yes, they don’t work well together even IRL. VNAV only does what we tell it to do. It is oblivious to weather, traffic, and even obstacles. ATC wants traffic to flow in an orderly manner in the airspace. VNAV doesn’t know about “traffic flow”.
VNAV and ATC work together to have aircraft meet waypoint crossing restrictions but not all waypoints have restrictions and it is possible to manually override restrictions.
In my IFR/ILS flights, I’m on on approach (activated) with GS captured descending down the glideslope and ATC is telling me to climb back up to the cruise altitude.
In the USA, Equally alarming, is which Controller (Tower or Approach) is issuing those Clearances , and why an Approach controller is turning you over to Tower, when you are still having IFR vectors to the ILS, and neither the pilot or controller has confirmed that you are actually established on then ILS.
Maybe this is closer to the way they do this outside the USA ?
Most likely you started your approach without getting clearance to the interception point or you didn’t follow STAR properly. ATC in this game does not care where you are, it cares if you flew over certain “checkpoints” along the route. If you skip one checkpoint ATC will keep giving you instructions to that checkpoint. Imagine a Forza game or similar where you have to drive through checkpoints along the track. If you miss one, the lap won’t count until you drive back and pass that checkpoint.
CJ4 AP does fly the flight plan correctly.
But the ATC expects the waypoint PATRN to be met.
And wants me to return to cruise altitude.
At 18 nm past KEWR, ATC directs me to contact NY
Center.
NY Center ATC advises to continue to PATRN while I am flying away from KEWR and PATRN.
On the runway prior to takeoff, if I enter PATRN into the scratchpad and replace the discon, then ATC does follow the flight plan.
I wonder why the PATRN waypoint is replaced with a discontinuity.
You would think using a stock plane with stock map and stock ATC would all work together.
However this is not just a stock plane, it has been worked over by Working Title and has a Rockwell Collins FMC.
As such while the stock map & ATC will work in sync with each other (looking for PATRN), the plane will behave in a different and more realistic manner.
The Rockwell Collins is looking for an airway to join the departure airport to the first waypoint or a SID.
If it doesn’t have either of these then it comes up with a discontinuity (realistic) as it would presume you’ll be getting ATC vectors instead if neither of these are selected.
The workarounds are:
Use Simbrief to plan your flights, not world map
Use a SID in your flight planning
Put PATRN in on the runway
Ignore ATC altogether and go direct to AGNSS.
Incidentally, PATRN is not included in any real world routing between these 2 airports
I tried requesting vectors from ATC and requested them 2 or 3 times.
But, flying the vectors does not do anything.
And does not seem to affect the AP.
Just flying vectors with the Heading.
In the real world, it means ATC will vector you, then clear you to a waypoint on your fight plan (i.e. “Proceed direct PATRN” in your case), and you will use a DIRECT TO in the FMC to activate it, then hit NAV, and Bob’s Your Uncle.
As you have seen, vectors are broken in MSFS. Some alleged improvements are coming in SU14, but I’m not on the beta so I’m not sure how much it’s really improved, or if it can actually handle departure vectors. That would be helpful for places like KORD where there are no SIDs and everything is vectors.
ATC is broken in msfs so you do need to make allowances for this, the CJ4 presuming vectors is a real world thing which doesn’t really work in the sim at the moment.
Think of it as the CJ4 being far more realistic than msfs flight planning or msfs ATC.
If you want to do vectors to the first waypoint yourself either use heading mode or direct to exactly like you just did but Simbrief will clear up all these issues, not only is it compatible with msfs it is also very compatible with the CJ4 and will automatically work out the best SID & STAR (if applicable).
According to SimBrief, the download instructions for MSFS are:
Download this file anywhere onto your PC.
Open your simulator and go to the “World Map” screen.
Click “Load/Save” at the bottom of the screen, then click “Load”.
Browse to and select the *.PLN file you downloaded in Step 1.
NOTE: After import, you may need to reselect your SID, STAR, or approach using the provided dropdown menus.
Whenever I import from SimBrief, I always reload the SID and STAR because the SimBrief flight plans (.pln file) do not contain SID and STAR waypoint altitude and speed restrictions needed by ATC. This is why ATC seems broken because descent instructions aren’t issued early enough.
Currently MSFS (including ATC) only process correctly flight plans (.pln files) created or modified using the World Map. Flight plans (.pln files) from other sources do not import correctly for MSFS ATC. The “workaround” is to use the World Map to modify the imported flight plan, not use flight plans created outside of MSFS, or not use MSFS ATC.
Personally, before every flight I review the SID and STAR for altitude and speed restrictions. If ATC does not issue climb or descent instructions correctly, I request the new altitude from ATC and dial in the speed restrictions. This works for me most of the time.
There have been recent MSFS updates enabling in some cases upload of FMC-entered flight plans to MSFS ATC. This assumes the flight plans entered into the FMC are complete and correct.