OnCourse Software

Welcome to our Product Support Forums

Disable runway change

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 2 of 2  [ 12 posts ]
Jump to page « 1 2
Author Message
martinlest
Post subject: Re: Disable runway change
Posted: Sat Aug 25, 2018 5:56 pm
Offline
 
Posts: 1308
Joined: Sun Dec 26, 2010 3:33 pm
 
I hadn't noticed that... not sure whether it will work as planned in X-Plane (via the plugin), but I have switched it to '0' to see what happens. Thanks.


Top
Profile Quote
Dave March
Post subject: Re: Disable runway change
Posted: Sat Aug 25, 2018 7:13 pm
Site Admin
Offline
 
Posts: 6095
Joined: Mon May 18, 2009 6:22 pm
Location: Sawtry, Cambridgeshire. UK
Contact: Website
 
Well it was in the 'Version History' document that resides in your PF3\Help folder, which is udated with each release. I really would recommend everyone reads this if nothing else, as you may well be missing out on a lot of new and useful features.
Quote:
ADDED some new options to the 'Advanced Tweaks and INI File Options' display.

Under the 'Approach' section YOU can now decide how many times PF3 should recheck to see which runway is 'active' at your destination airport and how long to wait between these checks. Prior to these changes PF3 would check to see if any AI were currently using any of the runways and obviously use the same one if they were. However, if PF3 could not detect any AI it would use the airport's wind direction to determine the correct runway to use. It would then go into it's 'recheck' mode and check a maximum of 5 times at 60 second intervals to see if AI suddenly became active. In which case, if this was a different runway, ATC would instruct you there had been a runway change. Runway changes could also be triggered if your weather program changed dramatically during the approach. These new options enable you to set the maximum number of times PF3 should recheck for an active runway (anything between 1-9) and also the time interval between these checks (anything between 30-900 seconds). Setting the retries value to ZERO would in fact turn this feature off completely so you would get the first runway PF3 detected and if there was no AI detected and PF3 used the 'current' wind direction you may be in for a surprise on reaching your destination if the wind changed and/or AI traffic suddenly became active on another runway. Still, as they say, the choice will be yours. The default settings for these options are 5 retries at 60 second intervals.

_________________

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
Display: Sort by: Direction:
Post Reply   Page 2 of 2  [ 12 posts ]
Return to “PF3-ATC at its best” | Jump to page « 1 2
Jump to: