Turbine777

Did a couple of tests and all is good again. I got my AWS voices back and chatter voices working. Only thing still making me scratch my head is my "Say it" keyboard short cut and chatter toggle short cut will not work, even though they are enabled and set. They will work once after I set them and close the config/dialog, but then no more. No other addon use those keys and I removed them and validated the emptied keys in MSFS to be sure there wasn't a conflict. It's not a rights saving issue or anything. I always seem to breeze through a reinstall until this issue and do know I never did anything different, it just eventually worked, so I'll continue forward. Thanks again!

I reinstalled the base version with navigraph and all works like before. I just activated but have to run out for a bit and wanted to update. I'll try "D" again when I get back. As always, thanks for the help, Dave! Another side note, after uninstalling I did a complete computer search for the other p2a folders and files. Found all my old beta zips in the windows temp folder. Guess I should empty that once in a while, haha. Some of those files go back several months.

Thanks for the reply, Dave. Doubt an issue just came out of nowhere since I just finished a flight and decided to check some of my payware sites for any recent updates and saw there were two beta builds since I last updated to 8B, and that is all I did. Didn't even reboot from my last flight where my voices worked just fine. Only reboots have been in reinstalling p2a as just in case scenarios. I'll try as suggested though.

Just tried the next possible beta download, 2.6.3.2 PublicBeta 6, and same issues. Voices tab shows zero voices. Not even the default windows voices. I rebooted each time and have FSuipc running, though that wouldn't matter in this case. Going to uninstall completely and try the normal base version...

Hey folks, Are Beta downloads available to download that aren't the latest? Looking to get back 2.6.3.2 Public Beta 8B. I just installed 8D and now nothing works right. Primarily it wiped out most of my settings and cannot get any of my Amazon voices to now show, or my cereproc for that matter. Only way is if I choose use random and then add each, but although that is the only way to see my voices in a list, they don't work. I've had no issues with overwriting other beta builds until now. Typically, after I install, I simply go to the voices tab and set each drop down to my desired voice, but nothing at all shows. Same with chatter. Using the same method I've done for years and it's not working. Maybe the D build wasn't ready for download just yet. In any case, any chance the beta builds are archived somewhere. I don't see them available on the site. Only the latest beta. Thanks, Dan MSFS here

Errands have kept me out today, but just finished a couple of flights that I didn't have issue #1 with the XPDR. I had to set it as you said and it worked nicely to where now they just say "Radar Contact". It's the default C172 analog gauge version. Hopefully a better SDK with more simconnect functionality will make for better fsuipc progress. @ rwilsonlj - Like Dave already mentioned, I have 5 Cereproc voices and the newer one is the worst and it's way to pronounce things is driving me crazy. For those who use Cereproc voices steer clear of the "Carolyn" voice. Sounded great when I previewed it using aviation lingo, but wow is it awful.

Thanks, Dave. 1- So I hear it give me the squawk and I have to go into P2A again and enter it? I always set it in the aircraft. I've never set it in P2A. I don't even know why I would. Must have missed that part in the manual. Once I'm in the sim I don't want to alt tab to P2A and didn't think I needed to. If it's giving me a squawk code why doesn't it set it in P2A itself? How do I even do that? 2- The main ones are Muni or Mun being short for municipal and INT being short for international. I was just thinking something like "Int = international, elseif proceeded by "K", or followed by another letter without a space. Sorry I can't explain better but I have zero idea of what this coding is compared to my limited best guess at it. 3- My point was really that if it's bothersome for something low and slow it would be a nightmare for airliners, such as traffic alerts. They're going to be getting them much more frequent than a Cessna. I've balanced them out now for most average flights but the default settings are just way too lean. 4- I do exactly that. I set the climb rate to 200 fpm since although I can start at 500 fpm, I can only climb at 100' fpm once I hit 13,000. Maybe a max ceiling entry block?

I have MSFS ATC off. I'm using normal frequencies. It is 100% P2A. I'll start gathering examples in my flights tonight and tomorrow.

