I installed rc on my fsx machine. I load up fsx, load up rc, import the same flight plan to both rc and fsx. Rc screen comes up but does not recognize any keypress. I've tried changing the keyboard mapping but to no avail. My system is as followsFsx sp2PMDG 747Rex/gex/utxFsdreamteam kord (that's not the airport I am trying rc with though)I've downloaded and installed the latest makerwys and rebuilt in rc. It just worked one time n1) installed rc and started at kord. Didn't work2) ran rebuild. Started at kord and worked but fsx crashed. 3) started At kord. Didn't work. 4) rebuilt. Started at kord didn't work5) started at kbos( no addon airport). Didn't work6) rebuilt and started at kbos. Didn't work.Forgot to mention nI use just flight mytrafficx also. Captainsim 757 is installed but not running.

Make sure you also have installed the latest FSUIPC4 as pointed to in the pinned links topic. This is especially important if running Win 7 or VISTA in 32 bit or 64 bit installations.In order for RC to receive keystrokes an FS window must have focus, not the blue FSUIPC-RC window. Also if running VISTA or Win 7 that RC is started with a shortcut that has its property set to run RC as an admin.The only other common cause is when another application is 'stealing keystrokes' such as some FMC's if their PC keyboard input is enabled or there are conflicting keyboard assignments. Occasionally depending on PC performance keystrokes are delayed getting to RC when a number of heavy loading applications are running.Just test with FSX, RC, and default aircraft and scenery to see how RC behaves. The try running with added applications one at a time until things become unstable. To increase RC performance avoid setting RC options Display Text and Prerecorded Chatter enabled. Just enable AI chatter and Interact with AI. Also test with you keeping the comms and control of the aircraft, not the copilot.Another thing to try is to alt-tab through running applications and the desktop in case an RC or other error dialog window is 'in back' of the window that has focus (in front).Nothing that RC does should cause FSX to crash. Remember not to click START in RC until your flight is loaded with aircraft at the gate and your aircraft clock running (if present).If nothing is resolved you can create a log for RC to run until your crash or unresponsive keyboard issue occurs. Just click the DEBUG button when loading your plan and before you press the STAR button in RC When that happens alt-tab alt-tab to RC and just quit. In the RC folder rename rcv4.log to something like rcv4-MMDDYY.log (month, day, year) so it will not be overwritten and follow the procedure in the pinned topic to send it in if need be.

Make sure you also have installed the latest FSUIPC4 as pointed to in the pinned links topic. This is especially important if running Win 7 or VISTA in 32 bit or 64 bit installations.In order for RC to receive keystrokes an FS window must have focus, not the blue FSUIPC-RC window. Also if running VISTA or Win 7 that RC is started with a shortcut that has its property set to run RC as an admin.The only other common cause is when another application is 'stealing keystrokes' such as some FMC's if their PC keyboard input is enabled or there are conflicting keyboard assignments. Occasionally depending on PC performance keystrokes are delayed getting to RC when a number of heavy loading applications are running.Just test with FSX, RC, and default aircraft and scenery to see how RC behaves. The try running with added applications one at a time until things become unstable. To increase RC performance avoid setting RC options Display Text and Prerecorded Chatter enabled. Just enable AI chatter and Interact with AI. Also test with you keeping the comms and control of the aircraft, not the copilot.Another thing to try is to alt-tab through running applications and the desktop in case an RC or other error dialog window is 'in back' of the window that has focus (in front).Nothing that RC does should cause FSX to crash. Remember not to click START in RC until your flight is loaded with aircraft at the gate and your aircraft clock running (if present).If nothing is resolved you can create a log for RC to run until your crash or unresponsive keyboard issue occurs. Just click the DEBUG button when loading your plan and before you press the STAR button in RC When that happens alt-tab alt-tab to RC and just quit. In the RC folder rename rcv4.log to something like rcv4-MMDDYY.log (month, day, year) so it will not be overwritten and follow the procedure in the pinned topic to send it in if need be.

Couple of things I wasn't doing right1) Starting RC before I was at the gate. I'm starting RC at the "Free Flights" screen. 2) Keep the focus on the blue window. As far as I recall, I always have focus on the RC Window in a mad dash to get it working. 3) FYI - RC did not cause the crash. The crash was due to a Kaspersky notification and subsequnetly FSC becoming unresponsive. I guess I should have been clearer. I will try all your recommendations and come back. Thanks for the prompt support.

