9 hours ago, Orlaam said:

Yes they match because I have all the older charts on paper.  The problem, despite FSX having the correct altitudes in the approach profiles, is that you aren't allowed to descend on time per your distance and speed.  If you're going 210 knots at 10,000 feet and have 7 miles to get to the IAF at an altitude of 5,000 then it ain't happening.  Of course you could dive at 2500 FPM and bust the speed restriction, but then you'll never slow in time to configure properly for landing.  It's a problem more often than not with default ATC, henceforth the reason I stopped using it for IFR.

Perhaps those descent profiles work if you are in a Cessna going 120 knots, but not much else.

I never had troubles with that and I fly the iFly737 and the Wilco Airbusses vol1 all the time on managed descend but default planes aren't very realistic with the V/S default at 1800ft/min

Herman

On 3/22/2017 at 8:15 PM, scott967 said:

The default action of FS ATC is to give you a vectors-to-final.  The optional action is to use the ATC menu to request an approach and transition.  In that case FS ATC vectors you to the transition entry (for ILS approach has to be a transition based on VOR).  You have to make requests for 1 runway 2 approach and 3 transition.  If you don't request a runway you will get the "sidestep" (if your requested approach is not to the ATC-prefered runway).

 

scott s.

.

 

Nice to see someone else who understands FS ATC. What I do apart from writing new approaches every time I fly (update) is make the transition altitude (IAF) the glideslope interception altitude which not only makes  FSATC do a far better job with my descent rate but also makes sense of the phrase "descend and hold xxxxxft until established" (xxxx being the GS interception height) 

On 3/26/2017 at 0:32 AM, electricman said:

I never had troubles with that and I fly the iFly737 and the Wilco Airbusses vol1 all the time on managed descend but default planes aren't very realistic with the V/S default at 1800ft/min

Herman

I haven't truly flown a default MS plane in 15 years.  It's been Dreamfleet, PSS, Level-D, PMDG, and others all along.  I used to use the ATC approaches in FS9 with the myriad add ons I had from PMDG, Level-D, Dreamfleet, Digital Aviation, and I think maybe 50% of the time I could make the altitude at IAF.  If you are just following ATC for ILS vectors then fine, but to choose an actual approach with an IAF and expect ATC to let you meet that restriction?  No way.

I didn't talk about a chosen approach but the assigned approach, if you want to request a different approach because you can't get to the altitude restriction in time then that strikes me as odd, in my opinion that is a missed approach and a go around.

Herman