Dave-Pilot2ATC

mhazy, You must have emailed to the wrong address. I don't have any requests outstanding. Dave

Email your key to me at admin@pilot2atc.com and I can reset it. Do not use the forum for this. Dave

Mike, When you don't specify that you want vectors to the ILS for runway xxx or to the visual straight-in for runway xx, then ATC assumes you just need help finding the airport and you will be contacting tower and requesting a VFR entry to the pattern. At about 10-12 miles out, Approach will had you off to Tower and you need to make a call something like "Tower, <CallSign> is inbound for landing", at which time the tower would give you pattern/runway information and tell you to report downwind. I suspect the strange looking diagram for the circuit was a VFR pattern with the entry included, so it may have had an overfly of the airport and a turn to get onto the 45 to downwind. Dave

I finally found the bug. It will be fixed in the next update. Thanks for the logs. Dave

I have found and fixed a problem that was causing the CPU usage to grow on long flights in P2A. It will be included in the next update. Dave

You need to set your traffic engine up for TCAS. Here's a link that might help.

Please send me (admin@pilot2atc.com) the log file for that flight as Tower should be responding to those calls. P2A Log files are located in: C:\Users\<UserName>\AppData\Roaming\P2A_200\Logs where <UserName> is your PC user name. Portions of the path may be hidden by default, so be sure Windows Explorer has Show Hidden Items checked in the View tab.A new one is created each time you start Pilot2ATC, and is closed when you shut it down. So if you take the most recent one after you have the error and after you shut down P2A, you should have the correct one. Thanks, Dave

In the real world Tom would be correct, but ATC and Pilot2ATC would not give you that abbreviated frequency assignment. Might be OK for a real world readback. If you can send the P2A log for the flight where this happened to admin@pilot2atc.com, I'll try to find and fix the bug. P2A Log files are located in: C:\Users\<UserName>\AppData\Roaming\P2A_200\Logs where <UserName> is your PC user name. Portions of the path may be hidden by default, so be sure Windows Explorer has Show Hidden Items checked in the View tab. A new one is created each time you start Pilot2ATC, and is closed when you shut it down. So if you take the most recent one after you have the error and after you shut down P2A, you should have the correct one. Dave

Thanks for the report. I'll have a look and see if I can get a fix for the next update. Dave

It looks for the nearest point to start from, so points are important near the gates. The taxi charts provided by Navigraph are not readable by the program. If you are aware of taxi data provided by them, please enlighten me.

I suspect that the map source web site might be slow. This can happen for that reason, or if you internet connection/provider is slowing you down. Usually, if it's the map provider site being slow, you can change maps and it will show fine. Dave

No, it uses both taxiways (lines) and taxi points. The default data will quite often not match what you see. That's one reason to import an airport. Even after importing, you will match the SIM, but may not match the charts. Life would be much easier if this taxi data was offered by the AIRAC providers, but to date, it is not. Dave

Please email me (admin@pilot2atc.com) the P2A log file for the flight where this happens. P2A Log files are located in: C:\Users\<UserName>\AppData\Roaming\P2A_200\Logs where <UserName> is your PC user name. Portions of the path may be hidden by default, so be sure Windows Explorer has Show Hidden Items checked in the View tab. A new one is created each time you start Pilot2ATC, and is closed when you shut it down. So if you take the most recent one after you have the error and after you shut down P2A, you should have the correct one. Dave

The goal of taxiway definition in the scenery is to provide paths for AI Traffic to follow. So, more taxi points and curved entrances to runways achieve this goal. The purpose for taxi points in P2A is to enable taxi instructions and hold-short commands, so unnecessary points are a hindrance. In general, the best approach is to leave the Taxiway definitions alone unless a problem is noticed. Then, the first remedy should be trying to import the airport taxiways from the SIM. In many cases, this will remedy the issue and no further action is needed. If there is still an issue, like not getting a hold for a runway crossing, then fixing that one issue makes sense. If you want to redefine the entire airport, it should be done in the SIM's tool, WED for X-Plane, as an example. Then import your newly defined airport and it should fix the problems. To answer your questions: 1. Generally, more taxi points are not better, but they usually aren't a problem either, so leaving them is OK unless, for example, there are taxi points between a hold-short point and associated runway. In the case of long taxiways near gates, it's a good idea to have a taxi point near each ramp area so the taxi instructions will find that as the nearest taxi point for taxi instructions. 2. Since the purpose of the P2A Taxiway definitions is to give good directions, you can extend the runway "red line" beyond the end of the physical runway and past the taxiway that passes under the glide path. Then connect the hold short point to a point on the extended runway. 3. P2A does not currently use taxiway directions/flow indicators. That is on the list for future enhancements. 4. No. 5. No 6. There is a list of Taxiway editing "rules" in the User's Guide. Dave

Thanks, but having read the docs, it's not a problem. It's on the list for future implementation.