sounds to me that PFE is not in my future and hate RC4 serial number process - life's to short - have no patience for the kind of crap

 

I have never had an issue getting a key for Radar Contact, the process works fine if you use the correct format. nnnnnnnnnn  ! firstname  ! surname

If that does fail for you then JD will soon sort you out via email, may take 24 hours or so but he will always respond

 

You are missing out on a very fine ATC program by not persevering with the registration but all of the available ATC programs demand a certain amount of effort on the users part either in setting up or operating them, patience and the will to read the documentation is certainly needed with all of them.

ATC is not easy stuff either real world or simulated.

Mike W. ,

 

Appreciate the info you've given Richard.  Eventhogh, VOX ATC is not compatible with P3D v3, I have it running fine in P3D v3.1.  Quick question about the PFE voice pack.  Do you know if someone can purchase the expansion pack  ONLY and plug those voices into the VOX ATC voice configs as I am looking for better voices than the VOX POP provided.  Thanks

Vincent,

              While you can purchase the voice packs separately from Simmarket, they won't work with VOX. Vox uses a voice recognition program that requires voice sets like Ivona. The PFE voice packs are wave files. I wish you could use them it would make VOX even better. I have VOX working in P3Dv3 but with some anomalies. I had a lot of sound looping on my last flight along with the Oceanic frequency issue. I'm really hoping that Tegwyn hasn't abandoned further development of VOX.

I am not finding a P3D compatible PFE version to purchase - are you using migration tools

 Go onto the PFE forum http://www.ocs-support.co.uk/forums/viewforum.php?f=4

They'll tell you to set it up.

 Go onto the PFE forum http://www.ocs-support.co.uk/forums/viewforum.php?f=4

They'll tell you to set it up.

 

Ah thanks for the info

Thanks Jarkko,

 

Have used the IVONA voices and agree they are good...(I am currently under their 30 day trial) and hoping to find something a little  less expensive.  I thought maybe the PFE expansion voices could be plugged into my VOX voice configs and thus find a cost effective solution to the VOX POP 4 voices provided by VOX ATC.  Thanks again

Mike,

 

Thanks for the information.  Will probably go with buying the IVONA voices ( I already love the aussie)..she's my fave controller  (gotta love her "RAAGGAA" ) .  Hope you get the Oceanic freq thing worked out.  I only fly US and I really enjoy the VFR and AI traffic provided by VOX.

How much are the ivona voices and where do you purchase them struggling to find

Eventhogh, VOX ATC is not compatible with P3D v3, I have it running fine in P3D v3.1.

 

Completely functional?

 

Please outline the steps you used to install it in P3D V 3.1

 

Chas

I downloaded the IVONA voices from a link I found thru Google... I don't have it available right now.  I am currently in week 2 of a 30 day free trial, but I think the info said they were $28.00 US per voice used (not positive about this quote).

 

I installed VOX ATC to my Prepar3D v3.1 by activating the EMT tool and pointing the installer to my FSX, then disabled my EMT tool.  I have had no issues...(there is one trick required to have VOX indexer recognize aircraft not located in P3D/simobjects/airplanes); but a little use of copy and paste can overcome this.

 

 

I primarily use VOX for VFR flights and short range IFR. I manage the radio and do not use the FO option.  As most of my flights are GA, I prefer flying as a single pilot operation and being able to use my voice and communicating with many different ATC controllers provides the realism I prefer over other similar add ons.

 

Another nice feature for us VATSIM flyers.  When I fly on VATSIM, if no controllers are available, I can use VOX ATC with VOX's provided AI traffic and if a VATSIM controller comes on line, I simply respond to VATSIM ATC and ignore VOX.  You just have to be careful not to transmit your voice to VOX ATC over the VATSIM network

installed VOX ATC to my Prepar3D v3.1 by activating the EMT tool and pointing the installer to my FSX, then disabled my EMT tool.  I have had no issues...(there is one trick required to have VOX indexer recognize aircraft not located in P3D/simobjects/airplanes); but a little use of copy and paste can overcome this.

 

1.what if you don't have FSx?

2.cut what from where ...paste to where?

 

Thanks,

Chas

1.what if you don't have FSx?

2.cut what from where ...paste to where?

 

Thanks,

Chas

 

 

1.  If you don't have FSX than I assume you cannot use the EMT tool...

