A quick question, as there is (currently) no AIRAC support, how do you guys keep your approaches (for example) up to date with the real world? Or does it make any difference? Can I shoot RNAV approaches or VOR approaches in any way I like?

If you want to fly outside of N America the default atc is an absolute no no. It's procedures, terminology etc are completely wrong.

 

Obviously when I can get my video up and running I'll post the link here.

#jvan E: If when you watch it you make any suggestion that the voices are robotic I will personally shoot you at dawn :Shame On You:

You and other will be amazed. I just think you didn't use the correct settings.

 

Looking forward to this video - please let Us know when its done

If you want to fly outside of N America the default atc is an absolute no no. It's procedures, terminology etc are completely wrong.

 

Obviously when I can get my video up and running I'll post the link here.

#jvan E: If when you watch it you make any suggestion that the voices are robotic I will personally shoot you at dawn :Shame On You:

You and other will be amazed. I just think you didn't use the correct settings.

 

Looking forward to that video. And I won't give you my address.  :wink: BTW I didn't create that video: I found it on YouTube and only posted it. 

 

 

I am mainly talking about the voices. If default ATC was really good we wouldn't be looking for an ATC add-on.

 

Yeah, that's right.

We all have a different feelings regarding immersion. For some it's primarily based on natural voices, for some it must be as real as it gets. Some prefer the Copilot to handle all ATC (like currently in PROATCX), some like me enjoy to communicate myself.

I personally enjoy the MCE and RC4 voice connection and will certainly try MCE + PF3 as well.

RC4 also has its shortcomings, but it's very reliable. Quite nice to speak e.g. 'Frankfurt Ground, guten Morgen, Lufthansa XXX with information Mike, ready to copy' and get the appropriate response from RC4 (or soon PF3).

 

I will certainly also try Voxatc, if the developer will be back with an P3D 3.x update.

 

So why not use all three (or four with default ATC), just depending on the mood

 

Mike

A quick question, as there is (currently) no AIRAC support, how do you guys keep your approaches (for example) up to date with the real world? Or does it make any difference? Can I shoot RNAV approaches or VOR approaches in any way I like?

 

Approaches aren't up to date because PF3 only reads the data that's in the sim. There won't be any AIRAC support afaik. You can shoot anything (apart from me   ) anyway you want to. ATC will let you fly the way you want to: if you want ATC to know more about a certain SID or STAR or approach you have to add the info into the add-on or put everything in the flight plan before you file it.

Can I shoot RNAV approaches or VOR approaches in any way I like?

 

Yes you can fly any approach as long as you check the STAR box in the control panel.  This check box will give you cleared to finals as you follow the STAR.  Its similar to what PATCX does but you have a choice in your planning stage.  If you do not check the box then you will receive vectors to the ILS down to the FAF at a certain speed.  I have my speed set to 170 as most ATC in the US have you fly 170 until 5 miles or outer marker.  You then contact tower when established.  

 

PF3 knows nothing about any approaches or arrivals and departures etc its all about creating a plan and following charts etc.  You can actually make certain runways for Landing only and others only open for Takeoff while others can be closed for neither.  (This is actually something I wish RC4 did as I hated being cleared for approach on a small runway).

 

I look at Flightaware or Flightradar24 to see the actives for Landings and Takeoffs then make my plans from that.

Approaches aren't up to date because PF3 only reads the data that's in the sim. There won't be any AIRAC support afaik. You can shoot anything (apart from me   ) anyway you want to. ATC will let you fly the way you want to: if you want ATC to know more about a certain SID or STAR or approach you have to add the info into the add-on or put everything in the flight plan before you file it.

 

Totally useless program if you fly for a good VA that uses up to date Airac data, with current sids , stars, and navaids. Probably OK for flying a Cessna around a local area. 

Looking forward to that video. And I won't give you my address.  :wink: BTW I didn't create that video: I found it on YouTube and only posted it. 

