CaptainCrewe

Sadly, resetting at the beginning of a flight does not work. I did that today before connecting to the flight sim. It was Microsoft Dave all the way. I see you've replied under another thread with news of a pre-release. I'll try that tomorrow. Many thanks

I'm not sure I do have the same voices. I'd attach a screenshot but that doesn't seem to be straightforward here. The first 3 in my list - they all start with SAPI: Microsoft Hazel Desktop Microsoft David Desktop Microsoft Zira Desktop The remainder all start with SAPI: Microsoft Server Speech Text to Speech Voice: en-CA, Heather en-AU, Hayley en-US, Helen en-US, Zira Pro da-DK, Helle fr-CA, Harmonie fr-FR, Hortense All of these test OK via the P2ATC Settings interface. I'm on a flight now and have been through clearance delivery, ground, tower and a number of center controllers. All have used David Desktop. Perhaps you are suggesting that I make David my Co-pilot voice, and then the others might come into play for ground, tower, center etc - is that right? Since I do have a few non-English voices, it would be nice to use those as well. As mentioned, the 'Use Non-English Voices' does not persist. In case it's relevant, I did shift to a new PC at the end of last year. As I recall, I deactivated the licence on the old PC, then copied over the settings into AppData and the files into my desired location. I did have to run the installer again so as to get the SQL Server element installed in the base OS. Everything was working fine after that, until the breaking change that Microsoft introduced earlier this year. So I accept that I can't get Natural voices until that is resolved. I could try AWS voices but it seems worth making sure P2ATC is working properly first. Thanks

Hi Dave, I agree that Microsoft has done something to break the Natural Voices. Per a support chat I opened with Microsoft, it may be a bug introduced by a recent Windows update rather than a conscious decision to disable their use. But having noticed some voices go quiet within P2ATC, I did take the steps you suggested above to remove the natural voices via the NaturalVoiceSAPIAdapter Installer. I now have 3 Desktop voices and 4 Microsoft Server Speech Text to Speech Voices showing in the Voices tab of P2ATC Settings (v0.2.7A). All test OK. However, when it comes to a flight, the only voice used is Microsoft David Desktop. I have ticked the box for 'Use Non-English Voices' and saved - I get Save Succeeded. But when I check again, either within a session or on a fresh load, that box is no longer ticked. Can you suggest how I might resolve this so as to get at least some variation in voices used during a flight? I'm also prepared to try the AWS voice option. But I'm reluctant to tackle its complexities if something is already awry within P2ATC. I've seen confusing posts about AWS and whether it is still supported. Your comment above is recent so I assume it is, but perhaps you could confirm. Thank you.

Thanks Dave. For the record I only used the version of the Natural Voices Installer that came with P2ATC v0.2.5m. I was only following the instructions at the NaturalVoivesSAPIAdapter website for pointing to manually downloaded msix files. Anyway, after more experimenting I think I'm there. The options on the Installer are not quite as you suggest - on my system there isn't an option for 'Current display language & English'. The options are 'All supported languages', 'User's preferred languages/display language' and Custom. I tried the second as being closest to what you suggested; didn't work. Eventually I tried 'All supported languages'. A Reload within P2ATC still didn't show anything, but after restarting P2ATC there were lots of voices, most appended with Online. I have yet to do a flight with the new voices installed, but the ones ending Online do test OK - contrary to the comments on the v3 downloads page. Perhaps that page needs updating? Thank you for your assistance.

Hi Dave, Thank you for the input. However, even with v0.2.5m I can't get the Natural Voices to show up within P2ATC. It's tricky to know how to proceed because the steps in the comments above differ from those in the Natural Voice Installer popup and also from those in the P2Av3 Quick Start Settings video. For instance the popup shows 'Include Microsoft Edge online voices' but the comments above suggest that Online voices need to be deleted (while the Quick Start Settings video shows them as still installed within P2ATC). I've used the Natural Voices Installer that came with v0.2.5m to uninstall both 32- and 64-bit 'versions'. I then selected 64-bit only and installed that. Back in P2ATC I did a reload - no change. I also tried restating P2ATC - same. I also tried the instructions here (Narrator natural voice download links · gexgd0419/NaturalVoiceSAPIAdapter Wiki · GitHub) to download the msix files; I extracted them as per the instructions and pointed the Natural Voices Installer to the folder holding the extracted folders. Re-installed the 64-bit version, Reload within P2ATC - no change. Meanwhile I did add a couple of MS SAPI voices - there aren't many to choose from on my system. They do however show up in the list of available voices. Looking at other settings, I do the language packs installed for English (UK, US, Australia, India and Canada). My 'Speech language' is set to English (United States) with 'Recognise non-native accents for this language' ticked. If you have other things I might check/install, details will be much appreciated. Thank you.

