Ok so I decided to do my first proper IFR filed flight plan in FSX.I was flying from Edinburgh to Amsterdam.first bug (happend 3 times)1) I was issued instructions by ATC- But in the ATC window, I did not have the option to acknowledge the instruction, however ATC kept asking me to repeat instruction back.they ask 3 times to repeat, then they cancel the IFR due to no response.this means I had to re-file my IFR plan whilst in air ( 3 times this happened)^^ that happend in FS9 now and then also.2nd bug now, this happened in FS9 alot.. which made me stop doing IFR... The ATC gives very different heading instructions right after each other.I.E turn right to 090 degrees-you make the turn then the sayturn left 010-you make the turnthen its turn right to 090 degrees again-you make the turn- thank back to 010 etc etc etc^^ i hoped they would fix this really obvious bug.the fact it happend with my first IFR plan in FSX too, it didnt look very promising.look at my map for an example of this, you see how I was directed all over the place before final vectors.anyone else experience this?-tibbzhttp://forums.avsim.net/user_files/159418.jpg

I feel your pain. Yesterday I was flying a short 45 minute flight, and with FSX ATC routing it took me an additional 63 minutes of flight time due to constant turn instructions for approach vectors. I have Radar Contact and can't wait to get an updated version for FSX. Best investment I've ever made.

the problem with ATC is that they try to keep you on the GPS route therefore you end up doing a jagged line rather than a straight one. I found the best solution for this right from FS9 ie. as soon as you get handed off on reaching cruising altitude, acknowledge but DON'T CONTACT THE NEXT STATION. You only contact approach when you're near the beginning of descent leg. Problem errrr solved?? :)

Hi,that would be a solution but I quite like the interactivity when doing an IFR flight.I think (though cant remeber), but in FS9, even if I had a direct GPS airport to airport route with no waypoints... it still sent me on a jagged route when nearing the airport :/how come they didnt fix this as its a blaringly obvious issue.-tibbz

That's my method too, but even when you contact ATC again at the beginning of the descent leg you will be directed all over the place... HDG after HDG after HDG...I was quit disappointed that they didn't do anything about the ATC, apart from the new ATC-window, which I like a lot. I didn't buy Radar Contact because I thought FS ATC would be fixed, but maybe I'll buy RC now, when it's been made compatible with FS X. I never fly online and like ATC a lot, so...

The `disappearing` response window problem is purely because you pressed the acknowledgement button as soon as it showed up. Wait a couple of seconds after the response box changes and the IFR calls will continue to show uop - the lag is just another example of how far the computer system is being pushed by FSX.As for the other thing, try slowing down. ATC will try to maintain traffic separation with AI, which travels at the speeds AI just travels at (obtuse, but it varies) If you hear there's a Dash-8 in front of you, slow down to 180-190 knots, if its a 737 you can maintain 240-250 knots relatively easily. IRL ATC will `stream` the various traffic flows not by instantaneous separation, but by `computing ahead` the arrival in the descent zone and maintain separation at that point. En route separation is often maintained by FL changes. FS ATC does it `for the moment` and in the horizontal plane only, so if you don't go the `dont ackowldge` route your only other option is to speed up, slow down, or request an altitude change to take you out the sphere of influence of whatever airraft is influencing your flightpath.The increased level of AI in FSX is only going to make this worse!Allcott