Hello--This has happened a couple times now, but I'm not sure which airport I was at the first time, but tonight...I was flying from KLAX to KLAS in the default King Air and had been given my approach/runway for landing. As I got closer, I was told to tune to approach 133.95. My radio automatically tuned to 133.95, but the dialog box only gave me the option of calling approach on 122.00. So....after about 20 seconds, I get told "Beechcraft 16, I say again, tune to 133.95". But I am not given that option on the dialog box. I press "1" to call approach, but it doesn't go through and it still shows 122.00. In another 20 seconds or so, I get told again to tune to 133.95. So I am just stuck at this spot and can't get past this point. Any ideas?Thanks,Don

Well in real life you would squawk '7600' on your transponder (the transponder code for communication equipment failure), then do a wide circuit and land when you can see the runway is clear, not before the time your flight plan is scheduled to indicate your ETA at the airport. So you could try that. Of course it doesn't solve your problem, but from a technical standpoint you would then still be doing everything correctly as per real world operations.Al

Hi Don.There are two things that come immediately to mind...The first is that you may have an addon KLAS where the comms frequencies don't match the defaults and (an old version of) makerunways didn't do a thorough job. Without a quick test (I'm not at a gaming PC right now) I couldn't be sure that it may be the cause. Still, it can't hurt to download and run the latest version (4.41 I believe, though I've seen a 4.43 beta).The second is that you need to take a look at the 'Controller' page in Radar Contact just to make sure there are no conflicts between controllers and no bad entries in there. I was caught out by failing to see what I was looking when I started using RC and found that e. g. 133.95 didn't work, the correct format being 13395 with no decimal point.Regards,Dave

Hello--This has happened a couple times now, but I'm not sure which airport I was at the first time, but tonight...I was flying from KLAX to KLAS in the default King Air and had been given my approach/runway for landing. As I got closer, I was told to tune to approach 133.95. My radio automatically tuned to 133.95, but the dialog box only gave me the option of calling approach on 122.00. So....after about 20 seconds, I get told "Beechcraft 16, I say again, tune to 133.95". But I am not given that option on the dialog box. I press "1" to call approach, but it doesn't go through and it still shows 122.00. In another 20 seconds or so, I get told again to tune to 133.95. So I am just stuck at this spot and can't get past this point. Any ideas?Thanks,Don

can you duplicate the problemm, and make a log?instructions on how to make a log is pinned to the top of the forum. be sure you click debug BEFORE loading your .plnthen duplicate the problem, and send me the log file, zipped upjd

I will make a log next time I fly (Sunday) and see if the issue happens again.By the way, the only change I've made since before this happened was updating to the latest version of ASE and FSUIPC. I was trying to get the fix that's pinned above about ensuring the proper runway assignment from the controller.Also, I have not installed makerunways. Is that recommended? I do not have any airports installed, but run GEX, UTX, REX.Thank you.-Don

Don't know if this is related but other versions of Active Sky use 122.0 for weather flight watch. If flight watch is enabled in AES disable it to see if there is some kind of conflict.Makerwys does not affect in RC4 comm frequencies. The fixed data for KLAS in f4.csv shows 13395 (133.95).

JD - I sent you my latest logfile in winzip format last night, per your request. That would be about 12 hours ago (9pm EST). This is the flight from KLAX to KLAS in the default King Air 350. The problem happens as I am approaching the airport...all is well for most of the flight until I get within about 10-20 miles. The same symptom with respect to being asked to tune to 133.95 and not being given that option.Ronzie - I went into ASE and turned off flightwatch, per your recommendation, but the issue still occurred. I would not be surprised if some ASE conflict is the problem as I have the long delays between keyboard commands and hearing the actual announcements when interacting with ATC. I will try turning DWC off and using FSUIPC for smoothing. I did add the UseASEweather=Yes command to the FSUIPC.cfg file, as was suggested to get the correct weather. I have also turned on "Force Destination Weather".Dave_Morgan - I also looked at the controller page and did not see anything out of the ordinary. As I mentioned, I don't have any add on airports and don't use makerunways.Chock - while I was making the logfile flight, and I couldn't contact approach, I did switch the transponder to 7600, swung out and came in when all was clear. So I did what I could! At least I got the hours counted toward my FSPassenger career. :( Thanks.Don

