I tried creating a flight plan right in P3D and loaded it into PF3 and nothing keeps saying resume on navigation - took forever to get clearance to take off something is definitely wrong here

 

You are clearly having a lot of issues with your setup. Register and post on the official forums and Dave will ask to see your log files so he can resolve your problem. That can't be done here.

To me, the #1 weakness of all ATC programs currently available is that they don't inform you of the runway to expect early enough and if the runway changes, they don't provide a "Plan B".

 

With PFE/PF3 you can request destination airport ATIS info through the simulated ACARs anytime during your flight. From about 200 nm inbound is a good time to do it and be aware if your runway will likely be changes. Yes, even so it can often change at the last minute if your weather engine updates.

 

PF3 had left me on a 6-mile final to runway 16 at 5000' with nothing set up to shoot the approach.

 

Change your FAF distance in the "Tweaks" section to 9nm. I find that a good number that avoids being too high for ILS capture. In your scenario I would have declared a go-around and PF3 would re-vector me to the runway.

You are clearly having a lot of issues with your setup. Register and post on the official forums and Dave will ask to see your log files so he can resolve your problem. That can't be done here.

 

With PFE/PF3 you can request destination airport ATIS info through the simulated ACARs anytime during your flight. From about 200 nm inbound is a good time to do it and be aware if your runway will likely be changes. Yes, even so it can often change at the last minute if your weather engine updates.

 

Nothing wrong with my setup - virgin install of P3D with fsuipc and makerunways - program does not work - resume on navigation all the time sending me to New York and I am suppose to be going south to Rhode Island - funny no tutorials on YT which tells me not many are using this program including the older version - not working not even close

I think one key issue with PF3 is that it makes you catch your ILS at 4 miles from touchdown per default. Which is crazy, isn't it? Normally, I start to descend on ILS 9 or 10 miles out. Why on earth is FAF distance set to 4 miles and FAF altitude to 3000 ASL?

 

That doesnt sound right darem. Check your default FAF distance (7) , I set it to 9 nm and it works well.

 

Also check your generic FAF Altitude is set to something sensible like 2000-3000. You can also set a FAF altitude to whatever number you wish per airport (SIDS/STARS page). This can be useful at airports with difficult terrain as PF3 won't descend you lower than this figure.

 Now if only it could accept aircraft profiles and not expect me to do slam-dunk descents in propliners...  which, of course, is one among several reasons that I keep experimenting and hoping for something better... and so the cycle goes...

 

One of the new features of PF3 is the aircraft profile which allows you to set a climb rate; descent rate; final approach speed (that ATC will instruct you when on finals);and emergency divert airport runway length preference. You can set up as many of these as you like and PF3 will use your climb/descent profiles to base your climb/descent calls on.

 

 

That's one area where RC4 does it better... it tries to give you a long enough final and normally waits until you're low enough before turning you.

 

RC4 will give you vectors for an ILS intercept 13DME out from the arrival runway and an appropriate altitude. Anything less than 10 is not recommended.

Good voices and the weirdness is fairly predictable.

 

 

I concur on the "good voices" part of the default ATC. And it's expandable using EditVoicePack. Many of the 3rd party ATC packages (and also the default) use a large number of WAV files of recorded words and phrases. At this point in time, you'd think that they would be using voice synthesis/text to speech, but I guess that then they would likely have to license a 3rd party SDK to do so. Windows' built-in voice synthesis is actually pretty good, but given all the possible OS versions, that's probably not a versatile option. So, most developers have fallen back on the theory that ATC uses a finite number of words to communicate with pilots and thus pre-recorded WAV files are the best approach.

I completely agree. I had now six flights, not a single one successful at the point when I should start the ILS. I was either too high, to close, or ATC just stopped telling me what to do.

 

I was pretty enthusiastic towards PF3, as I loved PFE, but the handling of the landing phase is much, much worse than in Radar Conctact. In fact, it's a major step backwards from PFE as well.

 