2.  The cut and paste involves getting a copy of the desired aircraft from outside the P3D directory into the P3D/simobjects/airplanes directory.  (Be aware !!!! This goes against LM's desire to keep add ons from being installed within the main P3D directory) 

Just jumping in to correct a few wrong assumptions:

 

* ProATC/X does indeed use the phonetic alphabet.  As Jarkko stated, you have the option to use "plain" letters or phonetic letters... the implementation is not 100%... for example, I still occasionally hear "A" instead of Alpha; but not very often.

 

* Approach Control does NOT issue a STAR... the Center (or "Control" in Europe) does.  Maybe if you're flying low, a neighboring Approach Control may issue one -- but that is definitely the exception to the rule.  STARS are issued to transition from the enroute environment to the terminal environment and since most STARS begin well outside of approach control airspace, it's primarily a center function.  While ProATC/X does handle STARS better than any other ATC program, it is still far from perfect.  It currently issues descent prior to issuing the STAR when it should actually be issuing the STAR and providing a "descend via" clearance (since "descend via" is pilot's discretion, that would also make things easier for folks that tend to over-rely on VNAV for descent).  I've had some lengthy discussions about this with the ProATC developers... so hopefully it will be addressed in a future release (although things have also grown disturbingly quiet at ProATC/X in the past couple months since the last patch).

 

* Transition altitudes are provided by ATC... sure the pilot can look them up; but it's an ATC function.  ProATC/X handles this the best using AIRAC data.

 

* As Jarkko said, U.S. and European SIDS/STARS are implemented quite differently.  One example is that U.S transitions tend to be on the front of a STAR (between an enroute waypoint and the STAR) while European transitions are on the back (in between the STAR and instrument approach).  While European STARS normally "connect" seamlessly with the approach in use, the chance of flying the complete route without a vector is slim to none in the real world.  Controllers use vectors to sequence arrivals, so they will yank you off the STAR and vector you to final the vast majority of the time (unless there are no other arrivals).  Let me say that again... European Controllers vector too !!!  Vectoring is still a major weak point for ProATC/X. If it can't figure out a way to connect to the IAP, it gives a lame/confusing attempt to vector to final; but it's pretty bad and RC4 does it a whole lot better.

 

* IMO, PFE has the best audio presentation of the three... but it is way too clunky to set up.  You can easily spend more time setting up a PFE flightplan, entering transition levels, calculating descent profiles, etc. than actually flying.

 

The fact is that none of these programs actually provide real ATC.  None of them adequately separate and sequence aircraft -- which is the whole reason to have ATC in the first place.  Until LM or Dovetail address the internal AI and ATC processes, third-party ATC will always have problems.  With that said, there are plenty of improvements that can be made on what we have right now... but third-party progress seems to be glacial as of late.  I would love to see somebody like HiFi take on ATC...they've already broken so many barriers related to weather and they already provide a pretty decent "ATIS"; but I'm afraid ATC might be a little too far outside their box.

1.  If you don't have FSX than I assume you cannot use the EMT tool...

2.  The cut and paste involves getting a copy of the desired aircraft from outside the P3D directory into the P3D/simobjects/airplanes directory.  (Be aware !!!! This goes against LM's desire to keep add ons from being installed within the main P3D directory)

 

1...but I have tons of FSX ad-ons

2.how much of the aircraft?

 

Thanks

Chas

The fact is that none of these programs actually provide real ATC.  None of them adequately separate and sequence aircraft -- which is the whole reason to have ATC in the first place.

 

Really well spoken sir

 

 

Chas

Why no mention of PFE?

1) Generates it's own ATIS: Yes

2) Assigns real world SIDs/STARs based on AIRAC (from Navigraph/Aerosoft): It's not a fpl generating programme. So "you" assign real world SIDs/STARs based on AIRAC to PFE.

3) Assigns real world transition levels automatically based on AIRAC (from Navigraph/Aerosoft): Again it's not a fpl generating programme so "you" assign to PFE transition levels for centres, FAFs, FAPs and airports.

4) Uses FAA phraseology when flying in the US and uses ICAO phraseology when flying in Europe: Yes it most certainly does. It is fully ICAO compliant compared to ProATC which is not.

All of the ATC programmes have a few ragged edges. But, RC4 is finished with no further development. VOX ATC is fine if you enjoy talking to a computer. ProATC is ok for non-pilots who don't fly outside of FAA jurisdiction. PFE will always be updated. And it works with FS9, FSX P3D and even XPL.

This is wrong! PFE is not updated with Navigraph or Aerosoft, and in fact it's Airac database is rather old, dating back to FS2002/2004 or older days. It does update it's airport data (Runways, taxiways gates) via the Makernwy utility. but it's AIRAC is currently not updateable. PROTC-X is the only ATC program that AIRRAC can be updated via Navigraph. (don't know about VOXATC)

 

PFE does not assign actual SIDs/STARS at all While you can assign names to them in the menu even by runway, no actual SID/STAR route is assigned. You must include a SID/STAR in your flightplan, you then manually set a end waypoint for your SID and an Start way point for your Star. Once you reach that point PFE will allow you to fly the rest of the flight down to FAF without complaint, This allows you  to use STARS in ICAO as well as FAA regions. PROATC-X and I think VOXATC is the only ones that actually assigns SIDs STARS based on weather. for both ICAO and FAA regions.

This is wrong! PFE is not updated with Navigraph or Aerosoft, and in fact it's Airac database is rather old, dating back to FS2002/2004 or older days. It does update it's airport data (Runways, taxiways gates) via the Makernwy utility. but it's AIRAC is currently not updateable. PROTC-X is the only ATC program that AIRRAC can be updated via Navigraph. (don't know about VOXATC)

 

PFE does not assign actual SIDs/STARS at all While you can assign names to them in the menu even by runway, no actual SID/STAR route is assigned. You must include a SID/STAR in your flightplan, you then manually set a end waypoint for your SID and an Start way point for your Star. Once you reach that point PFE will allow you to fly the rest of the flight down to FAF without complaint, This allows you  to use STARS in ICAO as well as FAA regions. PROATC-X and I think VOXATC is the only ones that actually assigns SIDs STARS based on weather. for both ICAO and FAA regions.

 

Where did I say that PFE does that? Read it again and find the word "you!!"