Okay, since there hasn't then any chatter here for five days I thought I would just throw this at y'all.

 

I have become in enamoured with… I won't say fallen in love with VOXATC jusssst yet…

 

When I choose to use a first officer....my FO has not been popping up lately....

 

I must mention that I have recently added about eight extra voices including three AT&T TTS voices, and one Ivona voice, Jennifer, which was an ancient purchase, but seems to work.

 

Could that be influencing things… I.e. taking up more memory then was planned by the programmer?

 

What am I doing wrong ?

 

Chas

Chas,

          I have 4 ATT voices and 4 Ivona voices and I haven't had that problem show up. I have 8GB of memory. Vox, since this last version was released can get funky at times. A few flights ago, I couldn't get delivery to respond. The last flight ,it was fine.

When I choose to use a first officer....my FO has not been popping up lately....

 

 

just a few ideas...

1.double check that you still have 'first officer available' ticked in the voxatc settings. maybe installing the other stuff reset it somehow

2. it think first officer is only available in 'airline' setting for the callsign as well although i'm not sure but it's something to try perhaps..

 

cheers

-andy crosby

I had an odd thing happen with Vox and P3D. I was doing a flight and everything was fine until I got to the runway. There was one aircraft ahead of me at the hold line. He never moved and there were no instructions from the tower. An aircraft called on approach and the tower never responded. I guess the controller went to lunch.

I had an odd thing happen with Vox and P3D. I was doing a flight and everything was fine until I got to the runway. There was one aircraft ahead of me at the hold line. He never moved and there were no instructions from the tower. An aircraft called on approach and the tower never responded. I guess the controller went to lunch.

Had this problem quite frequently on 6.46.

Had this problem quite frequently on 6.46.

 

This happens after the Fatal error message. Sometimes, the message stays for a short time and it is easy to miss.

Naif,

        I did get a Fatal Error message before that. I thought I read where you could ignore it and proceed. I guess not. What caused the fatal Error message I don't know but it seems to happen more frequently with this version of Vox.

"What caused the fatal Error message"

 

No flight plan loaded .. for one.

Vaughan,

                No, I had a flight plan loaded. The Fatal Error message came after I received my clearance. Very odd.

"What caused the fatal Error message"

 

No flight plan loaded .. for one.

I have been having so many error messages with the latest versions that I stopped using it. I even contemplated going back to 6.20, the last stable version for me.

Vaughan,

                No, I had a flight plan loaded. The Fatal Error message came after I received my clearance. Very odd.

 

Did you check your Windows Event viewer to see the Module Name that caused the problem?

 

I have been getting Fatal Error when departing KDTW just after takeoff like 500 feet or so.

I had the Palace7 departure ... right after I was told to head for my first waypoint .. got the error.

 

The developer isolated the problem to bad SID procedures.

 

Did your clearance include a SID?

 

Which airport?

 

My problem could be duplicated ....

 

Can you duplicate ypur error condition(s)?

I reinstalled 6.49 and I'm getting ready to try the same flight again. It was out of Sydney (YSSY) with a SID. We'll see if the same thing happens again.

I reinstalled 6.49 and I'm getting ready to try the same flight again. It was out of Sydney (YSSY) with a SID. We'll see if the same thing happens again.

 

Any info?

I haven't had a chance to try it yet. Hopefully this afternoon.

Well I have flown 6 flights now with 6.49 and I love the improvements made but I am highly irritated with a new bug.  I don't know if I did something wrong or others have this but once I switch to the Approach and make contact they will give my initial vector and altitude to descend to and assign me a runway and that is the last I hear from them.

 

Example:  Last night I was arriving in Phoenix Arizona on the Bunter Two arrival.   When I got to bunter you vector off at 225 degrees and you get approach control on the horn.   "Southwest 4096, Turn right heading 035, descend and mainting 7000.  Expect runway ILS 7L, blah blah blah"

 

Heading 035... is BACK the way I came... not only that.. but at 7000 feet I was getting terrain warnings from the mountains.   I was having to flying through the valleys here.  No word from ATC.   25 minutes pass, still no word.. I let it go that long just to see if it would ever tell me to turn back to the airport.  Never.  I had to take matters into my own hands.

 

That's 3 times it has done this.  It's almost like it is trying to send me back to the first waypoint that starts the STAR arrival.  If this is what it is doing, and it looks like it is, this needs to be fixed immediately.  That is a huge bug.     

 

I can't think of anything I would have done to make it not work.  All my airports are full indexed.   The latest AIRAC cycles are loaded for it to use.   Anyone else get vectored AWAY from the arrival airport?