Hello and thank you for outlining this procedure. I've just installed Pilot2ATC v3 and am trying to get it set up. I've followed the steps above (and per the info on the main website, V3 Downloads). But I'm not getting the newly added natural voices showing up in the P2A interface. I'm running Windows 11 Pro with the latest updates (v25H2 for x64). Under Accessibility, Narrator I see 7 voices with (Natural) as part of their name. Then 19 voices with a mix of languages (eg Microsoft Richard - English (Canada)), then 5 with Desktop appended to the name, and finally about 20 ending with Online. Per the guidance, I've deleted all the Online voices from within the P2A Settings. I've used the Natural Voice SAPI Adapter utility (as included with P2A v3, not the GitHub download) to install the 32-bit and 64 versions. I've set the 'Included languages' there to en-US. I've restarted P2A after each change and also rebooted the PC for good measure. Despite this I only see 3 voices in the dropdowns within the Voices tab of Settings. They are all prefixed with SAPI: and only include the voices ending with Desktop in the Narrator settings. If I click 'Use Non-English Voices' and Reload, then I see the 5 voices mentioned above. Any guidance for getting the Natural voices working would be much appreciated. Many thanks.

The news is good. I have managed to identify the offending add-on. I started by trying to remove scenery.cfg, as suggested above. It turns out that there were three versions of this file on my system. I started with the one in the main FSX folder, being the first place that I looked. FSX didn't like that at all (said it would have to be reinstalled), so I copied the original back in. I thought then that it might be the one in my AppData\Roaming\Microsoft\FSX folder, where fsx.cfg lives. I removed that, started up FSX, and saw that the scenery entries hadn't been changed, nor was a new file created in this location. I then tried the SceneryConfigEditor tool, which showed me yet another scenery.cfg file, this time in C:\ProgramData\Microsoft\FSX, which I think is the one actually in use. The tool reported no errors with this file, so I didn't delete it. Instead I moved on to Jim's next suggestion of looking at my fsx.cfg file. Having taken a copy, I deleted it. Starting FSX did indeed create a new one. Lots of pop-ups while starting asking if I wanted to allow various dlls to run. I did so one at a time - allowed one, then shut down FSX and checked the Application log. Started FSX again, allowing just one more, then close etc. Finally, the errant add-on was exposed. Turns out to be one of three add-ons that got installed with Concorde-X from FlightSim Labs; specifically FSL Events. The other two, FSL Options and FSL Sounds, did not generate the error on shut down. I can now actually toggle the behaviour by editing FSX.cfg and flipping the value for FSL Events within the Trusted section from 1 (OK to load) to -1 (don't load). I'm guessing that I could achieve the same end without the annoying prompt on starting FSX by editing my dll.xml file and setting the Disabled element to be True for FSLEvents. My limited understanding of dll.xml (and its sibling exe.xml) is that FSX will first check the Trusted section in FSX.cfg. If allowed, then look at dll.xml to check the required behaviour. If anyone can confirm this is how it works, then that would help me and perhaps others. Armed with this evidence, I've posted a question on the FS Labs forum asking for advice from them (and their users). It would be a shame to lose Concorde-X - it's a wonderful product. Meanwhile I thank you for your patient assistance in guiding me towards at least identifying the source of the problem (and educating me along the way). That's often more than half the battle. Wishing clean event logs to you all

Thanks so much for the quick response. I'll give your suggestion a try and report back. I'll also take a look at my fsx.cfg file, perhaps trying an earlier version to see if the problem stems from there. It helps so much to be given the confidence to try these things, rather than flailing around in ignorance and hope. Your assistance is much appreciated. Best wishes

Thank you for the clarification and explanations. At one point (as recently as June this year) FSX was operating on this machine without errors. The Application log error referencing mfc90.dll started a couple of weeks ago. From what Jim says, FSX doesn't use Visual C++ 2008 (of which mfc90.dll is a part). Yet I get the error if I start FSX, wait a few moments and simply close it, without doing a flight. From which I deduce that it must be one of the add-ons that gets loaded when FSX starts that has got corrupted. So perhaps I can try disabling all the third-party add-ons in dll.xml and exe.xml, then add them back in until the problem recurs. Then try reinstalling the offending add-on. Or I can just live with the error on shutting down FSX. Flights do seem to be working which is the main thing. I do have .NET v2 installed by virtue of having selected .NET Framework 3.5 (which includes .NET 2 and .NET 3) via Windows Features. Yes, I did install all software, including the MS Visuals, with Admin privileges. No, I haven't disabled UAC at any time. I feel this is unlikely to be the cause of the current problem in as much as things worked well for a few weeks. Yes, I try to remember to pause my anti-virus protection while running FSX. I would note though that I haven't experienced any problems when I forget to do this, and the closing error still occurs even if the anti-virus is paused. And yes, I did try setting the FSX executable to run as Administrator. It didn't help with the closing problem, in fact other errors popped up so I un-ticked that box. Unless there are other suggestions, I think I'll try the route of disabling add-ons in an effort to pinpoint the culprit. Should I do do this for the entries in both dll.xml and exe.xml, or just one of them? Many thanks for your continued assistance Sebastian

Getting the various Visual C++ redistributables correct for FSX is confusing, more so on 64-bit systems. Jim, you said that one should never have the 64-bit versions installed. Yet the wonderful AVSIM CTD guide has a screenshot (p7) showing both x86 and x64 versions installed for VC++ 2008. My understanding (supported by the text in the guide) was that FSX wouldn't use the x64 versions even if installed. Indeed, the error message I included in my first post includes the path C:\Windows\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_4bf7e3e2bf9ada4c\mfc90.dll, which suggests to me that it is the x86 version that is causing the problem. Anyway, I've removed the x64 versions, leaving me with four VC++ 2008 x86 redistributables: 9.0.21022, 9.0.30729.4148, 9.0.30729.4974 and 9.0.30729.6161. I fired up FSX, waited a bit, then closed it. Same error in the Application event log that was mentioned at the outset. Meanwhile, the VC++ 2005 entries in Add/Remove Programs don't show the architecture as part of the name. Like the screenshot mentioned above, my system has two, 8.0.61001 and 8.0.56336. Following the various links at https://support.microsoft.com/en-us/kb/2977003 shows that Microsoft use the same version number for both the x86 and x64 packages. So I don't know how to confirm that I have only the x86 package for VC++ 2005 SP1. Or if it matters. Can anyone offer guidance on whether all those VC++ 2008 versions are required? Would it perhaps be sufficient just to keep the latest of the v9.0.30729 instances? With thanks and regards Sebastian

Many thanks indeed for the very quick response - and apologies for posting initially in the wrong forum. I'll try removing the x64 versions of VC++ 2008 and also make sure my VC++ 2005 (x86 only) is SP1. Will post back with the results. Thank you again Sebastian

Hi Things are good on the whole, running FSX Acceleration Pack (10.0.61637.0) on Windows 8.1 Pro. In case my profile is not visible, the system specs are as follows: Computer Type: PC/Desktop System: Scan 3XS Custom OS Windows: 8.1 Pro x64 CPU: Intel Core i7 5820K Motherboard: ASUS X99-A Memory: Corsair DDR4 16GB Graphics Card: NVIDIA GeForce GTX 970 Sound Card: Realtek on-board PSU: Corsair RM750 Case: Corsair Carbide 330R Cooling: Noctua NH-U14S Hard Drives: Samsung SSD 850 Pro 256GB Seagate ST2000DM001 SATA 2TB Western Digital WD20EZRX-22D8PB0 SATA 2TB Internet Speed: Fibre Browser: Chrome Antivirus: Kaspersky KIS 2015 I use a Thrustmaster Warthog throttle and joystick, plus Saitek Combat Flight rudder pedals. Having got everything working, I've recently had problems when closing FSX. Specifically, a dialog box pops up saying 'Microsoft Flight Simulator has stopped working' and offers options for closing or debugging the program - I choose Close. I've read through the excellent CTD document and followed the advice there. Sadly (or fortunately?) this problem does not result in a WER report so the AppCrashViewer has nothing to show. But the event log shows 2 error entries at the time of closing, both with the same details: Log Name: Application Source: Application Error Date: 13/07/2015 15:31:52 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: SC-MAIN Description: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: mfc90.dll, version: 9.0.30729.6161, time stamp: 0x4dad06e0 Exception code: 0xc0000005 Fault offset: 0x0020cab2 Faulting process ID: 0x12f8 Faulting application start time: 0x01d0bd705bb3a8d5 Faulting application path: D:\FSX\fsx.exe Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_4bf7e3e2bf9ada4c\mfc90.dll Report ID: e6bbde6b-296b-11e5-82c5-ac9e17b55317 Faulting package full name: Faulting package-relative application ID: I accept that I am luckier than many in as much as the error only comes when closing FSX; the sim itself seems to run fine. But with Windows 10 around the corner, I'm keen to clean it up if possible. I've followed the advice in the CTD guide and done: Run sfc \scannow - I've done this a few times in connection with a boot problem; it claims to fix things but I see no difference. Booting is intermittently successful but once running, all is well. Deleted the scenery indexes and shaders folders Run DXDiag - no problems Run Process Monitor while closing FSX - nothing stands out to me Used CCleaner to check the registry - nothing untoward; I used it to remove a few outdated references to .NET v1 Reinstalled the latest VC++ 2008 Redistributable - x86 9.0.30729.6161 Run the Microsoft .NET repair tool - nothing found Installed and run the Scenery Configuration Editor - nothing found Made sure all drivers are up to date Something has changed since I was last using FSX a month or so ago. This is a development machine, so I have installed stuff. But nothing that I know of that would use the VC++ 2008 library. And anyway, I've reinstalled the version that was referenced in the error message since the FSX problem occurred. I do see in Add/Remove Programs that I have several versions of the VC++ 2008 Redistributable. For x64 I have versions 9.0.30729.4148 and 9.0.30729.6161 for x64, while x86 is well catered for with 9.0.21022, 9.0.30729.4148, 9.0.30729.4974 and 9.0.30729.6161. The redistributables for VC++ 2005 are present for both architectures; ditto for 2010 and 2012. For 2013, there is only the x86 version. My understanding is that only the x86 versions of VC++ 2008 are relevant to FSX. I'd love to delete all but the latest for each architecture but have resisted in case my add-ons are version specific. Would the advice here to be just to live with the error on closing? Or is there anything else I can try to get to a clean running (and shutdown) state? Many thanks and regards Sebastian Crewe