I've just noticed that ATC is giving me totally different random courses and altitudes to what i planned. For example if im flying on FMS/GPS hold (not NAV) bang on course atc will be telling me to turn to almost a 90 degree turn sometimes. i also get new instructions every few minutes so im tipping and turning all flight, not very pleasant.As for the approach, 15 NM from the runway im being told to be at 14000 even if i descend to the altitude i should be at, please could someone help me out with this.also theres no point in APP charts as ATC just makes a totally random spur of the moment route for me.another bug is that theres always a plane, ALWAYS, almost in an exact position and location on course to fly on the same runway as me at the same time. virtually every flight i come within 50 foot of another plane, then have to do a go around. has atc never heard of a holding point?

Welcome to FS ATC... This is it, really...FS ATC only takes notice of plans you make with the build in FS Flightplanner. If you make a plan and file it with ATC, it will lead you along that path. But only until you get near your destination: from there on ATC will vector you towards a point from which you will be able to intercept for instance the ILS.Plans made with other programs or whatever are not being followed by FS ATC, unless you are able to export the plan as a native FS plan: then ATC will follow the plan again.It is 'normal' for FS ATC to let you change directions more often than you'd expect...Indeed, APP charts are completely useless because FS ATC doesn't know them. SIDS and STARS and the likes are unkown to FS ATC.Planes getting in your way is another know issue. I don't experience it that often because I have the AI at 10 or 20 %, so... I remember about a tool called AISmooth that will help you on this: don't know it myself, I just remember reading about it last week somewhere...Since I do a lot of VFR flights and don't mind using the unrealistic flight planner for IFR I seldom have problems with the FS ATC... The do a good job to get you to your destination, but it's not realistic. I like it: it's a nice gimmick, so to speak... ;) But if you want it to be more realistic you should consider getting online with VATSIM or something like that.

thanks a lot :) now i realise why i was getting what i did :) also thanks for suggesting AI smooth, ill go search for it in the library now.

oh by the way is there any program i can download that really improves FS ATC by giving me more realistic amounts of turns, better altitudes, new options, just a general improvement?

There is no program that will improve FS ATC, but there is a prog which will provide a very realistic ATC environment - Radar Contact, Go and have a look at the forum below.Bud

Look for a thread containing RC, FE, and ASV. It includes pros and cons of Radar Contact.It is a payware program that I have been using since experiencing the "defects" of FS8 ATC. I still use it in FS9.Rather than repeat myself, find that thread in this forum and also check out their support forum here on AVSIM.

ATC will vector you into a position that is outside the final approach fix, on a heading that will allow you to intercept the final approach course, at the minimum altitude for that segment of the approach.I agree the FS ATC is kind of jumpy and will issue quite a few turns. The FS ATC often delays the clearance to descend to a step down altitude to a point late in the approach. It's not a bug, per se, but that is the way the logic is coded right now.What rate of descent do you use? While enroute, you use a rate of descent that is at least 500 fpm, and a greater amount consistent with safety. Factors influencing the choice of rate of descent include traffic avoidance, obstacle clearance and the capabilities of your airplane. Within the last 1000 feet of the assigned altitude your rate of descent needs to be within 500 - 1500 fpm. Reference: Instrument Flight Training Handbook.Some mental calculation is usually required. When ATC clears you to descend, first figure out how much time is required to get to the next fix at your descent airspeed. Then divide the amount of altitude to loose by the amount of time to the next fix. That yields the rate of descent. In a GA aircraft the rate of descent may be relatively small over large distances. In speedy jets at high altitudes, however, the rate of descent may be quite high. Rates of descent of between 2000 and 3000 fpm, at high altitude, would not be considered unusual.One final note: a high rate of descent at low altitudes is not recommended. Instrument approach procedures are designed so that rates of descent remain reasonable even for aircraft with high approach airspeeds. A three degree descent angle, for example, may yield a 450 fpm descent for an aircraft making 90 kts on approach, and that same angle may yield approx 1100 - 1400 fpm for an faster aircraft. That's about as high a rate of descent you would want to have near the ground.

That's incorrect. FS ATC does know instrument approaches. It vectors you to a point outside the final approach fix at the minimum altitude specified on the plate for the intermediate/initial segment of the approach, which is what real controllers do.What you can't do with FS ATC right now is request the full approach and still be under FS ATC control. A full approach is flying to the initial approach fix, execute the procedure turn (or DME arc) and fly the approach. That doesn't happen in MSFS. MSFS ATC is only coded to replicate ATC vectors to the FAF. In spite of this limitation, approach plates are not only useful for flying IFR in MSFS, they are required if you want to fly instrument approaches. The plates give courses to fly from the FAF, MDA/DH and missed approach procedures, among other important information. Flying an instrument approach is beyond, you know, just having some guy on the ground tell you which direction to fly to find the airport, so having the plate and knowing how to read it is important, even in MSFS.

If you want it as real as it gets and with real world approaches and procedures, start flying on line with the VATSIM or IVAO networks. Many of the controllers are real-world too.