I had another problem yesterday, the controller was vectoring me for landing and all the sudden no more radio contact.I had a message like " Vectoring for I L S approach runway three six" in the VoxATC window and I was waiting for the controller to provide me with more instructions. Vectoring had already started. After a while and 25 miles from the airport, flying in the opposite direction, I understood that something was wrong. Actually I was already worried after flying for 10 miles without any instructions, at 25 miles I was sure that something went wrong.I changed the COM frequency and then went back to the one I had, and all the sudden, I hear the controller's voice once more. He starts vectoring me again, but at the last moment, when I was supposed to make my last turn, the controller was kind of busy giving instructions to other planes. It was too late when I received my last instructions, resulting again in a missed approach.OK, I declare the missed approach, the controller acknowledges the message, and that was it, no more instructions from the him. At this moment, and after flying for like 40 mins around the airport I got tired and ended the flight, frustrated of course :(.It's been 4 days testing VoxATC and at this point I'm unsure if I'll make the step and buy it. I had a very good first impression, followed by small "un-important" bugs and now some annoying ones. I'll give it another chance tomorrow, lets see how it goes.

First, I'm happy for other critical and open eyed customers around as this is a currently silent section of the forums.I can recall such problems like you are reporting in the first example, but I don't recall them as things that always happened but sometimes in the past. For me, the cause was that VoxATC seemed to wait for a proper readback or something and therefor stopped all further instructions.How could this happen? Well, I'm flying with the VoxATC panel off most of the time, so my readback gets done and I don't check if it was understood. Silence from ATC after your readback usually means that everything was ok, so I found myself flying without a doubt but later realizing that the last readback wasn't understood (for whatever reason).So if it told me to "turn left heading 100" and didn't recognize my voice on the readback, it seemed to wait for a proper readback or another click on the PTT while I interpreted this silence as an "ok".So the solution or workaround is to check if the VoxATC panels shows some "hanging" instructions or to just press PTT from time to time to trigger the function where VoxATC just sees your readback as correct (which happens at every second failed voice recog attempt).Maybe the devs can tune VoxATC to just go ahead if you are lazy on the readbacks (in VoxATC's eyes you are lazy if it doesn't recognize you and your words). A real ATC would act the same way I think.As for the go-around. I had such situations where I used this function and reported the go-around after I selected zero "0" on the menu. I then was redirected to the approach controller and the whole stuff started again. So the flawless operation there seems to get triggered on the correct report of that go-around.On the first few attempts I didn't use the menu and received silence like you are describing.The devs have some tools to record a VoxATC session with everything that is commanded, said, understood and finally made. Maybe this tool would help you too if you are looking for the difference between user related or program made errors.As said in the other thread, they might be on the year's end vacation, so be patient if answer takes longer.

I had something similar happen with me on one flight early last week - Cardiff Approach was vectoring me towards an ILS approach when I was forgotten about. I flew 20 miles out to sea before it sunk in that I was not getting any more "control." I had behaved myself and had read everything back properly so I was puzzled. It was a training flight for me though, so I stopped w/o concern.Fortunately I had enabled full logging before that flight and was able to send all of the transmissions and events to the developer. Yes he has taken a holiday; he dropped an email earlier today to say that he hadn't had time to review my logs but he would soon do so. He was concerned about this happening, so I take it that he will be looking into this area. After the first would be fine....Two days ago on a 90 minute flight, it dawned on me that Departure had not passed me off to Center in a reasonable time. I was determined to complete this flight and to land sans control if need be. I played a hunch though and disabled VoxATC, changed frequency to my expected Approach, then re-enabled VoxATC. After it initialized the prompt had me contact Center on the correct frequency. I did so, and the rest of the flight went smoothly. So I'll keep this in my bag o'tricks for the meanwhile.Reading through those logs I've concluded that I had missed my final waypoint on my SID - ergo the Departure controller hadn't handed my flight strip over to the Center controller. Yes, VoxATC creates virtual flight strips that are handed from one contoller to another.I'm only VFR rated, but I've been in the cockpit on enough IFR flights to know what's what and I hear more and can do more in VoxATC than with other ATC solutions - even with its glitches. I've missed waypoints with other add-ons that would result in their controllers wanting me to backtrack 30-40 miles before allowing me to proceed. It appears with VoxATC I can reenable it and continue my flight.

@CoolIP Proper readback was provided and acknowledged, I'm 100% of that. For now I'm flying with the VoxATC window opened as I'm still not familiarized with the procedures and required phrases (hopefully that will change very soon), so I actually saw that the readback was successful in the screen. Regarding the second missed approach, I actually tried to use the 0 menu for requesting assistance to land in the same and other runways. The lady said to me 6 times that she was unavailable :), I literally wanted to kill her :(.@Fenric Yes, the little frequency change then going back to the approach frequency seems to be a good workaround to the problem. That worked for me during this flight, but latter ...I will definitely activate the logging stuff for my next little flight test. The bad part is, I have only two more days to continue my tests. Today it won't be possible for obvious reasons, so I'll report back tomorrow. Perhaps the 7 days trial is not enough ?, and I must say that I've been playing with it a lot more than I normally would because of the holidays.Thank you for everything guys.