Key Assignments not working...

[Avi8tor1]

Hello,I purchased Radar Contact 4 in hopes of being able extend my simulation knowledge and get a feel for how real-life ATC works, as I am working towards becoming a commercial pilot one day. Since the download, this program has given me nothing but problems. I have had high hopes for this program, as it has been around so long, and has appealed to me for such a great period of time only to realize how much pain I am going through. I had trouble finding the download link, and finally found it. Once the registration finally came in, I installed it and tried to load a flightplan. Apparently I was missing my msstdfmt.dll, so after trial and error for another 30min or so, got that. Now to my biggest frustration, the Key commands don't work. Whatsoever. I have FSUIPC 4.703 or whatever it is, loaded and the Key Assignments in the program are all defeult. Upon loading FSX, pressing the 1 and 2 keys to try to listen to ATIS or File my Flight Plan the window just stays there, no "Standby" text is seen and ATC says nothing. Please help me as I would really like to get this program to work, so I can get in the air as soon as possible. Hopefully, I don't have to give up on this program and fall back to FSX's default ATC.I am running Windows 7 64-bit.Any help is appreciated.Cameron Caldwell

[ronzie]

There are several reasons why RC may not respond to key commands:The most common is that the FS panel view windows do not have focus. Click anywhere in a panel view but the RC in-flight window so FS gets the keystrokes which are passed via FSUIPC to RC.Some add-ons running may trap the keystrokes assigned to RC by default or may not even pass on keystrokes they do not use. You need to insure there are no conflicting keystrokes in an add-on application that conflict with RC. A good example is the PMDG 737NG FMC. If you enable keyboard input to the FMC those keystrokes defined on the FMC keypad will not be passed to RC. You can reassign RC keystrokes including key stroke combinations in the keyboard tab of RC.The current full release of FSUIPC for Win 7 is FSUIPC4 4.70 (:(. Later interim links are in the pinned topic on the page top. The latest version is FSUIPC 4.705 at http://forum.simflight.com/topic/66139-updated-modules/. This version get through some Win 7 loopholes in security.

[Avi8tor1]

There are several reasons why RC may not respond to key commands:The most common is that the FS panel view windows do not have focus. Click anywhere in a panel view but the RC in-flight window so FS gets the keystrokes which are passed via FSUIPC to RC.Some add-ons running may trap the keystrokes assigned to RC by default or may not even pass on keystrokes they do not use. You need to insure there are no conflicting keystrokes in an add-on application that conflict with RC. A good example is the PMDG 737NG FMC. If you enable keyboard input to the FMC those keystrokes defined on the FMC keypad will not be passed to RC. You can reassign RC keystrokes including key stroke combinations in the keyboard tab of RC.The current full release of FSUIPC for Win 7 is FSUIPC4 4.70 (:(. Later interim links are in the pinned topic on the page top. The latest version is FSUIPC 4.705 at http://forum.simflig...dated-modules/. This version get through some Win 7 loopholes in security.

Thank you Ronzie! I shall give it a whirl. I am using the MD-11 by PMDG which does have the FMC command (but I don't use it anyway:Black Eye: ) I'll report back with my findings...Your help is apprciated!

[Avi8tor1]

Okay so I clicked anywhere on the panel, that didn't work. What confuses me the most is that Radar Contact worked for one flight then stopped after that. I reinstalled the program and it still isn't working. My FSUPIC is not a registered version...is that the reason why? If so it dosen't really make sense to me why it worked for that one flight...

[ronzie]

RC should be registering it itself with FSUIPC. It does not need a paid version. In your FSX\modules folder there should be a file called fsuipc.log. Look at it with notepad or wordpad to see if there is something about RC registering itself.Here are some things to try;Run just FS with a default aircraft and RC and no other add-ons running. Turn AI percent down to zero (off) for now. This will reduce any chance of an add-on stealing keystrokes or causing interprocess communications being slowed to to other applications hogging resources.Have you created a shortcut to RC with its advanced properties set to Run As Admin? This insures Windows communications between RC and FS. Please note that logging in with admin privileges is not the same as setting a program to run as admin in its shortcut.When you are not getting a response to keystrokes please alt-tab to switch to RC and other windows. This should bring forward any errors hidden by the FS windows.You have the option of creating a log to send in for analysis. When loading RC click the Debug tab. Add the date to the suggested title to make it unique. See the pinned topic about creating and sending in a log. You would would run RC until it failed to recognize your keystrokes. Then you can alt-tab to RC to quit it and prepare the rcv4-date.log by zipping it to send in.The standard order of doing things with your environment is important. Start FS first and load your your flight at the gate insuring let's say the clock is ticking. Start a weather add-on if you have one and load the weather. If there is a refresh option use that to immediate update the weather and AI patterns plus ATIS reporting. Then load RC, load your plan, and make your option choices. For best RC performance in your options/general tab Display Text should be off, PreRecorded Chatter should be off, AI Chatter should be on, and Interact with AI should be on. For now keep control of the comms, pilot auto-reply off, auto-tune on contact on so your comms follow RC's fixed comm frequency table (as shown in the RC Controller Page) and tunes your comms for you, and keep control of the aircraft. (RC will not control the PMDG MD11 because of its non FG standard auto-pilot.) Start RC. The FSUIPC/RC window should appear. Make sure your APU or ground power is enabled with avionics on. Prep your FMC and IRS to get ready to go. Now get your clearance and then ack it. If you are OK request push back if needed. When in position request taxi and get your runway assignment. Do not ack it until your have set up your departure runway in the FMC and updated your V speeds, etc. Then ack it and taxi to the runway. As you get close to the runway be in take-off configuration and pull very close to the runway. Be aware that in a high cockpit configuration that you will appear closer to the runway than you are for RC purposes. When AI traffic allows, you'll be cleared to taxi into position and hold. When released listen carefully for any intitial headings, etc.Depending on your departure choices and the location of your first waypoint, you may not receive vectors to your first waypoint. See the RC tutorials about the various departure scenarios.That's how things should go.

[Avi8tor1]

Got it. I didn't realize that you had to load the plane before you minimized FSX, then started RC4. Silly me :(.I just had a final question regarding SID/STARs. I've read that RC4 does not include SID/STARs in the program but use them as a waypoint (?). I am using the FSX flight planner for now (which obviously doesn't include SID/STARs) however, if I use a program like FSBuild to create my Flightplan will RC4 incorporate the SID/STARs as waypoints? And I believe I heard somewhere that you can ask ATC to permit you to use a STAR approach. At which point in the flight do you ask this and how do you? I haven't come across this yet...I appreciate all the help you have given me. I'm so happy it finally works!!!!Cameron Caldwell

[ronzie]

FS Build among others expands SIDs and STARs in its database into individual waypoints when it exports in your FS and other formats like FMCs. FSBuild now allows updates via the paid Navigraph subscription system used for many FMC databases. If you subscribe to it you can download all of the cycle formats you wish at no additional fee for that cycle. This allows syncing your FMC database with the flight planner so there is sync between procedure waypoints in the FMC and your FSBuild flight plans.The important thing is that waypoints of the FMC legs page match those in the plan RC gets (FS9 or FSX).I'll be back later today to answer the rest of your question on this.

[ronzie]

Here is my tip sheet regarding the use of FSBuild and similar flight planners (as requested):-----------------------FSB tips:1. Include this line in FSbuild.cfg:NAVCHKDUPDIST=100This decreases the chance of using the wrong duplicate named local (to the airport) waypiont from a nearby airport. Local waypoint names are not exclusive. It decreases the database search when it is named in the route to within a 100 nm radius of your airport. You will find these in terminal procedures such as "D" number something within a SID or STAR to define a merge or turning point.2. When doing a Auto Generate (Route) be sure the SR (Stored Route) button next to it is "up" that is not highlighted. Auto Generate will use a stored route if found by default and most are out of date with old waypoints and terminal procedures. Having Stored Routes off forces it to search a path with fresh data. (Now off by default in version 2.4.)**REVISED 12/31/10** 3. Starting soon in 2011 FS Build database updates will be exclusively released through navigraph.com. It should be part of the FMC data line. For those not familiar with Navigraph each subscription term (cycle) includes multiple format downloads at no additional cost. This is very convenient for aligning FMC/navigation equipment databases with the flightplanner so among other things ATC data and your nav equipment data should match as you send a plan to ATC and then load it including terminal procedures into your FMC. The 2.4 upgrade includes the thirteenth cycle of 2010.4. Where an airport uses specific runways for different terminal procedures select the runway using an estimate based on weather and if the runway fits your aircraft requirements before doing the Auto Generate. This helps select the correct SID and STAR for the runway and direction of departure and arrival.5. After the Auto Generate and/or first build look at the map created to spot any obvious errors. In the route grid look for any sudden non-sensible changes in direction or extremely long legs not in the correct direction creating a zig-zag in the map. (See item 6 following to correct).6. Be aware there is an option you can set for each session titled "Build Route from Grid Table". It does not stick between sessions. This lets you build from an edited route grid that you may have modified without recreating the table with the same error on your next build/export. For example you might wish to drop an errant waypoint when proofing the map and rebuilding.7. Sometimes the name of a procedure (SID/STAR) does not match the name exactly in a published route and the procedure will not expand into its plan waypoints in the grid table. You can click on the arrow in the SID/STAR box to see what close name is in the FSB database. (Another reason to keep up with AIRACS.) For example KMSP has a current real such as this one:http://flightaware.com/resources/airport/KMSP/DP/WAUKON+TWObut the FSB database only has UKN2. (It does have UKN3 now with the latest available AIRAC update). If so in the route line just change UKN3 to UKN2 so it will expand. Here's a real route from flightaware.com for KMSP to KMDW:KMSP UKN3 DBQ CVA MOTIF3 KMDWthat can be pasted into the FSB route line. If UKN3 or MOTIF3 does not expand in the route grid to individual way points look in the upper part of FSB in the airport section dropping down the SID or STAR box to get the available version and substitute that label in the route line and rebuild. Note that the SID and STAR dropdowns may follow the chosen runway in certain areas.8. Sometimes it takes a second build to get the map to move and/or magnify. The mouse scroll wheel lets you magnify. Just click on the portion of the map you want to center on and scroll to magnify.9. If you click on a line in the route grid table to highlight it, the waypoint on the map will turn red. This is useful for finding errant waypoints that cause an error in the path. That line can then be edited or deleted and a rebuild accomplished with the build option to build from the route grid table.10. If you are running a weather program such as active sky, first build the route in FSB exporting to FS9 using an anticipated cruise altitude and specify the nearest aircraft profile. In AS get the weather you wish to use. (I always get the weather for the zulu time of the departure in FS since time of day affects weather characteristics). Import the plan into AS via the new route button, check the altitude and choose an appropriate true airspeed in knots (this is your no wind ground speed). Process the route. When it is finished click the button to print a hard copy of all. Use this AS navlog for METAR data at both ends and winds aloft and temperature aloft that can be used for FMC data. (You'll also get your estimated average wind at your specified altitude - handy for FMC data.) Leave AS running. Now go back to FSB and your chosen aircraft profile. Enter the surface temperature from your departure METAR, then estimated total taxi time, hold time, and extra time (sometimes called discretionary fuel). Now turn on again your FS9 export along with any FMC export you might use. Rebuild and you'll see the messages regarding the export completion. On the route selection on the left which brings up your route window select the navlog tab and click the .pdf to save the navlog in a file or the print button to get a hard copy so you can easily reference the estimated fuel and other data. This estimated fuel has now taken into account your winds aloft data - no need to enter it in FSB. Now that you have the hard copy and exported your route, you can first optionally save the plan by selecting flightplan window, then clicking the category tab, then select user category. Now click file, save from the menu bar. The name you might want to embellish. Click Save Route To User Flight Plans. For another session, you can recall this working plan and just build.11. If you are using an aircraft with nav equipment that has its own terminal data procedures in its nav equipment (think FMC) you might wish to use step 6 above to take out the waypoints of the terminal procedures keeping just the transition points and build and export with just them. This easily in most cases lets you select the SID and STAR assigned by ATC on your nav equipment by providing a clean legs list in your nav equipment. If you need ATC to monitor the waypoints of the terminal procedure than just export all. To keep ATC and you nav equipment in sync, you might consider importing the full plan into your nav equipment and not using your nav equipment procedure database.This is kind of long but through experience I've described some tricks I've used watching out for any pitfalls.Be sure to check the FSBuild forum for updates.----------------------

[sameermankame8960]

HelloI am also facing the same thing as "Cameron" faced before.The only change is i am running:-1) FSX SP22) iFly 737 NG3) FS2Crew2010 for iFly 737 NG Voice Version4) My Traffic XI heard this is best addon ATC for FSX.....Please let me know what is wrong.Can't wait to fly my new NG with Radar Contactsamman6707

[ronzie]

Please refer to the replies preceding in this thread.With all of those add-ons be sure that there are not any conflicting keystrokes and the current versions of FSUIPC have not been overwritten. You can reassign RC keystrokes including combinations with crtl and shift options if needed.Be sure RC is the last thing started (START button) in your sequence. If the iFly 737NG has a function where the FMC can capture the keyboard make sure it is turned off before starting RC. Also be sure you have a loaded flight running before starting RC.