Hi all. So I am nearing the end of a long flight from LAS to EWR at FL370. The controller instructs me to contact Cleveland Center on 132.4. I acknowledge the controller and as soon as the radio changes the sim goes to a black screen and the encounterd a problem box appears. The culprit: atc.dll. It has happened on 3 seperate occasions now, only with this sector. Anyone know what is happening? It occurs with different aircraft. Thnks

I see you are on FS9. Make sure you have the 9.1 service pack installed:

 

http://www.microsoft.com/en-us/download/details.aspx?id=9727

 

"To determine if you need the Microsoft® Flight Simulator 2004: A Century of Flight (UPDATE):

1. Run Flight Simulator 2004.
2. Click Fly Now!
3. Press ALT to display the menu bar.
4. Click About Microsoft Flight Simulator on the Help menu.
5. Check the version number in the About Microsoft Flight Simulator dialog box. If the version number is 9.0 we recommend installing the update.

After updating, the version number for Flight Simulator 2004 will be 9.1."

 

There is a bug in 9.0 that where under certain circumstances comm frequencies are repeated (but not necessarily an immediate repetition) you'll get the crash you described. Supposedly 9.1 may correct that.

 

See the fsuipc 3 manual regarding this.

Im sorry I should have posted that in the original post. I am running the FS9.1 update.  I also am running RC V 4.3.3845 and makerunwys 4.6.7.4. FSUIPC is 3.9.9.9.

It is still that FS9 bug.

 

Try adding this statement to the General section of fsuipc.ini:

 

RemoveATC=Yes

 

which turns off FS9 ATC. See if that helps. You will no longer be able to get FS9 ATC on your screen. This will not affect ai or listening via RC to ai comms.

 

If things get worse take that statement out.

 

If this is a one time issue with that it might be other issues. If the error can be reproduced you might make an RC log as pinned at the forum head. Before your flight bring up the RC controller page and jot down the destination frequencies used. You can also use a shorter flight but use the same last third or so of your path with the same cruising altitude so the same frequencies are used for center and approach.

OK. Ill try that and report back the results.

Well I had another crash, this time with a different sector. However I had saved the flight about  a minute before instructed to contact center and it crashed. I reloaded the flight and started the debug but could not replicate the crash. Instructed to contact Albuquerque center and tuned in without a problem the second time around. But I did notice something that may not be anything but I noticed that the enroute center frequency I am instructed to contact and get a crash is the same frequency as the wx briefing frequency at the departure airport. When it crashed on Clevland center the freq was 132.4. My departure airport was KLAS and the ATIS freq was also 132.4. This time my departure airport, KCLE, had a ATIS freq of 127.85. The Albuquerque Center freq it was tuning to when it crashed was also 127.85. Could these be related?

The frequency repetition is indeed the suspected cause of the atc.dll crash. I'm not sure if it is specific to ATIS and center but the pattern is there.

 

This is a bug in atc.dll I believe.

 

The atc.dll in the modules folder is version 9.01.040901.01 in my 9.1 update.

 

Now normally atc.dll is running in the background whether FS ATC is being used or not ready to tune perhaps placing frequencies in a queue. Putting "RemoveATC=Yes" in the general section of fsuipc.ini supposed to inhibit FS9 atc.dll from functioning.

 

Have you tried running the same scenario with that statement in your fsuipc3 version of fsuipc.ini?

 

You will notice the FS9 ATC menus will not appear with that statement active.

 

Again, this is not a function that affects AI operations.

 

 

I have inserted that line as instructed and will let you know what the results are. Thanks