Starrfoxx

I have not seen this in my flights with VoxATC. I believe it says somewhere in the documentation that departure and arrival airports are the ones with generated traffic, so there wouldn't be anything in between. VoxATC is great for short flights, but for longer ones you might want to use something else such as PFE. I have both, and I like them each for different reasons.

That could be a "launcher" executable. Download it, start it, and then it downloads from that program. I've seen various other programs do that.

That is weird. Is this happening at all the airports with ATIS, or just one specific place? It could be a problem with the AFCAD file. Perhaps the ATIS wasn't programmed in, or it was programmed on the wrong frequency. It may not be the fault of Vox at all.

Are trying to use Com 2? If so, it doesn't work. All communication has to be done on Com 1; ATIS included.

You've got to create a flight plan, convert it through PF2000, and load it up into PFE. I look at it as if I had to really file a flight plan anyway. With PF2000, it acts like FSS while it's converting and tells you your flight plan is approved. I'm not sure how RC4 works, but I know with VoxATC you have to create a flight plan as well so that the program knows where you are flying from and to. It seemed cumbersome at first, but after a few times I got the hang of it and it's not much of a big deal now. The extra time is worth it for me.

Do you have any FS9 AI traffic, such as World of AI? If so, FSX will use it and ignore your FSX specific AI. To fix it, you'll want to convert your FS9 AI Traffic to FSX file format.

I haven't found a way to disable the ATC, but you can go into "sounds" and turn the Voice option off.

I haven't tried it, but I've had trouble with one of my custom CRJ-700 aircrafts with my virtual airline. I haven't figured the problem out in the .cfg file, so I had to remove it, so that the indexer would work properly. I've had to fix other planes by removing aliases and putting the actual folders/files in the particular aircraft folder for Vox to read it right.

I used Airport Design Editor (ADE) to look up the BGL's. Grand Canyon is KGCN. On both of the above examples, a name correction could be done so that it would read: Grand Canyon National Park instead of Grand Canyon Natl ParkDetroit Metro Wayne County instead of Detroit Metro Wayne Co That still doesn't help with the Vox controllers trumping the name to "Canyon" or "Metro", unless it's supposed to do that.

One thing that I really love about Vox (and default ATC) is being able to hear the name of the airport (even small ones). I've noticed a couple of airports where Vox does not read the entire name, though. For example:* Detroit Metro (KDTW) refers to itself as "metro"* Grand Canyon National Park Airport refers to itself as "canyon"So when calling ATC, I'll have to refer to them as "Metro Ground" or "Canyon Ground'.Is there a reason why this is happening, and can this be fixed so Vox reads it correctly?

Last night I had an enjoyable flight from Flagstaff to Grand Canyon, Arizona airport. I flew VFR and had no trouble with ATC or AI Traffic. Everything looked good. I had traffic set to 20% this time. I'll let you know if I have any other trouble. Hopefully turning down the traffic will be the trick.

I recently bought PFE 2.14 with the Voice Expansion and also the free Enhancement pack. I got it mainly for FS9 on my laptop, but I'll use it here and there on FSX on my desktop (where I use VoxATC mostly). All I have to say is .... awesome. There are TONS of voices, and it is just neat to hear something like that. I also flew from the US to Canada, and it was neat to hear controllers with French accents telling us Americans what to do and where to go. It's been a very enjoyable experience. It does take some patience to get set up, but I find it totally worth the investment.

I've got the latest PFE and Windows 7, and I didn't need to run it that way. I did have to install it as an administrator, though, and took some patience to get installed correctly. Works fine for me now.

VoxATC is also missing. I use both VoxATC and PFE, depending on the flight I'm doing.

This will happen to me also, especially if I start going through too many other windows that might have sound attached to them. It'll cut my VoxATC sound in half and will be harder to hear.

Maybe there was an event going on in Flagstaff and nobody told me. The flight from Sedona to Flagstaff isn't very far. It took about an hour to get there, so I don't think it has anything to do with the flight time. Originally I thought it might have been with the first example, or maybe it was happening at heavy traffic airports. Now the amount of traffic looks about right, for 60%. The problem is that they are all grouped together, instead of being spread out and flying their flight plans. That's the one thing that really needs to be worked on with VoxATC and that is the AI schedules. If they were flying their schedules, then I probably wouldn't get this massive cluster frell in the sky. But since Vox doesn't understand AI schedules, it just generates the AI and they all seem to be taking off and having a pow wow in the sky.

Just to get back on topic with this thread, I made another flight from Sedona to Flagstaff in Arizona. ATC was fine for most of the flight (I had to repeat myself a few times to ATC, but not much). Flagstaff is not a big airport, but it sure did generate a lot of traffic. I had VoxATC set to 60%, and maybe that was the problem? I'm going to set it to 20% on my next flight and see what happens. I have the demo of FS Commander 9, but I can't get it to work and show the AI traffic. I'd like to see how it shows up on that program and post a snapshot of that also.

How do the SIDs/STARs work in Version 6? I realize ATC will assign you one when leaving/arriving the airport, and I assume it would be by name. Is it based on which direction you are going to/coming from, the runways in use, or both? Is it up to you to look up the SID/STAR and fly it correctly, or does ATC vector you along the SID/STAR? Finally, can the SID/STAR database be updated when things change with the procedures?

Did you install the 32 bit version of UIAutomationCore.dll in your main FSX folder? I was having crash problems too, until I did this. It seems to run okay now.

Forgive me for sounding naive, but if your flight plan is to an airport to the east and ATC assigns you a SID to fly that goes west based on Runway 27, wouldn't it be counterproductive? Wouldn't it be better to just be vectored around? Or could you just ask ATC to depart from Runway 9 and then it'll give you the correct SID that corresponds with your flight plan?

According to the VoxATC Update News for 6.05: The 'old style' Sids and Stars defined with Sid/Star setup or Wizard now work http://www.voxatc.com/Home.aspx/News Wouldn't you want to use the Wizard if you wanted to fly a certain SID/STAR and not have ATC assign it to you, or can you just call ATC for the procedure now?

According to the manual, you still can use the SID/STAR wizard. Or is it simply out of date, now that Vox will assign you one?

I had this problem last night. I was flying a practice flight from Detroit to Toronto using VoxATC to prepare for an upcoming Vatsim event. Using 5.63, I used the STAR/SID wizard to get my information entered. Everything at the departure airport went fine. I was cleared for my STAR and flew it like I should. I reached the transition point, got a text message to "fly flight plan" and that was the last I ever heard from ATC. I was never contacted to change the frequency to Center, and I flew my flight plan until I was practically flying around in circles over Toronto. I was never asked to change to Approach or anything. I even tried to contact Toronto. I managed to find the right frequency, but all I got was "Last aircraft, say again." It didn't want to listen to me. I went ahead and landed anyway, and I noticed that there were no AI traffic at all at the destination airport. Just for giggles, I disabled Vox and re-enabled it, and "boom" ... the AI traffic was there, and eventually I was able to get Toronto to speak to me. It was just too late by that point. I wonder if the STAR/SID caused a problem? Next time, I might try without using it and see what happens. Oh, and be careful with those emergency landing requests. One time it directed me to land my CRJ-200 at a small airport with turf. It was difficult to find.

Weren't those among the first ones they made? Could be why they don't sound as natural. I think it still sounds better than the two AT&T voices I have.

That's where the co-pilot feature comes in handy, especially with jet aircraft. On props, I seem to have enough time to switch. Otherwise, I depend on the co-pilot to take care of that, because you're right.... I'm too busy trying to line up and get on the right glide slope to land correctly.