I've been using RC for only a few weeks but absolutely love it so far. It has worked flawlessly on numerous flights of varying lengths and locations with my Carenado Bonanza, C340, and C208B.Unfortunately, I'm having issues now when I use it with some of my jets (F1 Mustang and F-Lite A320). RC simply freezes at seemingly random periods of the flight after an instruction to change frequencies. It has happened on the ground when switching to Clearance. It has happened in flight between Centers. This morning it happened at the end of a long flight, including a highly entertaining series of holding vectors, when the controller instructed me to contact the airport for my arrival. These freezes have occurred both when I was controlling the communications and when "Otto" was handling it for me. I'm 0-6 on completing a flight with RC with these two aircraft and am extremely puzzled.Since I can't seem to isolate what's different about these failed flights versus my many successful ones (except that it always happens in my jets), I was hoping for little guidance on how to begin to troubleshoot this odd problem. No doubt it's user error. Oh, and this is with FSX with a registered copy of FSUIPC version 4.60a running in Windows 7, if that makes a difference.Thanks in advance for any suggestions!- Alex

You should update FSUIPC to at least 4.70. See the links at the forum top.Next time you fly oner of these jets, before you press the START button in RC, click the Debug button to create a log of RC technical data running its functions in your flight. After the problem occurs quit RC and FS. Go into your RC4 folder and look for rcv4.log I suggest adding a date to the name to make it unique. Then follow the procedure pinned at the forum top to send it in.Is there anything special with these two jets that cause a problem?Perhaps there is a gauge conflict or something similar. If the program slows or halts use alt tab to cycle the the program screens. Sometimes pop up program crash are behind the FS view on the screen.Try things out a few times and reply here if you see any error messages.One thing to watch out for is something that steals key strokes like enabling the pc keyboard as input in an FMC.

You should update FSUIPC to at least 4.70. See the links at the forum top.Next time you fly oner of these jets, before you press the START button in RC, click the Debug button to create a log of RC technical data running its functions in your flight. After the problem occurs quit RC and FS. Go into your RC4 folder and look for rcv4.log I suggest adding a date to the name to make it unique. Then follow the procedure pinned at the forum top to send it in.Is there anything special with these two jets that cause a problem?Perhaps there is a gauge conflict or something similar. If the program slows or halts use alt tab to cycle the the program screens. Sometimes pop up program crash are behind the FS view on the screen.Try things out a few times and reply here if you see any error messages.One thing to watch out for is something that steals key strokes like enabling the pc keyboard as input in an FMC.

Thanks for the tips! I updated FSUIPC to 4.703 and tried another flight in my F-Lite A320 from Minneapolis to St. Louis. Everything was fine until I tried to switch communications over to "Otto," who had controlled the radios during some early parts of the trip, about 80 miles from St. Louis. I got the "standby" text message but Otto never responded. After that, I could cycle through various windows of the RC text options, but requesting a change in altitude, a weather report, etc did not produce any responses. Didn't see any error messages, but I did have to force RC4 to shut down as an "unresponsive program" after exiting FSX.I've sent in a log from that flight. I'm sure this is just some boneheaded user error, but it sure has me scratching my head!Thanks again.

If you had an outstanding acknowledgment at the time you switched that can stall RC. It would also cause you not to get credit for crossing a waypoint.The log should tell.It may take a while for jd to respond. Atlanta is experiencing severe weather again and his server might go down if he gets an extended power outage.

Thanks for the tips! I updated FSUIPC to 4.703 and tried another flight in my F-Lite A320 from Minneapolis to St. Louis. Everything was fine until I tried to switch communications over to "Otto," who had controlled the radios during some early parts of the trip, about 80 miles from St. Louis. I got the "standby" text message but Otto never responded. After that, I could cycle through various windows of the RC text options, but requesting a change in altitude, a weather report, etc did not produce any responses. Didn't see any error messages, but I did have to force RC4 to shut down as an "unresponsive program" after exiting FSX.I've sent in a log from that flight. I'm sure this is just some boneheaded user error, but it sure has me scratching my head!Thanks again.

if the problem persists, the only way i'll be able to figure out what's happening, is to see a log. instructions pinned to the top of the forum, on how to make a log. make sure you click debug, before loading the flight planjd

I finally made a successful beginning-to-end flight with my F1 Mustang using RC. As I expected, I think the problems I was having were simply user error. I believe my main issue using 2x and 4x time compression too early after take-off and also leaving it on too close to decent/approach when instructions and navigation changes come too quickly. I look forward to giving it another shot on my A320 soon.Thank you again for the tips and for this wonderful product. I'm really enjoying it immensely!

I finally made a successful beginning-to-end flight with my F1 Mustang using RC. As I expected, I think the problems I was having were simply user error. I believe my main issue using 2x and 4x time compression too early after take-off and also leaving it on too close to decent/approach when instructions and navigation changes come too quickly. I look forward to giving it another shot on my A320 soon.Thank you again for the tips and for this wonderful product. I'm really enjoying it immensely!

like another post above. 4x is a no go. unless you REALLY know when you can bump it up, and when you bump it down. at the end of the day, it just isn't worth it. the risk of losing rc is too high. if you can't finish the flight in one sitting, hit ctrl-shift-; save the flight with a name you'll recognize tomorrow, and pick up the flight tomorrow by loading the saved flight in rc.beats the alternative. a long silent approach....jd