I believe there is a conflict between RC 3 and FDC as it relates to key strokes of 1,2,3,4, etc. RC has ceased to function at times when using both programes simultaneously.

I don't use FDC, but this is a known issue, and one of the team members is working on a solution. You can define both RC and FDC keys. See if you can find a happy medium. I personally use CS-1, CS-2, etc. so I can use 1,2, etc for engine control.

Hi Les,I'm cautiously optimistic that we've hit on the solution here.Doug suggested I try some variations and it looks like the order of which you start up your applications will make the difference between success and failure.I run FS SkyWorld along with FSMeteo so the order I start my applications is as follows: FS SkyWorldFS2002FSMeteoRadar Contact version 3Flight Deck CompanionThe whole key here is that it seems you MUST start Radar Contact FIRST before starting Flight Deck CompanionIf I start FDC prior to RC then I can consistently reproduce an FDC error message. If I start RC first and FDC last everything is solid and stable.The sequence of events during a flight for me look something like this:Auto-Cabin Announcement - FDCATIS - RCv3Clearance - RCv3Pre-Start Checklist - FDCRequest Push - RCv3Before Pushback Checks - FDCBefore Start Checks - FDC(pushback)After Start Checks - FDCGround Control - RCv3Taxi Checks - FDCBefore Takeoff Checks - FDCTower - RCv3After Takeoff Checks - FDCDeparture Control - RCv3Center - RCv3Climb Checks - FDCDescent Checks - FDCApproach Control - RCv3Approach Checks - FDCTower - RCv3Landing Checks - FDCAfter Landing Checks - FDCGround Control - RCv3Post Flight Critique - RCv3Parking Checks - FDCGive this a try and see if it doesn't work. I've just spent the last 4 hours experimenting here and it works for me every time now. It's high workload but MAN is it fun! Having full crew checklists and ATC is the ultimate!Let us know if it works for you!Michael Collierhttp://jdtllc.com/images/RCbeta.jpg

Does not the FDC program let you change the keystrokes. I have the newest version and that is what I am going to do on mine and that way I dont run into this problem. Dave

beta testers have shown that it is the order that the programs are loaded is the problem/solution, regardless of keystrokes used in either program.the correct order is rc, and then fdc.

Dave,Both RCv3 and FDC allow you to define keystrokes. However, even after verifying to the best of my ability that there were no shared keystrokes I was getting an FDC error message. The error was related to an unassigned hotkey in FDC. I've been sitting here for several hours this evening happily reproducing the error at will. It seems that it only happens when you start FDC BEFORE you start RCv3.As long as you start up FDC after RCv3 then things work perfectly together. More news as it develops but for now that's how I'm getting them to play nicely together.:-waveMichael Collierhttp://jdtllc.com/images/RCbeta.jpg

:-jumpy

Mike,Thanks for the information. I'm testing a flight at this moment and everything is working flawlessly. The start-up order is:FS 2002FS Flight TrackerFS METEORC 3FDCIt looks like that's the ticket. A heck of alot easier than messing around with keystrokes ! Thanks again.

:-jumpy Michael Collierhttp://jdtllc.com/images/RCbeta.jpg