Hi Sandy,Seems a lot of work just to add one line. I just wanted CG to be aware of the problems if he deleted the INI.Cheers,

Hi Sandy,Well now it's ok, but in fact the problem was that I have assigned a key to switch on or off the fsuipc display, so I suppressed this key and now it works like you told me.Another question it's possible to assign a key for display/hide fsuipc window without problem with window of fs9 atc?And thank you for your help.

Hi CG,You're welcome. Pete Dowson did a fantastic job in providing the workaround for the atc.dll crash problem as well as implementing the new FSUIPC Display window.The key to the left of the "1" key--the "tilde" key on US keyboards--is now used to toggle the FSUIPC Display window. This is the same key that Microsoft originally assigned to toggle the ATC windows.Without RemoveATC=Yes, this key still toggles the FS ATC windows as previously, while the FSUIPC Display Window is always "on".With RemoveATC=Yes set, this key toggles the FSUIPC Display window, and the FS ATC windows are always suppressed.I believe that the key to the left of the "1" key may not be used as the "tilde' key on some non-US keyboards, but it is still the FSUIPC Display toggele nonetheless.Hope this helps,Sandy

Hi Sandy,I'm sorry but it's still not working well (always fs atc window open), I think it's because I have a non US keyboard, the key you told me assigned the spoiler and for me the key to toggle on or off the atc window of fs9 is on the left of enter key. Have you a suggestion?Thank you

Hi CG,1. Are you sure you are using FSUIPC 3.553?2. Have you made sure that the "FSUIPC multiline display window" option, in the FSUIPC front option screen, is checked. 3. Are you now seeing the new FSUIPC Display window? Please note that this window disappears when it it empty.4. Do you have RemoveATC=Yes added to the [General] section of your FSUIPC.INI file? If so you should never see the FS9 ATC windows.BTW you can toggle the new FSUIPC Display window by means of a hot key or a joystick button. Just use the FSUIPC AdvDisplay Hot Key or Button options.Hope this helps,SandySandy

Hi Sandy,It's me again, yes all you said it's ok....But the problem is still here...nevermindThank you for you help and if you have a new solution contact me.

Hi CG,At least we were able to help you eliminate the atc.dll crashes.I'm afraid that I have no further advice. It appears that the problems that you are still having are related to your FSUIPC installation. I suggest that you direct this matter to the Peter Dowson Support Forumhttp://forums.simflight.com/viewforum.php?f=54Good luck,Sandy

I just wanted to mention that this issue is still alive & well (well not well). Twice I've had a CTD while switching freq. and didn't put 2 & 2 together until searching the forum & found this. When I checked both flight plans in RC4 sure enough the ATIS frequencies were the same at departure & arrival. I flew the same route twice and recieved a CTD then the 3rd time I changed the arrival ATIS (on the controller panel) to a different freq. and whala (sp?) landed at -283 ft/min.I have the latest FSUIPC 3.74 so it's not an issue there. I'd just suggest always scanning the controller page for repeating freq at both arrival & departure arpts. I don't know about controller freq as every mention I've found refers to at least 1 ATIS freq & then either the other ATIS or a controller but I just change any freq that is repeating one of my ATIS freq.Hope this helps.Bobby

Sorry to re-open this thread but I've had the same problem with CTDs in FS2004. These occur in one area only. In my case, a triangle between Belfast - Isle of Man - Dublin. My CTDs occur when I activate the Garmin in any plane, or when I turn off the taxiway and ATC requests a change to Ground frequency. Sometimes the GPS works okay but the simulation crashes as I turn off the runway. Sometimes I do not get as far as the runway. I can fly for hours in Alaska or Eastern England without any problems. I've posted about it on the General FS2004 forum because I thought it was a scenery problem - I was using SBuilder to modify scenery around County Down, N. Ireland. I've disabled/removed all my addon scenery and I've replaced all the relevant ABxxxxxx.bgl, APxxxxxx.bgl, etc, files in the Eurw scenery folder from a back up version of FS9 on an old PC. This did not make any difference. I've checked for duplicate AFCADs and removed these. No difference. I then uninstalled my recent install of RC4.3 but the problem remains. I am running FSUIPC 3.75. Can the atc.dll problem occur even after RC4.3 is uninstalled? If so, how to fix? Thanks. John

Hi John,The atc.dll bug is inherent in FS9 and although Pete Dowson managed to prevent some instances of it in a release of FSUIPC he wasn't able to catch them all.Although it may appear RC is responsible for the crash it's only the messenger. The problem arises when you change a frequency - either tuning an ATIS or switching to TWR from Approach for example. No definitive reason has been discovered but the presence of identical frequencies in your departure and arrival airports appears to be responsible for some of them.Check the frequencies at both sets of airports and if any are the same then change one to keep all frequencies unique. That may help. Use NotePad to edit the relevant data file and save the change. Sorry, I can't remember which data file but look for the one that starts with the ICAO followed by a set of frequencies.Cheers,

Thanks, Ray. I checked the ATIS, Twr, Gnd, App etc frequencies in the area and there were no duplicates. The Garmin causes the problem too. I've been flying in this area since 2004 without CTDs so something has happened recently to cause them. I've eliminated the scenery as a cause and am left with ATC. Something changed the way ATC works and the most obvious thing to exclude at this stage is RC which I had installed recently. At one point I installed advdisp.dll but this has been deleted.Can RC leave a 'footprint' in the form of an .ini file or similar to cause conflicts.

no i don't.chang the season. jump ahead to summer. still get the error?jd

I didn't read through every reply in this forum ao I don't know if it was mentioned but I remember something in the FSUIPC manual saying to delete a certain MSFS file if using a third party ATC add-on to prevent probelems from occurring. I don't remember if it said CTD's exactly or not. I have experienced this same CTD problem though. If it happens to me one more time I'll try deleting that MSFS file.

Spring, summer, autumn, winter, no difference. I fly with VATSIM and use FSInn, FSCopilot. Could one of these be doing something it shouldn't? Maybe I will uninstall these next.John

Hi John,If you upload your plan here for the route that causes the problem I'll fly it and see what happens.If this is ma recent problem then ask yourself what you have installed that could have caused it? New airport scenery could be favourite. Do you have any 3rd party scenery installed for the two airports in question?I honestly can't remember the last time I had a atc.dll crash and I fly all over Europe and occasionally the US.