Mad_Mac

There is a key combination to toggle the window off and on. I have it programmed onto my throttle and don’t recall the combination, but it is in the manual. When toggled off, the window is completely gone.

Jaboom, all I can say is LOL!.

What I can tell you, is that it works much better with a flight plan. Airports that are not towered will not recognize your calls (or populate flights). Class D and above will respond, but you will need to be prepared to repeatedly state your intentions in order to maintain contact with the controller.

There is already a thread on this topic: It seems to be related to a problem with add on software.

Mine is still working (with the caveats described in this forum).

Yes, it is as simple as that!

There is a way to activate traffic at on route airports right now. If you contact approach, or the tower or Unicom for an airport you are approaching, it will, “come to life” Then you can tune back to the controller you were talking to and the airport will remain active. I discovered this myself by accident, but it is a cool “feature.”

In a simulator, who cares? I searched this question for real pilots, and the overwhelming consensus is that you should use the entire runway, regardless of weight, performance characteristics of your airplane. There were decenters to this opinion, but they were overwhelmingly younger, less experienced pilots. I don't know that you can expect VoxATC to support such a decision.

Just a few threads down there is one titled, "Problems running VoxATC 7.41" It is not quite identical to yours, but very similar. If filing a flight plan has already been done, or does not help, in addition to generating a log file and taking a look at it, I would recommend submitting the log file to Tegwyn (Developer of VoxATC) at info@voxatc.com

This is a small thing, but would add to the emersion. In VoxATC the name of my home airport is spelled West Bend Mun (short for Municipal, which is the full name of the airport). VoxATC pronounces is it, "West Bend Muhn." In real life all pilots simply refer to the airport as "West Bend" (with no Muhn, or Municpal). It is the same at many airports around the country. Dane County Regional Truax is commonly referred to as simply "Madison." Is there some way to edit how these locations are pronounced?

I can't speak to the vectors issue, but the slow to 200 kts is based on an FAA rule that states 200 kts is the top speed in Class B or C controlled airspace.

This sometimes happens in real life too. If you let the tower know you are "Clear of the zone to the (East North West South), that will sometimes wake them up. Works in Vox ATC too.

Have you tried adding Windows 10 voices from other countries? They speak English, but with their native accent. Adds an International flavor.

The hardest thing about expert mode is you need to know VoxATC procedures and phraseology, which does not always match real world. Also, real world ATC will usually give you a clue about what they didn’t understand, instead of making you say the whole thing again. That being said, if you’ve been doing VoxATC for a while, you’re probably ready for expert mode. It does add a lot of optional phrases.

I fly out of West Bend KETB regularly. The taxiway for runway 13 joins with 5/6ths of the runway available. Until this release I’ve never seen AI planes back taxi on that runway. Maybe with less runway available they were more likely to back taxi in previous versions.

I decided to take the plunge (at least put my toe in) after reading all of your excellent posts on this topic. I installed P3d 4.1 using the client method, and so far working fine with no problems. (other than the usual ones already discussed in this forum).

I'm using FSXFlight also in P3d 4.1 and have perfect 1 meter accurate GPS with other aircraft showing up as well.

The back taxi (is the actual phrase) is a relatively new behavior I have just noticed. Previously the AI planes in FSX and VoxATC used to just try to take off from wherever the taxiway meets the runway. Unfortunately, while more realistic, the back taxiing does create more potential for conflict. VoxATC seems to get rid of the conflict by removing a plane. I have noticed this a couple of times when I was about to be hit, and would rather have the plane disappear than have to reboot the flight (which used to happen more often in previous versions of VoxATC). Although, I do not think this is the most elegant of solutions it does work.

I flew VFR from KSBA to KSFO using FSXFlight to send GPS data to ForeFlight. It worked perfectly. I was able to see nearby aircraft displayed on the moving map in ForeFlight. As I approached KSFO I was handed off to approach given vectors that made sense and as I got closer to the airfield, I could see that my little Comanche was being placed on a circular path inside of a larger circle of passanger jets. I could Also see a gap in the circle, and figured that’s where I was going to go. I kept following the vectors and VoxATC, slotted me right into that gap. I was handed off to the tower and cleared straight in for landing behind an airbus. I made sure to keep my flight path above the jet’s to avoid his wake turbulence and made a smooth landing. It was great to be able to watch ATC fit me into the pattern.

I’m in no hurry to update to P3d v4.1. It’s working well enough for now.

By the way, VoxATC does not recognize the phrase, “shutting down.”

Not only from country to country, but from airport to airport. In the US your flight plan is not automatically closed when you are cleared for landing. I recently flew to a class D airport, had padded my flight plan by about half an hour. After landing and parking (I didn’t report “shutting down” as the ground controller was also working the tower and seemed kind of busy) I was having lunch when I got a call from flight services asking if I was OK. I had neglected to close my flight plan. I was glad they called before sending out search and rescue, and have been more careful ever since.

I have reported this, along with submitting the log, but I agree, there are bigger fish to fry.

I am not experiencing some of what you are reporting. I generally fly VFR in the US. I am usually prompted to tune to flight service to open my flight plan at towered and nontowered airports. I usually load a flight plan, even to fly locally. I believe you need to be in Expert mode to fly without a flight plan. I have seen odd behavior from AI aircraft, but at a much reduced level. I fly several times per week, and have only been rammed by an AI plane once, and that was at an aftermarket airport. I also have a private license and rarely get any instructions from the tower beyond clearance for takeoff. I often have to tell them (especially in class D) I am clear of the zone, and then am told I’m free to change frequency (without being given a specific handoff) In class C airspace you are usually handed off to departure. This does happen inVoxATC. Transitioning airspace is not enabled, but the prompt you refer to does offer some hope for future releases. If you are using traffic advisories, you are handed off to approach prior to entering class C or B airspace, but are not prompted to request transition of those airspace’s. Class D airspace is currently ignored by VoxATC (but easy to fly over the top of, which is what I do in real life). One thing you did not mention: In real life, when approaching a towered airport for landing, you are supposed to listen to ATIS first and inform the initial controller (approach for class B and C, The tower for class D) that you have information Alpha (or whatever the ATIS code happens to be). This is not modeled in VoxATC. To me, it is still the closest thing to real. One other thing, If you use Spanish speaking voices, they will pronounce English words with a Spanish accent, ie. glide becomes “Gleeda”.

I don’t generally save and return to flights, and not sure I want to give it a try after what you’re reporting. If I have to step away mid-flight I generally hit the pause key. Both VoxATC and P3d v4 tolerate this relatively well, even for extended periods. If you are saving and shutting down P3d, you would have to disable VoxATC anyway, so you may as well shut down VoxATC first, save your scenario, and then restart it after loading your scenario. Good Luck!