menno

No VoxATC does not control taxi speed. FSX default is about 10 knots. There are some small programs out there that allow you to increase the taxi speed of AI. Google is your friend in this case

Hi all, I am experiencing a persistent problem with VoxATC assigning me an approach into PHJR (John Rogers Field, Oahu, Hawaii) when using the option 'no vectors to approach' in the flightplanExtras menu of VoxATC v6.34 It might be a long explanation but let me try to condense it a bit. It all started when I got fed up with the missing GPS runway 04R approach into PHJR. I decided to create it in ADE X exactly after the examples of standard FSX GPS approaches. Compiled the airport, 'replaced' it for the stock one, ran VoxATC indexer and UT2Bridge. After testing with VoxATC (not ticking the 'no vectors to approach' option) it all works flawlessly. VoxATC assigns me GPS runway 04R approach and gives me vectors to final. Also all AI traffic gets assigned this approach. So far so good. However, I would like to fly without vectors to approach with full published approaches so I loaded the flight plans into the flightplanExtras menu and ticked the 'no vectors to approach' option and saved the flight plans again. Now when I fly those flight plans into PHJR I am not getting assigned GPS runway 04R approach. Strangely enough AI traffic does get the GPS approach, but they always get assigned vectors to approach anyway. What happens to me when I get handed of to Honolulu approach is that (approaching from any direction) I am to expect VOR DME 04R approach and am required to fly to HNL VORTAC and descend to 1000 and report entering the hold! At this point I am unable to request a different approach. Also 1000 feet seems way too low seeing the DME arc of the approach is to be flown at 3000. HNL is actually the transition for the VORDME 04R approach but there is no hold (except for the missed approach hold). Anyway, when I just report entering the hold when overflying HNL I am to report the outbound marker. When I do this I am again able to manually request another approach. I included a screenshot. This VOR DME approach gets assigned with the stock airport (approaches) and the modified airport (with added GPS approach) so the problem is not my added GPS approach. The weird VOR DME approach is also not really the problem. The problem is that I am not assigned the GPS approach in the first place. As I said, long story. However the core problem that I am experiencing is that I am not getting assigned the GPS approach when the flightplan is saved with 'no vectors to approach' ticked. If I do not tick this option all is well and I get the GPS approach and vectors to approach by VoxATC. Does anybody have similar experiences at PHJR or other airports? Does anybody have a solution or an explanation for this behaviour? To be completely clear. I am using VoxATC v6.34 with Airac 1307 rev. 1. I am flying the Carenado Beech 1900D with the standard FSX GNS500. Thanks for your help Best regards, Menno