This is very often. Too often to list all of the instances so can someone tell me or link where this is explained? Maybe it's a limitation somewhere in the current MSFS SDK or something else. Problem is when I fly VFR and tune in what should be ground or tower in tons of places that I'm nearing I get ATIS. For the record, I'm using MSFS with the latest navigraph data and no other addons that would cause this. Thanks, Dan

ATC won't let me leave them if flying a VFR flight following. This is an example only (KAPF to KFLL): Initially I start off asking "Cessna 951 request VFR Flight Following from KAPF to KFLL). ATC replies with as happily expected (really love that it will do this). Later in the flight, I change my mind and decide to land at KFXE. I cancel my flight following and am told to squawk 1200. I then try to tune in KFXE Tower but when I do, ATC tells me to switch back. I cancelled my flight following and they acknowledged this but cannot change to anything at this point without being told to get back on freq xxx.x. Thanks, Dan

I really don't like a title to lack info about what the topic is about, but can't think of better. Is it possible to (in a future update perhaps): 1- Have ATC stop telling me what to Squawk xxxx in every single message from them? 2- Learn to say "Municipal" instead of sounding like a Jamaican saying "Mun"? Or International instead of spelling out INT? No idea what it is to code this but think it would be simple if using IF or ElseIF statements. VOXATC fixed theirs back when I used it. Especially bad when they spell things out that aren't meant to be spelled. 3- Revise defaults!!! I haven't posted much at all and have learned to use the program through either searching this forum or reading the manual but now that I have 100+ hours with it I can say that no matter what aircraft I fly there are many default options that should not be as they are. For instance, having to set the distance for aircraft alerts. I read tons of topics where many people had issues with a plethora of ATC alerts and all of which were told a better setting to set the alert proximity and others. I fly mostly low and slow GA and if it's too much with it I would think the default would be too much for everything else. Why not just adjust some of the default settings from the start? 4- Expedite climb and other expectations. I'm mostly flying a C172. ATC seems to think I have a rocket ship and doesn't seem to know my max ceiling, let alone the climb rate. Even if it could not know this due to limitations, please give an option to tell it not to remind me literally every 7 seconds. I've been testing this for over 100 hours now and these are just things I see as a new user thru now. They are all downfalls 'TO ME' in this addon. No idea if it's due to limited SDK or just a "take what you get" type of thing, but these are what I find most needing to be fixed. Thanks! Dan PS. I have others that but think they are more needing their own topic that might be something I'm simply doing wrong or maybe bugged.

I never seen that as default behavior. What other addons are your using? I know I get some similar warnings from "OnAir", but that's only with it and not MSFS 2020. If actually from MSFS 2020 then please post a screenshot or link to a video.

Glad I could help 🙂 Yeah, I guess I'm used to just airways for the IFR Low. I'd still be doing my planning on skyvector regardless, but just this one flight I wanted to fly to Area 51 which isn't seen on Skyvector but is seen as KXTA in both FS20 and P2A so wanted to use P2A as my planner.

The route I have in my images is KRNO to KLAS so your screenshot of LA looks closer to what I see but as I originally mentioned, those two images are only one single zoom click different. Nothing wrong with my install, just odd there are a billion more airways in both our images than any IFR LOW would ever have in real life. Just check Skyvector or Foreflight, or anything other than P2A. As for Avsim not allowing image embedding, they do allow it but for dropbox you simply need to change the ?dl=0 at the end of the link to ?raw=1 at the end of your links. Like this, here is your own image of LA.

Since I use Navigraph I decided to look to see if there were issues with duplicates or something that looked abnormal but I can't see where it installed any data to in P2A. P2A has an empty Navigraph and NavDataPro folder in two locations (I can see hidden files and folders but these files wouldn't be hidden anyway). ...\Pilot2ATC_2020_x64\Grammars ...\Pilot2ATC_2020_x64\Data Makes no sense to have two empty folders in two different locations. I can't see where Navigraph installs to for P2A but it would help if I knew what files to look for that it might be installing. The only thing I can see is cycle_info.txt with several other files that installed to the data folder directly. I also just noticed the same exact issue is with the IFR HIGH map.