kingie

If Simbrief's intention was to have the radio callsign in the callsign box would their description not be different than: To me the above sounds like Simbrief caters for airlines with a difference between Flightnumber and Callsign (7839 vs 78VA). Otherwise it wouldn't be a combination of Airline + flightnumber in the callsign box.

Firstly great work on keeping the regular updates / fixes coming! I had a read through the recent changelogs and stumbled upon the updated callsign logic. To my understanding it seems like this logic isn't 100% correct (or maybe I am misunderstanding Simbrief and happy to be corrected!). If I have the following flight: U2 7839 // EJU 78VA (easyJet Europe flight 7839) I fill in Simbrief flightplan as follows: Airline: U2 Flight number: 7839 Callsign: EJU78VA But according to the 7E logic this would result in the following P2A callsign: U2 7839. Shouldn't logic be: If callsign is available shouldn't it always take that field as priority? So first 3 characters as Airline lookup code and the rest as flight / tail number in P2A?

Ah okay, I didn't know it was common practice to include SIDs/STARs in a real world flight plan. I learned something new! I will try this next flight and see if that works how you just explained it to me. Thanks a lot!

Hey Dave, as always, thanks for your detailed answer! My understanding was, from the manual, that the option "force Star assignment" cancels the behaviour of the intercept angle limit. Is this incorrect? What is P2A's behaviour when the approach it wants to assign me doesn't match with the transition point in my flightplan? I never included SID and STAR in my flightplan so it remains "dynamic" and a bit more realistic as I'd only know the STAR once ATC assigns it.

Pilot2ATC keeps giving me unwanted approach vectors with the following settings enabled in the Flt Pln tab: ATC assigns SIDs ATC assigns STARs ATC Assigns approaches Force STAR assignment The rest of the setting are unticked. I load a flight plan into my ATC, start flying it and a little bit before decent it informs me of the the STAR to expect. I input the STAR, start flying it and sometimes ATC informs me I am off course and need to follow heading X to return to the route without STAR. (I ignore that when it happens). When I am at towards the end of my STAR it suddenly starts giving me vectors rather than letting me fly the approach which transition. E.g.: Flight from KCRW - KMCO with SNFLD2 STAR and ILS36R approach (which even has a valid transition). This is why I have force STAR enabled in the hope it will stop giving me vectors while there is a STAR > Approach.

Voice Load Error. Attempt to use voice ZiraPro failed. Please set the Center voice to a different one. System.ArgumentException: Cannot set voice. No matching voice is installed or the voice was disabled. at System.Speech.Synthesis.SpeechSynthesizer.SelectVoice(String name) at P2A2021.modTTSGlobal.PlayATCPhrase(String Phrase, Boolean Publish, Boolean PlayBkgnd, String SugResp, EventHandler`1 SpeakCompleteEventHandler) Voice Load Error. Attempt to use voice CereVoice Jack failed. Please set the Center voice to a different one. System.ArgumentException: Cannot set voice. No matching voice is installed or the voice was disabled. at System.Speech.Synthesis.SpeechSynthesizer.SelectVoice(String name) at P2A2021.modTTSGlobal.PlayATCPhrase(String Phrase, Boolean Publish, Boolean PlayBkgnd, String SugResp, EventHandler`1 SpeakCompleteEventHandler) I found the errors when trying to play the voices that don't work.

Okay. I'll try that. But could you point me to the logfiles and application configuration files as well so I can do a "clean install" of Pilot2ATC? Thanks!

When I "test" the voices I can hear all of them just fine. So the voices do work. And at the start of the flight P2A did use those voices for the different ATC frequencies. After a while it just stopped using them and using a default fallback voice. Where are the logfiles? Where is the application configuration saved so I can remove P2A and do a "fresh" installation with a "fresh" configuration.

Update: I enabled the "Display random voice assignments" and apparently it has assigned one of the new voices yet it plays a different voice. See image below. How do I find out why it displays a different voice?

I have bought two cereproc voices yet P2A just uses whatever voice it feels like using. See my settings below. Yet after switching to a couple of different ATC frequencies it uses a voice that is NOT in the random voice list. First it works fine yet after switching to a couple of different ATC frequencies it uses a voice that is NOT in the random voice list. Have I now spent money on voices that won't work reliably either or am I doing something wrong @Dave-Pilot2ATC

I've never had them stop working during a flight, but they only seem to work about 25% or less when I start up P2A. And most of the time they don't work even if I restart the application 5 times.

Tried that, didn't really seem to make a difference. I wonder if the big issue is the fact it's cloud based rather than anything else.

Unfortunately this only solved the issue partially. The keys became available but P2A didn't "grab" the inputs so it didn't work, even if I had the sim window or P2A active. Something completely different: is it possible to use something like a type functionality for situations where you want to be routed to a different airport but "SayIt" doesn't offer the option to choose anything else than destination and "PTT" is not an option?

Thanks for the suggestion! Is the setup really difficult and fiddly? And do they work 100% or do you still have the occasional reboot of P2A? If they're really stable and work consequently I might try it out as well.

I'll give that a go, I might have misinterpreted that option. I'll update here.

Hey Dave, thanks for your quick response! The weird thing is; it is actually remembered but it just doesn't work. The key shows as still being bound in P2A but doesn't do anything. Yet P2A still "reserves" it as I can't use both the home and end key any more (e.g. tested in simple text editor). After I close down P2A both keys suddenly function like expected. That makes me think it's something related to P2A.

I've got the SayIt button assigned to either home/end on my keyboard as I mostly only use the sayit function (glad it's implemented that well!!). Every time I start up my P2A I need to reassign it to the other. (Home > End or End > Home) as it doesn't work any more.

The interesting thing is that when I configure one of the Amazon Polly voices in On Air Company it never not-works. This is why it makes me thing it is somehow related to P2A. Did you buy 13 voices a 27 GBP each?

I have installed the Amazon Polly voices on my PC and P2A does recognize them but half the time they don't play while the default Microsoft voice plays and the Amazon Polly voices play perfectly fine through the polly app. How comes they don't work half of the time?

I've set this up as well and I agree it does sound a lot better than the default Microsoft TTS. I was doing a flight earlier and the Polly voices I had configured just stopped working suddenly.

South America shows as "South_America" in the X-ATC download section, do I need to replace spaces with an underscore? Never mind, I asked that question based on the filenames in the download section, not based on the actual content.

Ah okay! Is US still "US" or would that be "United_States"? That's the only one that's not there.

I see, a misunderstanding on my part! Thanks! What are the correct names for all the other regions according to that structure? I couldn't find the relevant part in the manual but would like to set it up for all the files in advance.

I have purchased X-ATC chatter and set it up in according the controller structure (e.g.: E:\Program Files\Pilot2ATC\Sounds\ATC_Chatter\Controllers\App\CA-DAR-001.mp3) I do have different kind of chatter throughout my flights but I feel like the correct files aren't played. I was performing a Norway flight earlier and kept hearing US chatter instead of EU. When I performed US flights I sometimes kept hearing EU chatter. The settings within P2A are the path cleared, controller type ticked and Default region selected depending on where I fly.

I have found the issue why I did not see any TCAS enabled traffic! I stumbled upon the following x-plane.org forum topic: link. I don't know if you're aware of it but I figured it can't hurt to tell you about it. It basically said: I tried this solution and suddenly the plane showed up! I checked whether the plane in P2A was the same one as showing in the LiveTraffic list and it was!