Tower wont talk to me

[veldthui]

Okay second day of the trial and having trouble. Filed an IFR from NZAA to NZHN. Went through all the prestart stuff okay and was off taxiing. Just before I got to RW05R ground told me to switch to tower 118.70 which I did, they acknowledged me and the screen said taxi to 05R. Well I was there and nothing else happened. Tried waiting another plane came up behind me and was given clearance to line up and blew straight through me... Booommm!I gave up, disabled VoxATC and took off and once I had flown the SID I enabled VoxATC and it picked up okay.Question is why would it not detect that I was at RW05R as it asked and had the red marker lights across??

[cbd80]

Hi. It could be a few things:1. Not enough CPU cycles for VoxATC, so increase the priority using the included tool.2. You didn't get close enough to the runway threshold (it will depend on where the hold short marker has been placed in the AFCAD).3. More than 1 AFCAD exists for the airport. There must only be one for VoxATC to work properly. Do a search and check.4. You don't have to wait for the dialogue text to update. Obviously being new to the product you may not know the phraseology required; you can just say, eg 'Speedbird 123 at runway X ready for takeoff'.Hopefully the above will help. 3 should always be done when airports are first used with VoxATC, as Traffic addons often include their own AFCADs. I would start with 4 and 1 above.Chris

[veldthui]

Hi. It could be a few things:1. Not enough CPU cycles for VoxATC, so increase the priority using the included tool.2. You didn't get close enough to the runway threshold (it will depend on where the hold short marker has been placed in the AFCAD).3. More than 1 AFCAD exists for the airport. There must only be one for VoxATC to work properly. Do a search and check.4. You don't have to wait for the dialogue text to update. Obviously being new to the product you may not know the phraseology required; you can just say, eg 'Speedbird 123 at runway X ready for takeoff'.Hopefully the above will help. 3 should always be done when airports are first used with VoxATC, as Traffic addons often include their own AFCADs. I would start with 4 and 1 above.Chris

1. My specs where in my sig and should show that there are more than enough cycles left over for it.2. I not only got close I went onto the runway and circled it a few times trying to trigger it.3. I will check again but it is an original install with no extras at present.4. I am a real GA pilot so know the phraseology and tried that several times and only kept getting "last aircraft say again" each time.

[veldthui]

Decided to take the PMDG 747 for a fly from Sydney to Brisbane. VoxATC would not let me taxi at all. Everytime I got to the push back and start it would stop there and not allow me to request a taxi. It came up with the text but each time said roger and that was it. The text went away. I had to stop it and do the entire sequence 5 times to get it through once. It is going to have to perform better than that if it wants my money. It is understanding me so no problem with the recognition. Just seems to get stuck a lot.

[cbd80]

Hi. I'm on my iPhone using Tapatalk, which unfortunately isn't showing me your signature.Given that you have had further problems with heavy addons, leads me to think it is a priority issue. Try 'Above normal' or 'High'. Additionally, let VocATC on your last 2 cores.Chris

[cbd80]

Ok. Just got on to see your specs and you're using the same CPU. What your signature doesn't specify is your CPU clock speed?You shouldn't be having such issues with VoxATC.I have my CPU set at 4.4GHz with Hyperthreading turned off and VoxATC running on the last two cores only at normal priority.Chris

[veldthui]

Clocked at 4.2. Today I set the first officer to do all the talking and see if it was better. Same flight. He got past the taxi out problem okay so I left him too it. Trouble was he and the controller at YBBN then got shirty with each other with the FO saying he was contacting her and she was saying please relay your message. It was just going round in circles so I killed it and restarted it. When even the program cant talk to itself there has to be an issue. I am a bit shy at putting out for VoxATC as it is very expensive. If it was half the price then I would have no issues with a few problems but at the price it is it should work 100%.I checked the core usage and there is heaps to spare. FSX running on core 1 at 100% with a bit of offloading onto core 0 for the texture loading. Core 4 running at 5-90% (mostly around 40%)with VoxATC and the other 3 cores basically idle doing sweet FA never getting above 10%.A second flight from NZAA to NZHN got us off the ground but when I kicked in the FO he said Error and that was it. Nothing else happened. Had to shut down VoxATC and restart it again.

[Fenric]

I'm not an expert on the program (I just use it a lot) but this has me stumped.This may be no real help, but next time just try reading your call sign - "Speedbird 152" or whatever - when the ATC is not giving you the attention you need. Since there's no official support here - sigh - I'd suggest an email to Tegwyn via the support address. Perhaps he could visualize what's occurring.Otherwise, if you feel confident to first backup and then to edit an xml file to enable program logging... then check out the details on how to do so in this Spoilery-colored Text...Load \AppData\Roaming\Internal Workings\VoxATC X\VASettings.xml into your favorite xml editor...And change this:<LoggingEnabled Value="FALSE"/>to this:<LoggingEnabled Value="TRUE"/>... then when you start VoxATC it will write lots and lots and lots of files to the same folder with transcripts of what everyone's saying and doing. One file in particular - err.log - will contain your interaction with ATC. That file could be of assistance to Tegwyn if other avenues fail.Regards,

[veldthui]

Tried just using the callsign and all it does then is say "callsign pass your message" to which you can only but reply diregard.