I use Radar Contact4 mostly as I find it the most Flexible addon. I tried to get into PFE but it just seems so complicated to set up (you have to mess around for ages and convert the old files before you can use them) and then you get no hints as to what to do next, all requests are numbered 1 to 9 and you have to know what number does what ie 0 to check in with clearance and you have to have another file open that tells you what frequency to use =(. Radar contact4 is much more user freindly and you have a menu right on the screen in FSX that makes selecting options easy. Its also runs right off the flightplan with no need to convert anything. Its not without fault though, if you are running Activesky and have DWC turned on it sometimes makes radar contact run very very slowly. Its a known issue that seems to have no fix. I would use VoxATC but its only got one voice set and sounds too digital.

I also use radar contact and have enjoyed it quite a bit! The interface is more or less the same as the default ATC in FSX however it is a lot more realistic and allows you fly departure procedures and approach procedures, or be vectored instead if you prefer! Theres a lot of options and the voices are pretty dang good too. You can also switch between controlling the radios or having your first officer control them (very useful when hand flying a difficult DP). Definitely give it a look!!

I have to say that PFE in the beginning needs some effort to get used to but everything is well explained in tutorial videos and the manual. When you have done it once, it's as easy as anything else. And yes it does have a lot of options, so whenever you need some fine tuning you're able to do that. Also PFE gives you taxi instructions which is something radar contact doesn't give. PFE comes with a separate tool (pfe displayer) that shows you all the commands you can give during the flight and it also gives you all the frequencies you will need during the flight. The additional sound pack for PFE is also pretty nice. I have never used radar contact though, I just made a decision by looking up reviews/previews and looking around on forums. :)

Excactly! I don't see a point to fly offline (only if dont have a flat rate connection). And if you fly online, you wont need any AI ATC or artificial voices.Vatsim is the answer to your question Andy! ;)

I have got Vatsim but I prefer my airports to be filled with traffic. Over here in Australia I go on at Melbourne or something and there may be 4 or so planes. And been in this timezone sucks, all of you seem to be off when I am on.

I use the default ATC. I like receiving clearance, taxi clearance, takeoff clearance, and the FL changes.I'm too chicken to jump on VATSIM despite having real world flight experience.I guess I should try it having been a memeber since '02.

I only use it to get an ATIS for winds and active runways pretty much.

I have got Vatsim but I prefer my airports to be filled with traffic. Over here in Australia I go on at Melbourne or something and there may be 4 or so planes. And been in this timezone sucks, all of you seem to be off when I am on.

Yes, I have to agree this is a strong argument! Unfortunately...When online (at different times of the day) I see that Australian ATCs are online not too often. :( But there are 2 options for you to consider: 1) come and fly in Europe or USA or even South America, 2) Take the part in Australian vacc (virtual air control governing body in Australia for VATSIM) and become a memmber to give it a good "kick" and gain more traffic and ATC online time! :) I realise that option Nr1 is not really a good one for you, because of that damn time zone. For rest of you, who would like to try, but for some reason haven't done it yet, here is the few things to think about and know: 1) VATSIM ATCs are real people, that will try to follow the real procedures, phraseology and etc.2) They will try to do their best to help you, support and even educate you (ofcourse if not too busy).3) You dont have to be a pro to start using it.4) If you are afraid of too many traffic (stress) in the beginning - just choose less populated airport with an atc online.5) If the heavy traffic is what you are looking for, just go to the biggest, most populated airports plus you can attend many events with inbound/outbond traffic, that happen every weekend and many of them in the middle of the week. Not to mention the big events like crossing the Atlantic and etc.6) If you are not familiar with the charts or procedures - we (ATCs) will help with an advice or we will point you where to get them for free. A lots of different resources are available for training on this.7) If you are afraid of using phraseology (speak to ATC) you can always tell that to ATC and use text instead of the voice.8) You will meet many real pilots and ATCs that are friendly and like to communicate. I havent met a community before, that is so friendly and polite. There are many more reasons, but lets not make it longer right now. Trust me - its a lot more fun to fly online (even if the traffic in some point is a bit less than in RW)!If you still dont feel ready or you have any fears or questions regarding VATSIM, feel free to PM me and I will do my best to consult and support. regards,

PFE, Yes, I made about 50 flights trying to get it to work correctly. I think mabe a couple worked only. I see it as a very old butchered up thing. Support is poor, or nil.Still thinking about RC though. JerryF

I usually use the default ATC along with EditVoicePack.

I use it and think it works pretty good. It's much better than FS2004 ATC. John Floyd

Regarding RC4 there have been performance improvements in FSUIPC and service packs for ASE. Be sure these are up to date. I have not seen ASE mentioned in the RC support forum for quite a while.

Its not without fault though, if you are running Activesky and have DWC turned on it sometimes makes radar contact run very very slowly. Its a known issue that seems to have no fix. I would use VoxATC but its only got one voice set and sounds too digital.

In addition for using an FMC and flight planner with any ATC here's a hint sheet I wrote up based on FSBuild and RC: ------------------------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 6/16/11** 3. 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. The FSB upgrade is free to 2.x version users and is available via your order history on simmarket.com. 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.c...P/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 KMDW that 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.

I switched to VATSIM 2 years ago, and it was the best choice I ever made. It's fun, realistic and a pleasure to fly with. P.S.: If anyone here wants to move to VATSIM but doesn't dare to or doesn't know what to do next, feel free to PM me.

What? .....smiles... I always use VATSIM.

I usually use the default ATC along with EditVoicePack.

Where do I find the details, files, etc. for the EditVoicePack for FSX?Thanks, Bruce.