JD - I sent you my latest logfile in winzip format last night, per your request. That would be about 12 hours ago (9pm EST). This is the flight from KLAX to KLAS in the default King Air 350. The problem happens as I am approaching the airport...all is well for most of the flight until I get within about 10-20 miles. The same symptom with respect to being asked to tune to 133.95 and not being given that option.Ronzie - I went into ASE and turned off flightwatch, per your recommendation, but the issue still occurred. I would not be surprised if some ASE conflict is the problem as I have the long delays between keyboard commands and hearing the actual announcements when interacting with ATC. I will try turning DWC off and using FSUIPC for smoothing. I did add the UseASEweather=Yes command to the FSUIPC.cfg file, as was suggested to get the correct weather. I have also turned on "Force Destination Weather".Dave_Morgan - I also looked at the controller page and did not see anything out of the ordinary. As I mentioned, I don't have any add on airports and don't use makerunways.Chock - while I was making the logfile flight, and I couldn't contact approach, I did switch the transponder to 7600, swung out and came in when all was clear. So I did what I could! At least I got the hours counted toward my FSPassenger career. :( Thanks.Don

will look at it in a little bitjd

JD - I sent you my latest logfile in winzip format last night, per your request. That would be about 12 hours ago (9pm EST). This is the flight from KLAX to KLAS in the default King Air 350. The problem happens as I am approaching the airport...all is well for most of the flight until I get within about 10-20 miles. The same symptom with respect to being asked to tune to 133.95 and not being given that option.Ronzie - I went into ASE and turned off flightwatch, per your recommendation, but the issue still occurred. I would not be surprised if some ASE conflict is the problem as I have the long delays between keyboard commands and hearing the actual announcements when interacting with ATC. I will try turning DWC off and using FSUIPC for smoothing. I did add the UseASEweather=Yes command to the FSUIPC.cfg file, as was suggested to get the correct weather. I have also turned on "Force Destination Weather".Dave_Morgan - I also looked at the controller page and did not see anything out of the ordinary. As I mentioned, I don't have any add on airports and don't use makerunways.Chock - while I was making the logfile flight, and I couldn't contact approach, I did switch the transponder to 7600, swung out and came in when all was clear. So I did what I could! At least I got the hours counted toward my FSPassenger career. :( Thanks.Don

looked at the logat 40 miles out, told to contact approach on 133.95, you dial it in, and contact approachit then looks like you request an iap approach, but you don't finish specifying the approach. looks like you are the selection submenus for a very long time. eventually you are told to contact tower on 118.75are you requesting an iap approach as soon as you contact approach?if not, what menu is displaying while you are traveling from 40 miles out, until you are told to contact tower?jd

JD-Thanks for looking at the log. I don't remember exaclty what the menus were when I flew last, but I considered what you said about being in the menus for a long time.So... I flew the same KLAXKLAS flight plan tonight, but was very disciplined to not hit any keyboard commands unless specifically instructed by ATC, and everything worked fine. I was directed on the downwind leg, base leg, then final approach. I was in the submenus last time because I am new to the program and was seeing what the various options were. Also, I requested an altimeter check a few times as I get penalized in FSPassenger if I don't have the correct altimeter. I may have hit some commands along the way that put the program into a do loop of sorts, I'm not sure. I also was kind of concerned due to the delay of getting a response after hitting a command. I may of hit the same command a few times because I wasn't sure if the key press was working.Thanks again for the help. I have to say that, overall, I'm really happy with Radar Contact. It is somewhat liberating to be free of FSX ATC! Now that I know I have to be patient, I hopefully won't see this issue again. I am still going to try some of the ASE changes (turning off DWC) to reduce the lag.-Don

Be sure to look at AES postings here. In particular get Service Pack 2 which provides additional options in its control mode.