October 26, 20205 yr Team The inclusion of the titled parameter in the VASettings.xml does not seem to function as it did in v742 ..... whereby earlier or later TOD's would be calculated by vox to suit arrivals different to the default 2.5 ratio direct to the destination. Further it seems (manual) requests for descent will not be granted .... & are delayed and subsequently instructed by vox on passing the 2.5 calculated (eg 90nm direct from FL360). Comments / advice will be appreciated. One needs some sort of flexibility to follow rnav star profiles where downwinds and / or TMA restraints apply. With v742, i felt it simpler to rely on a pilot initiated request although that often attracted nagging from vox if the vnav profile was shallow. for now, cheers john martin
October 26, 20205 yr Could you make contact through the VoxATC.com contact page, this might require some diagnosis.
October 26, 20205 yr You won't be able to send the logs on initial contact through the contact form, just use the contact form to get the ball rolling.
October 27, 20205 yr Author have done but no receipt seen ??? email also sent with files !! for now, cheers john martin
Archived
This topic is now archived and is closed to further replies.