This is an issue with the windows System.Speech library itself. For whatever reason only a limited subset of installed voices are listed. I have no idea what makes the difference between one that is and one that isn't.
Elite Observatory - Search your journal for potentially interesting objects, or notify you of new ones on the fly while exploring!
- Thread starter Vithigar
- Start date
It's the values written to the registry and there's a way to make voices globally available: https://www.ghacks.net/2018/08/11/unlock-all-windows-10-tts-voices-system-wide-to-get-more-of-them/
How strange.
I'm not about to have Observatory start mucking around in people's registries to enable voices, but if anyone does try this let me know how it goes!
I wondered why some of the installed voices didn't appear in the list of voices - not just in Observatory, but elsewhere too. Very odd. That said, I just followed the instructions to enable the Cortana voice and it worked just fine, with one caveat - where it has microsoft.windows.cortana_cw5n1h2txyewy in the registry key, for me it's actually under microsoft.windows.search_cw5n1h2txyewy, I guess this might just be dependent on win10 updates or something.
I'd previously tested one the the Spanish ones but she seemed to get very confused and spoke half the words in English and the rest in Spanish
I'd previously tested one the the Spanish ones but she seemed to get very confused and spoke half the words in English and the rest in Spanish
Last edited:
Perhaps I'm stating the obvious, but not all language packs have Text to Speech ability... When downloading the voice pack, you have icons indicating what ability those language packs have...
I don't quite get what you're talking about. Microsofts TTS voices that can be downloaded using the language settings of Windows are all - well - TTS voices. Of course they all are able to do text to speech.
Appendix A: Supported languages and voices - Microsoft Support
Learn which languages are supported in Narrator in Windows and how to adjust your Narrator Settings.
support.microsoft.com
Yep, confirmed this worked for me too... I found Microsoft Hazel (english UK) appeared without any hackery, and sounds better than the default two voices -- and others such as Catherine (australian twang) needed the registry hack.
Never mind, I was talking about language packs... Not all language packs contain TTS voices... My bad...I don't quite get what you're talking about. Microsofts TTS voices that can be downloaded using the language settings of Windows are all - well - TTS voices. Of course they all are able to do text to speech.
Appendix A: Supported languages and voices - Microsoft Support
Learn which languages are supported in Narrator in Windows and how to adjust your Narrator Settings.
Some minor personal life things getting in the way of the next release but should happen soon, with support for the new barycentre infomation in the logs, so that's nice.
One thing I wanted to check on though, it's now been a little over a month since the new Lua custom criteria were released, and while the feedback I've seen has been pretty positive I'd like to hear people's thoughts on it, and most importantly anything they'd like to see changed or added.
One thing I wanted to check on though, it's now been a little over a month since the new Lua custom criteria were released, and while the feedback I've seen has been pretty positive I'd like to hear people's thoughts on it, and most importantly anything they'd like to see changed or added.
I'm very pleased with Lua so far - keen to see other users creative examples of criteria over time to give me more ideas for my own - and of course watching FDev like a hawk to see if they add more exploration-centric content one day.
Lua rocks! In my opinion it's by far a better way to define conditions than the previous one.
I've only noticed minor general details like reading "body 2 g" as "body 2 gram" or "body AB 1" as "body ab 1" (not "body A B 1") or playing several notifications at a time (for example: two stars on fast orbits, scanned at the same moment).
Sometimes smth is wrong but the app does not return any error code but just dies which makes debugging more difficult. For example: I was looping the rings collection "for ring in rings(scan.Rings) do" without checking if there is anything there "if scan.Rings then". No error message, no just doing nothing because there was nothing to loop at, the app just kept dying when a no-ring body was scanned.
I've only noticed minor general details like reading "body 2 g" as "body 2 gram" or "body AB 1" as "body ab 1" (not "body A B 1") or playing several notifications at a time (for example: two stars on fast orbits, scanned at the same moment).
Sometimes smth is wrong but the app does not return any error code but just dies which makes debugging more difficult. For example: I was looping the rings collection "for ring in rings(scan.Rings) do" without checking if there is anything there "if scan.Rings then". No error message, no just doing nothing because there was nothing to loop at, the app just kept dying when a no-ring body was scanned.
Both of these should be fixed in the next release. Voice notifications will properly queue up rather than all playing at once, and speech markup has been added to the notifications internally to instruct the text-to-speech to spell out parts of the body labels.
This is actually the first I've heard of this. I'll look into reproducing it myself, but are you able to check if application crash details are written to the windows event log when this happens (event viewer, windows logs, application)?
Obs Core + Plug-Ins is really working great...I'm still running Observatory (Legacy) as a 'safety net' in case I find some criteria I haven't copied yet....
I mentioned this in our Discord - but maybe got lost - but I think it would be a wonderful addition to the Core settings - if you could have a spot for URL links to the other plug-ins download locations / GitHub repositories etc (provided by their authors of course) - as then it would be easier to check if you had the latest version(s) [Not saying that ObsCore needs to version check - just a URL link - if even only text that you needed to copy/paste]...
Cheers
o7
I mentioned this in our Discord - but maybe got lost - but I think it would be a wonderful addition to the Core settings - if you could have a spot for URL links to the other plug-ins download locations / GitHub repositories etc (provided by their authors of course) - as then it would be easier to check if you had the latest version(s) [Not saying that ObsCore needs to version check - just a URL link - if even only text that you needed to copy/paste]...
Cheers
o7
I have been hunting through this thread trying to find out why this tool has NEVER worked for me. Now I know. I have NEVER used the FSS. I really dislike it. I fly to every body in the system, every time. Too bad, would have loved to use this...
Not the makers fault, just mine... lol
Flying to the bodies to get a proximity scan should also work. Though I expect you'd already know most of what Observatory is checking for by that time.
This is something that's "on the list", but I've got a lot more under-the-hood stuff to hammer out before I really dive into nice-to-haves like this.
I'll try to keep it in mind though!
Hold on... how do you even know where things are to fly to if you're not FSSing? Are you spotting planets by parallax!?
Same reaction I get from a lot of players. I learned how to explore without even knowing the FSS was there. I fly to a system, stop, honk, look in left panel, pick one, fly to it, pick another... and so on.
Just FYI, only things that have been previously scanned by other players will show up like that. If you're the first to discover a system then your left panel navigation tab will not list any bodies.