amazeika

Already tried that as well. The same happens with the default FSX AI traffic planes by completely removing WOAI. Thanks for the suggestion though ;). I was taking a look at RC4 features and didn't like the way they handle SID and STARS. I would really love to solve this as I really like the way SID and STARS are handled on VoxATC using Navigraph data.

I just wanted to add that this is happening with any single AI traffic pushback. I just tried to set my own flight on different airports and I'm having the same issue everywhere.It's sad but for me this is not acceptable, I really liked VoxATC, but this issue + the other one I had (loosing contact during approach) made me change my mind about buying VoxATC. Of course, not everybody is experiencing this issue, so this is probably a conflict with another 3rd party add-on or like suggested, the fact of having the Acceleration pack installed ?. If these issues get fixed, I will definitely consider buying it in the future, but I just cannot go ahead and buy it with the problems I'm currently experiencing.I would to see if the dev can find the source of this issue I'm having, but I'm not buying until getting the desired results, or at the very least promised a refund if this doesn't get resolved. Every single AI traffic plane crashing into terminals instead of being pushed back, not good. Let's hope that the developer can reply back after the holidays. I actually got a response from him regarding the FO problem I recently reported (http://forum.avsim.net/topic/322413-first-officer-problem/).I would like to try RC4 + MCE, but unfortunately there's no RC demo available.

@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.

CoolIP, sorry, I though you were referring to a dev that recommended to disable this for avoiding problems on VoxATC instead of a dev of another app.I agree with you, removing Acceleration is not an option. Nonetheless, the suggestion of clarkey06 is most appreciated indeed, as it provides pointers to what the problem may be.

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.

Yup, the problem he was referring to is the same problem I'm having. Planes end up jumping on their wheels after being "catapulted". Therefore, I'm not the only one having this issue.

Thank you for confirming this :). Yes, I'm using the Acceleration pack.However, I'm not sure I would like to remove the Acceleration thing though. CoolIP, are you using it as well ?, and thank you for reporting back and trying to reproduce the issue ;).

Before installing VoxATC I was using WOAI.I had to rename the FSX default AI traffic for WOAI planes to show. Otherwise only default FSX planes were present. However this weird issue was present with both the default .bgl file and without it, i.e. before I had an FSX MD-80, now I have an American Airlines one, but both get pushed like tomcats from an aircraft carrier towards the airport !.FSX ATC & AI traffic is disabled. Too bad that you can't reproduce this as you are using UT2. It would be nice if anyone else could try this out.Thanks !.

Hello everyone,I just wanted to know if anyone else is having the same issue. I load the demo IFR plan provided with VoxATC (Kansas City Intl to Eppley) with a setting of 50% on traffic density.Just wait until the plane that's located at your right requests a pushback. Instead of a pushback, the plane is literally catapulted towards the terminal . Is it just me, or someone else have experienced this weird behavior with AI traffic ?.

I'm a developer myself (web applications) who's flying instead of coding :), so I perfectly know what you mean. No remote islands or piña coladas for me this year though ...

The problem occurs only when requesting actions to the FO by pressing the PTT button. Otherwise, no problems at all.The solution is to either do ground operations by yourself (my choice) or ask the FO to perform those actions by asking him to do so.However, as CoolIP pointed out, it's far too easy to make a mistake and press the PTT button to ask the FO to proceed with an action when this is actually not required, causing VoxAtc to hang as a consequence.Because of this this I think that we should get the attention of the dev so that this bug gets fixed. I already contacted him, I'm just waiting for his reply.

Hi,Thanks for your reply. This is actually happening at the very beginning while asking him to ask for clearance, etc. During this stage you are required to tell the FO to perform those operations, so you just need to press the PTT button to reproduce the issue.Like you do, I'm testing it in flight for frequency changes, etc. and everything is working just fine as I'm not required to ask the FO to do anything, by pressing K he will just do it.Thanks for taking a look at this.Kind regards.

Hello,I'm currently reviewing VoxAtc and so far I believe that the software is a keeper.However I'm currently experiencing problems with the First Officer feature. VoxAtc freezes while asking the FO to perform actions by just pressing & releasing the PTT key (space). It keeps saying "First officer operating radio", but nothing happens at all.Everything seems to work just fine if I ask the FO to perform the task by talking to him.I'm using FSX under Windows 7. Any idea of what might be causing this ?.I also contacted the developer asking for help.Thanks in advance.