OnCourse Software

Welcome to our Product Support Forums

2 more minor procedural bugs

PLEASE NOTE:

If you are reporting an issue with PF3 please remember to Zip and attach the Debug_Monitor.log file from your PF3\Logs folder. Thank you.

Post Reply   Page 1 of 1  [ 8 posts ]
Author Message
Mike T
Post subject: 2 more minor procedural bugs
Posted: Sun Aug 06, 2017 3:34 pm
Offline
 
Posts: 39
Joined: Sat Aug 27, 2016 11:19 pm
 
Bug 1: Prior to ATC beginning the STAR clearance to final at the transition fix I am handed off to approach while still at cruise - which is too high to be handed off to approach. I've verified this twice on two separate flights. As I am approaching my STAR transition fix Center now hands me off to Approach which delivers the STAR instructions instead of center giving it. This is more of a distraction than broken functionality because the end result is still the same, however it is strange (and incorrect) to be told to contact approach at FL350 :-) .

Bug 2: This one has always been there but I'm surprised that no one has said anything. During ATC chatter aircraft report that "Airline <x> is out of <altitude>", which is only one half of the required sentence. The correct comms should be "Airline <x> is out of <altitude> for <altitude>." Again, more of a distraction than broken functionality, but every time I hear it I finish the sentence in my head and wonder if this can be programmatically fixed or it is the way it is because it cannot be fixed.

Again, I'm flying in Prepar3d v4 and I don't remember Bug 1 in FSX. Bug 2 is legacy and has always been there through both product evolutions.

Mike T.


Top
Profile Quote
reecemj
Post subject: Re: 2 more minor procedural bugs
Posted: Sun Aug 06, 2017 4:20 pm
Offline
 
Posts: 68
Joined: Sun Aug 21, 2016 4:38 pm
 
Same here yesterday only flying at 7000. Got handed to approach 150 miles from airport. No departure hand off.


Top
Profile Quote
Dave March
Post subject: Re: 2 more minor procedural bugs
Posted: Sun Aug 06, 2017 5:19 pm
Site Admin
Offline
 
Posts: 6121
Joined: Mon May 18, 2009 6:22 pm
Location: Sawtry, Cambridgeshire. UK
Contact: Website
 
reecemj wrote: *  Sun Aug 06, 2017 4:20 pm
Same here yesterday only flying at 7000. Got handed to approach 150 miles from airport. No departure hand off.
I'd like to see the log file for that flight please

_________________

Cheers

Dave March

Email: dmarch@oncourse-software.co.uk

I don't know if my memory is getting worse as I get older...
...I just can't remember how it used to be!

[ img ]


Top
Profile Quote
Dan77
Post subject: Re: 2 more minor procedural bugs
Posted: Sun Aug 06, 2017 5:21 pm
Offline
 
Posts: 766
Joined: Sun May 05, 2013 2:22 am
 
reecemj wrote: *  Sun Aug 06, 2017 4:20 pm
Same here yesterday only flying at 7000. Got handed to approach 150 miles from airport. No departure hand off.
You should have been handed from Departure to Center when passing through Center altitude, which is user-configurable. Please post the logs so we can have a look.

Last edited by Dan77 on Sun Aug 06, 2017 5:42 pm, edited 2 times in total.

_________________

Dan

[ img ]


Top
Profile Quote
Dave March
Post subject: Re: 2 more minor procedural bugs
Posted: Sun Aug 06, 2017 5:21 pm
Site Admin
Offline
 
Posts: 6121
Joined: Mon May 18, 2009 6:22 pm
Location: Sawtry, Cambridgeshire. UK
Contact: Website
 
Mike T wrote: *  Sun Aug 06, 2017 3:34 pm
Bug 1: Prior to ATC beginning the STAR clearance to final at the transition fix I am handed off to approach while still at cruise - which is too high to be handed off to approach. I've verified this twice on two separate flights. As I am approaching my STAR transition fix Center now hands me off to Approach which delivers the STAR instructions instead of center giving it. This is more of a distraction than broken functionality because the end result is still the same, however it is strange (and incorrect) to be told to contact approach at FL350 :-) .

Bug 2: This one has always been there but I'm surprised that no one has said anything. During ATC chatter aircraft report that "Airline <x> is out of <altitude>", which is only one half of the required sentence. The correct comms should be "Airline <x> is out of <altitude> for <altitude>." Again, more of a distraction than broken functionality, but every time I hear it I finish the sentence in my head and wonder if this can be programmatically fixed or it is the way it is because it cannot be fixed.

Again, I'm flying in Prepar3d v4 and I don't remember Bug 1 in FSX. Bug 2 is legacy and has always been there through both product evolutions.

Mike T.
For Bug #1 isn't that down to you're flight planning? i'e You reach the STAR transition at cruise?

