Microsoft ATC problems, Again....

[Aiden327]

OK, this is the last time I re-install FS2004 because I am going to end up getting radar contact anyway as I've always wanted it.

Today, I flew my average semi-fictional flight (KEWR to KMDT to KEWR). Simply pick up passengers from newark, take them to harrisburg and then others back.

I make it from KEWR perfectly with Ultimate traffic and FDC Live cockpit with a perfect landing, of course im all real happy. I notice a storm moving in because im using real world weather and time settings but I manage to make it to KEWR airspace in one piece. ATIS reports 400ft overcast and 1inch rain. With the combination with my trusty co-Pilot handling the flaps and calls and check-lists we line up perfectly for landing. Just as my VCP is saying "OK, decision height you have control of the aircraft" Microsoft ATC sends me on a Go around messing up everything. After flying a published miss approach  atc proceeds and throws me 40 miles out in the opposite direction on heading 310 and then terminates IFR.

I know Microsoft ATC is not perfect, but giving me a go around for no reason, flying me past the empire state building, near misses with Jet Blue and a Spirit wings aircraft and then just leaving me on my own is a bit dum.  >:(

My question is is there anyway of "patching" this bug until I can buy Radar Contact because its going to be a while until I can get it.

Sadly once this happens once, it never stops happening and atc gets less accurate with every approach every time and always terminates my ATC after sending me off on a wild goose chase  :o. The only way to make the ATC accurate again is to re-install.

I don't use the GPS any more because I know my route by heart but I feel bad when I have to Cheat now to make sure the atc is doing their job. Flying without ATC is not an option because my goal is to be as real as possible for a possible future career or hoby in real aviation...

-Aiden

EDIT: Could this also be at the fault of EditVoicepack? I am pretty sure all that does is speed up atc messages and modify terminology to comply with ICAO standards.

[Sean_TK]

I don't think it's an edit voicepack issue.

I've had this occur very occasionally where FS seems to forget about you when sending you on a go-around. Perhaps there was an AI aircraft on the runway or on approach that had priority. Not sure what you mean by 1inch rain in the ATIS forcast...haven't heard that before, and doesn't make sense either.

In any case, as you have realized, the MS ATC can sometimes screw up. For some reason, it happens to some people more than others. The cancellation of the IFR by ATC rarely happens to me, but I'm sure it can be annoying if it is common on your system.
Since you are unable to obtain Radar Contact for a while yet, I would suggest

[JBaymore]

Install AISmooth to take care of SOME of the pesky AI conflicts.  At least you'll get less go-arounds.  It put them in holding patterns if they offer too much conflict with you on final.

best,

...................john

[olderndirt]

In the 'real' world, only the pilot can cancel IFR.

[JerryH]

Hi Aiden,

I would also recommend getting AISmooth if you haven't already.

The solution that always works best for me is to ignore the "Go around". Just continue with your approach and landing. When the tower yells at you, just fire the whole bunch of them. It's your sim, not theirs. Problem solved.

As far as mid-airs and runway collisions, I turned off collisions many years ago. I see no reason to ruin a perfectly good flight experience because of a minor software glitch. FS2004 (or any newer version) will never be perfect, so I prefer to maintain control of these situations when possible.

There's another option that may work when ATC terminates your IFR plan for no good reason. Check the ATC menu to see if you have the option to file another flight plan. If so, just file the same one you were on, then see if ATC picks you up and vectors you back toward KEWR. It's worth a try.

While I may have sounded a bit flippant earlier, I do take sim flying seriously as a hobby and a learning experience. But FS2004 (and any newer versions) will never be perfect, so I find it more satisfying to use simple work-arounds instead of tearing out more hair.

Regards,
JerryH

[Aiden327]

Thank you for all your reply's! I will look for AISmooth, hopefully it will help a bit.

I have heard of VATSIM and I will think about giving it a try in the future, right now my pc is not in a good condition and Im very busy so online would

[Sean_TK]

Hmm. I have never heard of someone having as many ATC problems as you have had. I have heard of the occasional ATC mess-ups, but it does not seem to be a common problem.
Maybe it's an AFCAD issue.

Also, what type of ATIS service are you using, because I have never heard one forecast a measurable quantity of rain in FS.

[Capt.Propwash]

does your ATC do this at 1 particular airport, or at various ones????

usually what i do in that instance, climb back up to 5000 ft, enter left pattern and go around... just like ATC told you to do. when you get back to "base leg" ATC will usually tell you that you are clear to land.

[DaveSims]

I think I can clarify the 1 inch rain observation.  I would bet the ATIS was reporting the visibility as 1 (mile) in rain, not 1 inches of rain.  

[visualchaosfx]

The thing that helped me the most was just setting the traffic slider to around 30%. The airports are still filled but the skies are not heavily populated with aircrafts. This made the go arounds less. I've had the ATC cancel IFR before. Lately I've been flying VFR. I input the flightplan in the FMC and just follow that route. Bad thing is that if I want to fly out of an airport thats really foggy, I get denied. ATC says IFR only. But I take off anyways.

[Capt.Propwash]

there is always a trick to IFR thought.  I have filed IFR before, but flew VFR the whole way, being that i got my VOR/DME Frequencies and put them in the NAV1 / standby by myself and flew it that way.  Granted you have ATC telling you to "turn left heading XXX".  

But then again, you could always file IFR, then when you are at your cruising altitude, cancel your IFR plans and fly VFR, then before you land..... just remake your IFR plans and land ILS.

[Fr. Bill]

The only way to make the ATC accurate again is to re-install.

Reinstalling FS is absolutely the very last thing anyone should do...

Ninety-nine percent of the time, the real problem exists in one or more of a half-dozen "dynamic configuration files" that FS manages during the course of any session. The two most common "problem files" are:

fs9.cfg
default.flt

Both of these files keep track of changes that've occurred during a session, and if either one (or both) become corrupted with trash data, then you will experience repetitive "odd behavior" in the sim.

Before doing anything drastic, the first step is to simply rename the current fs9.cfg file to something such as ORG_fs9.cfg, then restart FS9 and allow the sim to build a completely new and uncorrupted fs9.cfg file.

Most of the time this will correct whatever problem you've encountered. If so, then simply copy/paste any custom keyboard and controller settings from the ORG_fs9.cfg file to your new fs9.cfg file to complete the recovery.

If that doesn't solve the problem, delete the new fs9.cfg file and rename ORG_fs9.cfg back to fs9.cfg.

Then, load FS9 and create a completely new default flight using the C172 and your home airport. Save the flight and make sure to put a check mark in the "make this flight the default flight" box.

If neither of these two procedures solves your problem, STOP mucking around immediately and come post a question, providing as much detail as possible.  ;D