I corrected all of them and now Radar Contact works fine. Thank you !However, I have now developed another problem where PMDG 747's autopilot wants to take it to a higher altitude than programmed in either VNAV or manually specified by me. This is the first time I'm seeing this issue . Checked my altimeters and they are ok. Could this be somehow related tp RC? Wx avoidance.....dunno....

To clarify:

Couple of things I wasn't doing right1) Starting RC before I was at the gate. I'm starting RC at the "Free Flights" screen.Yes, you must have a flight active running in FS first. 2) Keep the focus on the blue window. As far as I recall, I always have focus on the RC Window in a mad dash to get it working.The focus must not be on the RC blue window but on an FS window.3) FYI - RC did not cause the crash. The crash was due to a Kaspersky notification and subsequnetly FSC becoming unresponsive. I guess I should have been clearer.See the pinned topic on antivirus software. RC needs to be made a trusted application due to its frequent access of the FS folder.I will try all your recommendations and come back. Thanks for the prompt support.

I have the PMDG 737NG suite. The 747 should be similar.(As stated RC can not control this aircraft using the co-pilot and therefore does not control the aircraft altitude other than issuing commands to you, the pilot.)If RC is complaining about your altitude you may not be switching the altimeter to the correct reference pressure when you are above the transition altitude. If you are commanded to a flight level your altimeter must be set to a standard pressure reference of 29.92 in. or 1013 mb. If you are commanded to an altitude in feet your altimer reference is then set to QNH or the surface pressure MSL reference. RC should give this value and it will change during flight. In FAA territories the transition altitude is 18,000 feet. Unfortunately FS is hard coded to 18,000 feet if you use the default 'B' key. The transition altitude elsewhere varies for the jurisdiction sometimes as low as 3,000 feet. You can see the transition altitude RC uses by opening the controller page and looking at each airport column before you start it. You might want to jot those down. On your PMDG 747 panel glare shield to the left of the MCP if it is like the 737 there should be a BARO section. Pushing in (clicking) the knob will toggle the altimeter reference to STD or the pressure you have set by 'turning' it. Check the 747 manual. On the 747 PFD under the pressure you set it will annunciate 'STD' in yellow or nothing as you toggle between the two references.The altimeter tape in the PFD always reads in feet. To convert feet to a flight level divide by 100. Therefore a reading of 30,000 feet on the altimeter equates to FL300 in ATC terms when you are above the transition altitude on standard pressure reference. Likewise when you are commanded to FL300 multiply by 100 which will be the altitude of 30,000 displayed on the tape (and you have set the altimeter to standard pressure).If you are using the the altitude display in FS it probably will not match all conditions.As far as VNAV in the 747 you need to check the manual about how you enter the altitudes in your FMC and how they are displayed on its screen (CDU) on the LEGS pages. You also need to check the 747 FMC manual on how to enter and change cruising altitude on your CDU on your RTE page. I believe three numbers is interpreted as a an altitude in 100's of feet so 130 on the scratchpad is 13,000 feet. I'm fuzzy on that. You'll also note I thing on the PROG pafe for destination you can enter the transition altitude for arrival. I think on RTE page 1 or 2 you can enter the departure transition altitude. Please check your FMC manual - it has been quite awhile since I've used the Smith's Boeing FMCs and I could be incorrect about the locations for entering these.Another VNAV error could be a pitch trim setting out of range or in the lower altitudes having flaps engaged when they should not be. Be sure one of your CMD buttons is lighted and not kicked off by a joystick bump or turbulence briefly taking the aircraft outside of its performance range.In the RC manual there several sections regarding transition altitudes and you should learn this. Until you get used to this I recommend you use LVLCH and ALT on your MCP to control altitude and get involved with VNAV. Remember that ATC rules, not your FMC so I'd stay away from VNAV for now and switch between LNAV and HDG as needed to comply with ATC.Finally, while discussing vertical navigation, read in the RC manual about the crossing restriction which occurs about forty miles out from destination and will be announced during your descent by ATC if above it. I put in the Smith's FMC a 40nm range ring around the destination airport to show on the ND. To do this go to the FIX page and key in the scratch pad the ICAO code of the destination airport and LSK that into the FIX label. Then enter /40 into the scratch pad and LSK that into the Bearing/Distance line of the CDU. You can do this before you take-off. When you are descending and RC has handed you the crossing restriction altitude be sure you are at or below this by the time you cross the range ring assuming no terrain problems.You might wish to take some shorter flights using RC and default aircraft to get use to things since in FS you most likely will have your hands full most of the time being both copilot (now called PNF - Pilot Not Flying )and pilot (now called PF - Pilot Flying).