I would like to see the log file for that flight please

For Bug #2 I'll certainly take a look but again would need the log

_________________

Cheers

Dave March

Email: dmarch@oncourse-software.co.uk

I don't know if my memory is getting worse as I get older...
...I just can't remember how it used to be!

[ img ]


Top
Profile Quote
ThomasAH
Post subject: Re: 2 more minor procedural bugs
Posted: Sun Aug 06, 2017 6:00 pm
Offline
 
Posts: 988
Joined: Tue Dec 24, 2013 12:27 pm
 
Dan77 wrote: *  Sun Aug 06, 2017 5:21 pm
reecemj wrote: *  Sun Aug 06, 2017 4:20 pm
Same here yesterday only flying at 7000. Got handed to approach 150 miles from airport. No departure hand off.
You should have been handed from Departure to Center when passing through Center altitude, which is user-configurable. Please post the logs so we can have a look.
And the default center altitude is 8000 feet, so what you experienced will always happen, unless you either use a slightly higher cruise altitude or lower the center altitude.

_________________

[ img ]


Top
Profile Quote
Mike T
Post subject: Re: 2 more minor procedural bugs
Posted: Wed Aug 09, 2017 2:09 am
Offline
 
Posts: 39
Joined: Sat Aug 27, 2016 11:19 pm
 
dmarch wrote: *  Sun Aug 06, 2017 5:21 pm
Mike T wrote: *  Sun Aug 06, 2017 3:34 pm
Bug 1: Prior to ATC beginning the STAR clearance to final at the transition fix I am handed off to approach while still at cruise - which is too high to be handed off to approach. I've verified this twice on two separate flights. As I am approaching my STAR transition fix Center now hands me off to Approach which delivers the STAR instructions instead of center giving it. This is more of a distraction than broken functionality because the end result is still the same, however it is strange (and incorrect) to be told to contact approach at FL350 :-) .

Bug 2: This one has always been there but I'm surprised that no one has said anything. During ATC chatter aircraft report that "Airline <x> is out of <altitude>", which is only one half of the required sentence. The correct comms should be "Airline <x> is out of <altitude> for <altitude>." Again, more of a distraction than broken functionality, but every time I hear it I finish the sentence in my head and wonder if this can be programmatically fixed or it is the way it is because it cannot be fixed.

Again, I'm flying in Prepar3d v4 and I don't remember Bug 1 in FSX. Bug 2 is legacy and has always been there through both product evolutions.

Mike T.
For Bug #1 isn't that down to you're flight planning? i'e You reach the STAR transition at cruise?

I would like to see the log file for that flight please

For Bug #2 I'll certainly take a look but again would need the log
Hi Dave:

Bug #1 - Yes, I almost always start my transition to the STAR at cruise since most STARs are designed that way. For instance I'm flying from KSEA to KLAX using the REBRG.IRNMN1 transition. REBRG is crossed at my assigned FL (FL370 in this case) and there are various lower crossing altitudes along the star. The problem with PF3 would be being told to contact approach since I'm still over 100+ NM from the airport. I'd be too far and too high to contact approach, so, it would be center that would tell me to "continue via the IRNMN1 approach" and not approach. Approach should not be contacted until you are within 30 to 50 nm of the airport and generally below 15,000 ft - even though there are some approach sectors that go up to 20,000 in crowded airspace. Either way, definitely not at FL370 at 150 nm from the airport :-)

Bug #2 - I'll have the logs for ya as soon as I land.


Top
Profile Quote
Dan77
Post subject: Re: 2 more minor procedural bugs
Posted: Wed Aug 09, 2017 3:14 am
Offline
 
Posts: 766
Joined: Sun May 05, 2013 2:22 am
 
Mike T wrote: *  Wed Aug 09, 2017 2:09 am
Bug #1 - Yes, I almost always start my transition to the STAR at cruise since most STARs are designed that way. For instance I'm flying from KSEA to KLAX using the REBRG.IRNMN1 transition. REBRG is crossed at my assigned FL (FL370 in this case) and there are various lower crossing altitudes along the star.
We don't have logs or your flight plan but in general your last PF3 waypoint should be about 25-40 nm out. I assume REBRG (more than 130 nm out) is not the last waypoint in your PF3 flight plan. If the STAR is long, the early STAR waypoints should be included in your PF3 flight plan, and in this case I would probably have IRNMN (about 31 nm out) as my last PF3 waypoint. You can designate REBRG as the beginning of your STAR on the waypoint page and enter the crossing altitudes from the chart.

_________________

Dan

[ img ]


Top
Profile Quote
Display: Sort by: Direction:
Post Reply   Page 1 of 1  [ 8 posts ]
Return to “PF3-ATC at its best”
Jump to: