I can't even get started. Well! I got the flight plan loaded then clicked on start RCV. Then what do I do. The manual did not load.Thanks in Advance

First for the FAA airports get the departure and arrival information from www.flightaware.com. Enter the airport ICAO and then click on airport information. You can then download for each airport you designate a .pdf file of bundled departure and arrival plates plus the airport diagram.Have a printout of your flightplan ready.The correct order is:1. Start and set up your flight parked in FS.2. Start any weather program, load any weather, then activate the weather. If there is a command to refresh use that and if there is a command to refresh AI use that also.3. Start RC. Choose your aircraft, airline, and tail number (or flight number). If you have not done so initially, choose the voice for your pilot, copilot, and your multiple controllers.4. In the setup tab I recommend AI Chatter (not prerecorded), Interact with AI, and you may wish initially to widen your heading and altitude tolerance.5. Load your flight plan. Go to the controller tab and make any appropriate changes for your departure and destination. Note the transition altitude for departure and arrival. This is the altitude you set your altimeter to standard pressure (29.92 inches or 1013 mb) on departure and for arrival back to surface pressure.6. Start RC. It will hide.7. Use your task bar or alt-tab to get to FS.There should be a blue transparent window that you can drag where you wish. Get a paper and pen ready. Make your sound is turned up.1.Via the RC menu get weather or ATIS as available especially current surface altimeter (it will be in mb or inches appropriate to your area). Note the active runway if present.2. Enter the menu number to get clearance delivery. Write down your initial altitude assignment and squawk code. Ack the delivery. Put the squawk code into your transponder. Set your altimeter. If using an autopilot place the initial altitude in there.3. Finish prepping your aircraft. Request push and start. Do the FS push routine (if needed) and then start your engines with all your lights on, etc., except landing.4. Call ground to get taxi instructions and clearance to the active runway. Ack the clearance. Start taxiing to the active and get your aircraft ready to go. Put the assigned runway heading into your A/P.Set flaps on the way out if needed.5. When told to contact tower you may wish to wait until you are near the threshold to ack the hold short instruction. Be ready to go when you do ack. Wait at the hold short point as close as possible to the runway until you are told to enter the runway. There should be no active acks waiting to be done. When landing traffic permits you will be told to position and hold at which time landing lights on, enter the runway, ack the tower, position for take-off. When giving your take-off clearance note any heading other than runway heading, enter it if you wish into the A/P, ack the instruction, and start your roll and take-off. As soon as you are 100 AGL steer the initial tower stated heading while climbing engaging the A/P heading and altitude as appropriate. Remember to stay below 250 knots IAS below 10,000 feet. Follow the gear retraction, flap retraction, and IAS schedule for your aircraft.6. Contact departure and ack any instructions following them by manipulating the A/P as necessary. When told to do your own navigation you can engage A/P NAV insuring you are going DIRECT from your present position to the waypoint indicated in the RC window. Do not return to the original flight path.7. Follow ATC instructions as necessary and contact center when necessary. Ack instructions and promptly follow them.8. During descent you will be given a crossing restriction altitude usually to be at about 35 miles from destination. Be sure you are there to avoid delay vectors - RC will not let you proceed toward the airport until you are at that altitude. You will also be told to contact approach.9. Follow the vectors for approach disengaging LNAV and manipulating your A/P as necessary. Reduce speed to 210 knots or below within that 30 nm range. Follow your aircraft approach procedures. Depending on your arrival direction you may get a downwind, base, or almost straight-in approach entry to the airport pattern. While you are not on LNAV, set up your NAV 1 OBI (or A/P course) to the LOC or ILS heading for final and set the correct NAV frequency if you are using an A/P approach if merging to a localizer and perhaps glide-slope path. RC will take you out far enough and turn you for the correct heading to merge with a localizer if present at the proper altitude. You can also do this with a VOR approach with less accuracy and of course you will need to control altitude. When your VOR needle starts centering turn your aircraft inbound and engage APP. Be sure you are tracking the correct localizer/VOR by identing it via audio morse code or on your navigation display before engaging APP. (This is especially important where FS has the same frequency at both ends of the same runway.)10. All during pattern entry and approach you should be following the correct flap and speed schedules for your aircraft. Drop the gear when appropriate and contact tower when advised. Be sure your gear is down or at the last minute tower will give you a go-around. Be sure in your A/P window you have the runway heading in the HDG window in case you do get a go around. The missed approach altitude should be in the A/P ALT window.I'm sure I've forgot a few things and this is oversimplified. If you are using an FMC be sure you know how to go direct from your present position the the indicated waypoint RC expects. For guidance during landing know how to advance your LEGS page. If you are taking vectors for approach you most likely will not be crossing all og the approach waypoints on the FMC. ATC RULES, not your FMC. Stick with the MCP accordingly when taking vectors.The manual with tutorials should be in your RCV4 folder as a .pdf file. Go through some of these to get familiar with it.I suggest training on a simpler default aircraft preferably a prop default plane until you get familiar with RC..You will also find manuals, a quick start, and tutorials here:http://www.jdtllc.com/documentation.htmGood luck and welcome!

what is the version number?hover over the fsuipc4.dll or click add-ins in fsx, and then click fsuipc.

4.1.6.O its in the Module folder in the main FSX folder

There is in the modules folder a file called FSUIPC.log. Open it with Notepad or Wordpad and see if there are any references to RC in it. If there are any stating a negative comment about RC registration please zip up this file and attach it to a post here.I do not use FSX so I have version 3.75 of FSUIPC which should be similar. Open a flight in FS. Hit the alt key to bring up the menu. Click on Modules. FSUIPC should be listed. Click on that. Check the first tab. If it is similar to version 4 there might be a check mark for multiline messages. That should be checked. Uncheck hide single line messages. This exercise will show (1) if FSUIPC is running which I assume since RC Starts and (2) if the window display options are set correctly. Again, this is what I verify in FS9 and FSX might be different. It can not hurt to try.Also, what version of Windows are you running and is it a 32 or 64 bit version.

Well I got all the way to step 8. There was no transparent window when I went back to FSX. Is there something not loaded correctly?

what version of fsuipc is installed?are you running in full screen or windowed mode?jd

Running Vista 32 bit

FSUIPC4

Welll there is no Module tab on the menu. That is something I was looking for after reading through some of the post in the forum. I used the FSUIPC that came with the program.

just a guess, are you running fsx with the update? that version of fsuipc may not work with unpatched fsxnotably, these lines in the fsuipc.log 32090 Exception 5 "VERSION_MISMATCH", Ref 0, Version 0.60905: Open: SimConnect Version incorrect! 32090 Trying another version of SimConnect ... 32199 Could not link to all needed SimConnect facilities

    49827 **** Retrying SimConnect connection ... ****    49827 Could not link to all needed SimConnect facilities [code 0]    64881 **** Retrying SimConnect connection ... ****    64881 Could not link to all needed SimConnect facilities [code 0]    79935 **** Retrying SimConnect connection ... ****    79935 Could not link to all needed SimConnect facilities [code 0]    94958 **** Retrying SimConnect connection ... ****    94958 Could not link to all needed SimConnect facilities [code 0]   109997 **** Retrying SimConnect connection ... ****   109997 Could not link to all needed SimConnect facilities [code 0]   125035 **** Retrying SimConnect connection ... ****   125035 Could not link to all needed SimConnect facilities [code 0]   140058 **** Retrying SimConnect connection ... ****   140058 Could not link to all needed SimConnect facilities [code 0]   156267 **** Retrying SimConnect connection ... ****   156267 Could not link to all needed SimConnect facilities [code 0]   171274 **** Retrying SimConnect connection ... ****   171274 Could not link to all needed SimConnect facilities [code 0]   186281 **** Retrying SimConnect connection ... ****   186281 Could not link to all needed SimConnect facilities [code 0]   201320 **** Retrying SimConnect connection ... ****   201320 Could not link to all needed SimConnect facilities [code 0]   216343 **** Retrying SimConnect connection ... ****   216343 Could not link to all needed SimConnect facilities [code 0]   231584 **** Retrying SimConnect connection ... ****   231584 Could not link to all needed SimConnect facilities [code 0]   246607 **** Retrying SimConnect connection ... ****   246607 Could not link to all needed SimConnect facilities [code 0]   261723 **** Retrying SimConnect connection ... ****   261723 Could not link to all needed SimConnect facilities [code 0]   276793 **** Retrying SimConnect connection ... ****   276793 Could not link to all needed SimConnect facilities [code 0]   291847 **** Retrying SimConnect connection ... ****   291847 Could not link to all needed SimConnect facilities [code 0]   306277 System time = 09:16:15   306277 *** FSUIPC log file being closedjd

Nope I have not update it. I will ry to update it.

After D/L he patch I got the addons tab on my bar now, with the FSUIPC tab. But I still do not see the RCV screen.

UP AND RUNNING NOW. The patch fixed it. WOW! Wha a great program, Thanks So Much For The Help!