:-(

 

This was not something that came up during beta testing at all. Can you post a screenshot of your flightplan from the PF3 flightplan page and confirm what you have set your generic or airport specific FAF altitude to.

Nothing wrong with my setup -  - program does not work -

 

I don't use P3d. But we had at least one user on beta testing so it clearly does work. If you are interested in finding out what is creating your problems then I have suggested a solution. Posting that it does not work is not helping anyone.

This was not something that came up during beta testing at all. Can you post a screenshot of your flightplan from the PF3 flightplan page and confirm what you have set your generic or airport specific FAF altitude to.

 

I don't use P3d. But we had at least one user on beta testing so it clearly does work. If you are interested in finding out what is creating your problems then I have suggested a solution. Posting that it does not work is not helping anyone.

 

I dont think the dedicated forum is going to make a difference - plenty of help here  - what would be best if the people stating that it works could post some instructions for a short vfr flight to prove it - I have not seen that yet - maybe I should be using a complex aircraft or something - I have been trying with the default B200 - could that be it - I dont know I would think the aircraft would not matter as I have not been told to go to a heading at all which is crazy

The demo version is free so that's no skin of your nose if you don't like it. Also the user guide is free and I think page 126 onwards there's a mini tutorial for setting up an IFR fpl.

 

 

....so that means the interface is the same?

I dont think the dedicated forum is going to make a difference - plenty of help here  - what would be best if the people stating that it works could post some instructions for a short vfr flight to prove it - I have not seen that yet - maybe I should be using a complex aircraft or something - I have been trying with the default B200 - could that be it - I dont know I would think the aircraft would not matter as I have not been told to go to a heading at all which is crazy

 

There is a detailed manual that comes with the product. Have a read of that and then post your flightplan and explain how you are contacting clearance/ground/tower, IFR or VFR.

 

 

One of the new features of PF3 is the aircraft profile which allows you to set a climb rate; descent rate; final approach speed (that ATC will instruct you when on finals);and emergency divert airport runway length preference. You can set up as many of these as you like and PF3 will use your climb/descent profiles to base your climb/descent calls on.

 

One thing I found out is that your copilot completely ignores your descent settings when he's PIC and uses his own. I entered 1200 for the 737 to test things, he uses 2500 nevertheless. With his descent rate, things went well, would I have used the one I entered, I would have been way to high again when approaching.

 

Can someone explain me the differences runway lengths make for the FP?

 

BTW - I sent all logs as requested to the author. Let's see what happens.

....so that means the interface is the same?

 

It is a stand alone program now. You dont use the old PF2000. You load a native FS9/FSX/P3d flightplan directly into PF3. 

If you have an ILS glideslope of three degrees then that is 3,000ft agl at 10nm. PF3 sets the default FAF distance to 7. So I have no idea how some of you got 4.  7nm is measured from the outermarker and puts you about 1nm+ before glideslope capture. Enough time to slow down. And in fact PF3 will tell you to do just that.

 

PF3's default FAF altitude is 3,000ft+airfield elevation. For example LIMF has an elevation of 1,000ft. Therefore the FAF altitude is 4,000. But the FAF altitude is 3,000agl so 7nm FAF distance works perfectly.

 

Other airfields like Kai Tak have a FAF altitude of 4,500 and the glideslope has a different angle. So there 8nm works.

LOWI has a glideslope angle of 3.8 and an elevation of 1,900ft. The FAF altitude there is 9,500 so 21nm FAF distance works there.

 

Richard Sennett, on 08 Feb 2016 - 11:06 PM, said:

Nothing wrong with my setup -  - program does not work -

 

You need to got to the forum. Explain exactly what you think is wrong step by step and Dave will help you out.

program does not work It does. So your setup is wrong or you have done something wrong, I know when things don't work it's frustrating. But allow Dave to sort you out ok. That won't happen on the avsim forums.

I dont think the dedicated forum is going to make a difference - plenty of help here  - what would be best if the people stating that it works could post some instructions for a short vfr flight to prove it - I have not seen that yet - maybe I should be using a complex aircraft or something - I have been trying with the default B200 - could that be it - I dont know I would think the aircraft would not matter as I have not been told to go to a heading at all which is crazy

 If you want Dave to help you, you have to go to the PF3 forum. It's not an avsim forum like RC4. Click on the link below my sig.

Well this explains it - so why would I need this program really - if the aircraft has the plan and following it - not seeing the need for this program other than altitude change which I can handle myself - guess I am missing the benefit

 

Thanks for the help Guys - much appreciated

 

Stated in manual:

 

Shortly after takeoff you will be handed off to Departure control and will then be given further instructions as they guide you away from the airport and toward your first waypoint. At some point you will be told you can 'Resume own navigation' and at that point it is your responsibility to fly the correct route according to your flight plan. It is not within the scope of this document to tell you how to do this but you could use your FMC or GPS to handle directional flight and let your VCP handle any altitude changes given by ATC via your aircraft's auto-pilot. Suffice to say, PF3 does expect you to navigate to each waypoint in your flight plan and you should certainly get to within a couple of miles of each one before turning to the next

One thing I found out is that your copilot completely ignores your descent settings when he's PIC and uses his own. I entered 1200 for the 737 to test things, he uses 2500 nevertheless. With his descent rate, things went well, would I have used the one I entered, I would have been way to high again when approaching.

 

Can someone explain me the differences runway lengths make for the FP?

 

 

 

Hi darem

 

Don't quote me on this as I am not 100% sure but I think the descent rate profile will (should) only affect the point at which ATC will give you descent instructions. If you have set your PF3 for the co-pilot to fly the aircraft I think he will always attempt to meet ATC instructions.

 

Why you did not get a much earlier desvent instruction is obviously the main question. Can you post a screen print of your flightplan. PF3 sets expected cruise altitude settings (and descent ones) for each waypoint in your plan, which you can ammend before connecting to FS. If you had a waypoint with a cruise alt at say 90nm from your destination you would not get descent instructions until that point even if at -1200 v/s.

 

The runway lengths settings only apply if you declare an emergency. ATC wiill vector you to the nearest airport that has a runway theat meets your minimum requirements.

Rich, if you're not at least willing to go to the dedicated forum and interact with the developer to try and figure out your issues, you're probably just better off finding a better alternative or going without an ATC program at all. I've used all of them except ProATCX. None of them are perfect. They all have their quirks. If making an ATC program that was just like real life was easy, it would already have been done and the programmer would be rolling in dough.