RobW05

The aircraft closest to you, but below you while you climb? Sorry, I would rather have the ones above me shown in that situation. 😉

Of course you should have it set that way. But xplane won't care how your TCAS is set, xplane simply shows the 19 aircraft that are more or less the nearest around you. You may agree these are, in certain circumstances like a climb, not necessarily the ones you are interested in in such a situation.

It can reasonably be called a 'hack' because it utilizes xplanes AI in a way it wasn't meant to be in the first place, bypassing the fact that there's no native access to xplanes tcas otherwise. But however you call it, I wouldn't say it's useless to have the ability to show more than 19 aircraft, as the 20th could be the one above you crossing your flightpath while you climb out, whilst xplane decided to show the 19 below you. I would appreciate if Pilot2ATC would be able to have direct access to Traffic Globals aircraft.

+1 for random approaches, that would be really nice to have a bit less predictability!

Same here, it almost never understood me saying "gate" when I speak in a normal way. Only if try to spell every single syllable slowly and pronounced, then it works. I sound like an idi_t then... 😁 But hey, it works!

Hello IBTC, in order to get some phrases to select you need to dial in a valid controller frequency. For example, if you want to copy IFR clearance you need to dial in the respective clearance frequency of the airport your currently at. (if no clearance frequency is available, tune in ground or tower). Then you are able to select the phrase you need to say to make your initial contact.

It seems this is not implemented in Pilot2ATC. If you listen to Pilot2ATC provided ATIS you will notice that there is no such "advise at initial contact you have information xy" phrase. It would be nice if it could be implemented!

Uncheck "ATC assigns approaches" in the FLT PLN page of the settings menu and you will get what you filed. (as long as it's still the active runway)

Haven't run into that, but the speed limit under 10000 ft should be IAS. That would be a question for Dave to answer how P2ATC handles that.

I agree it is very immersive to use P2ATC in connection with AI traffic! The big downside, be it with World Traffic 3 or Live Traffic, is that P2ATC has no control over the injected traffic. It's nice to experience being issued a go around for a few times, but it can get very annoying over time. Try to land on the active of a busy international airport, you will have to go around forever as there is no slot for you and the AI traffic keeps blocking the runway you have been assigned to land. After a while you end up just ignoring the go around as you want to get down. That's where i hope there will be more integration in future, if I'm cleared for an approach I want ATC to keep other planes away from my runway. 😁

Hmm, why do you think it's getting confused, can you give an example? Generally IAS is important for your flying maneuvers as it is showing the airflow over your wings. The higher you get the lower your IAS will be, as the air gets thinner. TAS is IAS corrected for air density, so that's telling how fast you really are moving through the air. But all that is useless for navigational purposes as it won't allow you to calculate by when you are reaching waypoints. Therefore you need GS, which is TAS corrected for wind. Therefore the only factor on which ATC can judge by when to assign you a descend or something is GS. You also need GS to figure out which vertical speed you need to reach an assigned altitude at a certain waypoint.

You could use the 'say it' function whenever you want and also bind it to a hotkey.

Since some time I noticed ATC is very strict with assigning higher altitudes during departure climb. For example, my last flight took me out of ENBR via the REKL1C departure. I filed a Cruise Alt of 280 and the departure part of the flight plan looked like this: ENBR RW17 UNPUT (5000ft) BR521 (FL075) GISUK (FL120) REKLI (FL240) VALDI (FL280) ... I was cleared to 4000 ft initially, then i was cleared to FL100, which i reached after UNPUT. I had to level off as I didn't receive a higher clearance. At waypoint BR521 I was cleared to FL120 which i reached shortly after just to level off again. At GISUK I was given FL240, had to level off again for 20 nm until i finally was cleared to FL280 when passing REKLI. So it looks like ATC will strictly stick to the altitudes which where calculated in my flight plan, even if I clearly could climb much faster. This was not the case previously, I think it started with one of the last versions of P2ATC. Another thing I noticed is that P2ATC seems not to allow to change the altitudes for waypoints, it would always revert back to the automatically calculated altitudes after I press validate. Did somebody notice same behavior recently?

With the TBM900 your TAS (true airspeed) at FL310 with normal cruise settings will be around 310 knots. Now let's assume you excpect a 50 knot headwind, then you would plan with a GS of 260 knots. Got it? 😉 But in the end it doesn't really matter, Pilot2ATC uses this to pre-plan your ETA and TOD shown on the map. But all this is re-calculated during your flight so you don't have to worry about it much.

Are you on a validated an filed IFR flight plan and received IFR clearance from ATC before you started your flight? In that case ATC should tell you to get back on course and even give you a rough heading. When back on course it should tell you to resume navigation. Otherwise if you are on a VFR flight, you will not be warned being off course.