Ok then we can find the poster and both have the opportunity to shoot him at dawn.

In mine I have deliberately included cabin safety annoucements, cabin crew interaction and interaction with ground staff so that punters can measure the differences. Frankly though there's none to speak of. But you do need to set up the voices correctly.

Dave did it this way so that punters can have it totally real, complete with indistinct transmissions. But with the ability to "dumb" it down if they can't actually understand what's being said.

 

A trainee pilot taking his/her RT test for the first time in the UK has to make the correct responses after just hearing one transmission. "Say again" is a luxury you can use only after passing it. Oh and the pass mark is a mere 100%

Totally useless program if you fly for a good VA that uses up to date Airac data, with current sids , stars, and navaids. Probably OK for flying a Cessna around a local area. 

I apply current airac data to my flightplans and fly SIDs and STARs in PF3 perfectly well with excellent results. So what you're saying is utter rubbish sorry!

A quick question, as there is (currently) no AIRAC support, how do you guys keep your approaches (for example) up to date with the real world? Or does it make any difference? Can I shoot RNAV approaches or VOR approaches in any way I like?

If it works the way PFE did, you define the start of approach on the flightplan, and from that point on PFE/3 won't care what you do, until you reach your FAF (Usually around 20nm out,) at which point you are transfered to approach for landing. So it really doesn't need an updated AIRAC to work.

If it works the way PFE did, you define the start of approach on the flightplan, and from that point on PFE/3 won't care what you do, until you reach your FAF (Usually around 20nm out,) at which point you are transfered to approach for landing. So it really doesn't need an updated AIRAC to work.

 That process has been refined a lot since PFE. In PFE it was simply not possible to fly a complex SID without effectively turning PFE off for the duration. PF3 however, knows exactly where you are and if you want to be vectored instead it'll do that too. The old "waypoints are too close" nag still exists but can be turned off as it is in effect totally superfluous now in PF3.

 

In PFE when you were given the "waypoints are too close" message PFE was effectively saying "Don't expect anything serious from me. " And indeed, an IFR fpl from LIMZ to LIMF was effectively the same as the Tour d'Italia except in the air! Now!!! however, in PF3 it works a dream.

 That process has been refined a lot since PFE. In PFE it was simply not possible to fly a complex SID without effectively turning PFE off for the duration. PF3 however, knows exactly where you are and if you want to be vectored instead it'll do that too. The old "waypoints are too close" nag still exists but can be turned off as it is in effect totally superfluous now in PF3.

Never had an issue with departures in PFE either, as it just worked in reverse. You define the end of the departure,  then PFE would let you fly your SID without complaint. I never did get any waypoints are too close issues, as they are removed by PFE when it's compiled.

Never had an issue with departures in PFE either, as it just worked in reverse. You define the end of the departure,  then PFE would let you fly your SID without complaint. I never did get any waypoints are too close issues, as they are removed by PFE when it's compiled.

But Now! you can include all those waypoint in your flightplan. Look at page 126 of the user guide. The ROKIB 6J departure. I can still say to PF3 this is a SID and I'll do it. But the difference now is that the same fpl can go into your a/c navigation computers.

I never did get any waypoints are too close issues, as they are removed by PFE when it's compiled.

Also note that in PF3, no waypoints are removed.  There is an optional warning if your waypoints are too close, but you can disable the warning entirely or ignore it, as you choose.

  All the talk about adjusting and setting FAF's etc..  You can't simply go mixing terminology to suit the program, an FAF is a fixed point on an approach and will vary from approach to approach (traditionally only non precision approaches at that, but can vary from country to country). The vast majority of simmers are already confused enough when it comes to IFR procedures and terminology.

 

 

 

Made me LOL actually. What a crap robotic audio that is. Seriously! Doesn't come CLOSE to default ATC.

 

Then stick with the default, as long as you are happy with american accents everywhere in the world.