Well I finally got a copy of FS2004 and after a couple of IFR flights, I can see that ATC interaction has improved significantly over FS2002. Being able to request altitude changes and alternate approaches certainly makes an IFR flight more realistic. However ...I still find that MS ATC will start vectoring you between 80 and 120 miles out ... very unrealistic in my experience (particularly in the northeast). Most often it's pilot nav to IAF or a STAR and vectors when you're 15-20 miles out.Is there any way to configure FS2004 to reduce the distance from the field that ATC will begin vectoring?Thanks!

Love to edit that as well. I usually find that ATC has the "you're six-zero miles north, turn right heading 185, descend and maintain 12,000, expect default ILS on biggest runway" too often. I'd love something a little more realistic...Best,sg

That was my biggest gripe about FS2002, and still is with FS9. It's not as bad with FS9 because you can sometimes request an approach with a transition that keeps you on your original flight plan.Last night I was flying fron KDAL to KLFK. I filed direct to CQY VOR, then V569 to the LVK VOR. The weather at KLFK was VFR, so I was planning to cancle IFR when I had the airport in sight and land VFR. Just after I passed the CQY VOR ATC told me I was 107 miles NW, turn left to 095 for vectors ILS RWY 7.I requested the VOR approach via. the LKF transition and all seemed fine. Then before I got to the FZT VOR along V569, they ATD wanted to vector me to the LFK VOR, so I cancled IFR, got flight following and continued as if I were IFR.I had an idea to get around this, but I havent tried it yet. I'm going to creat my flight plan, but not activate it. I'll get flight following and fly the route as filed, then when I'm 20-30 miles out I'll open the IFR flight plan and let ATC give me vectors.