Hello Radar Contact,After an initial hic up or two getting RC up and running ( my fault entirely) this certainly makes me sit up and pay attention when I fly, especially when my first two flights critique were somewhat uncomplimentary. However, I've now got the hang of things and have discovered a flaw in one particular flight, namely from LFAT Paris Plage to LFPG Charles de Gaulle. I've done this flight twice to assertain if it was my fault but on both occasions the same problem occured at the same point of the flight. I'd been directed to a heading 150 degrees for vector to 26R . I was asked to call Approach on133.70 but the RC window shows 121.40. I pressed 7 on the keyboard to respond but the radio was set to 133.70. Pressing 1 on the keyboard didn't change anything and I was repeatedly advised to respond.Eventually I was asked to contact Twr. on 118.65 but 121.40 still showed on the RC window. The only way I could escape from this situation was to select a visual approach and then things then returned to normal.Don't think this is me this time.As as aside, I've recently added a second screen so I place all my pop ups on it including the RC window. I discovered that if you don't click somewere on the main screen, the keyboard won't respond to the numbers on the RC window. Probably an old problem but I just thought somebody else might have struggled with it and wondered why.Regards,Richard.

RC responds only when one of the FS main views has focus. If you were dragging them to the second monitor then maybe an FS screen was not active. The FSUIPC/RC window does not count as being an active FS window and RC will not respond to keystrokes if that has the focus.Here's the frequency data RC4 uses for LFPG:LFPG,Paris - Charles-De-Gaulle,126.17,121.72,118.1,118.65,0,0,133.37,0133.37 is in the approach column. If you have RC autotune on contact enabled that is what your radio should tune to if you use the contact or ack and contact option. Make sure no other program is tuning COM 1.If RC was not responding to your keystrokes perhaps 121.4 was a left-over from center or other frequency. See the first paragraph. Also if you handed the comms to the RC co-pilot make sure you took them back for your approach.If you wish to verify your frequency data go to the data folder under your RC4 folder. Make a safe copy of f4.csv. Right click on f4.csv on open it with Wordpad or Notepad. Search for LFPG and it should find the line I've pasted above. This file must be treated as .txt but unless instructed do not edit and save this file.If that problem continues you can make a log to send in when you starting at your descent by alt-tabbing to RC and clicking Debug and then alt-tab to FS to continue your flight.

Thanks for your reply.Re your first line, that's what I discovered after I fitted the second screen. I just thought it was worth a comment.I'll fly that route again sometime and verify that the problem is still there. As I said, Comms 1 auto set to 133.37 but the RC window showed 121.40. I had responsed to ack. but I was continually hit by " I say again....".I'll try your remedy to send a log if I knew how to do it. I'm afraid I'm not too I.T. savvy.Thanks again,Richard.