Dhruv Kalra

You could also just program the PTT within X-Plane itself by binding the XPilot Toggle PTT command to the button in the X-Plane joystick settings.

I deliberately run with XC OFF so that airborne aircraft get the full immersion of AFV’s range degradation. Honestly it doesn’t bother me if you step on someone. I’ll sort it out on the frequency. The biggest thing you can do from a pilot standpoint to mitigate stepping on someone that you can’t hear is if you hear the controller give a clearance that you know requires a readback, don’t jump in and key up as soon as he’s done issuing it. Wait however long you think a readback might take (perhaps even read back the instruction to yourself to mentally time it).

Still happening as of iOS 14.2. Can this please be looked at?

I stated it pretty clearly above. “When Ready” is the ICAO Doc 4444 equivalent to the FAA term “at pilot’s discretion”.

I’m with Rob. If I’m too busy to provide exacting top-down, I’ll break out “runway XX, taxi via pilot’s discretion, cross all runways”. Of note, the ICAO 4444 equivalent to the FAA Term “at pilot’s discretion” is indeed “when ready”, so depending on where in the world the OP was, this might be why that particular phraseology was used.

VATGOV5 may be able to elaborate, but from what I can tell it's working for flights that originate and terminate within the US.

ICAO flight plans are required in the US for all IFR aircraft, but ATC automation still uses the old single-character suffixes. ICAO flight plan messages are passed through a filtering system in ERAM that converts the data based on ICAO EQP and SURV data and generates a single-character FAA NAS equipment suffix that is displayed on data blocks, flight strips, and in the EDST system (electronic strips). The full ICAO flight plan is available to us as well, but it requires diving 2-3 levels deep into the EDST. Last I’d looked, the prefile system conversion mentioned by @Matt Bozwood-Da

As stupid as this may sound, make sure TwrTrainer is running from your ProgramFiles (x86) folder on your Windows boot volume.

I know several training staffs that would be eternally grateful if you considered this!

I assure you that they haven’t been abolished on the ATC side. All controller-facing flight plan information at FAA facilities still has single character suffixes. Yes, filing ICAO flight plans is now mandatory in the US, but the automation still runs them through a translation process. Don’t get me wrong, I’m 100% in favor of moving to ICAO FPLs on VATSIM, and I wasn’t trying to be a stick in the mud about it. That being said, controllers in the US don’t actively get fed ICAO data. I have to dive 3 menus deep in the automation to get at ICAO equipment, and even then it’s not present

Don’t forget the multitude of 3- and 4-digit alphanumeric US airports that don’t necessarily start with “K”!

The technical solution is to convert either server or client side back to an FAA single character suffix letter, which is what the real system does. VATGOV and Ross have been provided the information regarding this.

I appreciate all the guides, etc. but frankly from an ATC training perspective in the USA, we shouldn’t have to go through this. There was clearly minimal forethought put into how ATC clients other than Euroscope (and presumably vTAATS), pilot clients, and the numerous tools that depend on the data feed would handle ICAO FPL equipment and surveillance codes. That’s a step that should have been documented and resolved prior to the new pre-file site being rolled out.

Click the word "SimAware" in the top left.

First step towards this would be to dis[Mod - Happy Thoughts]ociate callsign from your connection. Have the callsign be tied to your flight plan, which would be more accurate to the real world, and also would allow ATC to edit your callsign without disconnects. Would allow us to fix the UA123s and DELTA456s of the world too. (Following applies to FAAland) The limitation in real life is that there can only be one instance of a callsign active within a FIR/ARTCC. There are cases, although uncommon, where we will get two flights airborne in the NAS with the same callsign and all will be fine