After installing EDDI and running for over a week or so I'm now having problems, each time I reinstall it and try to run it I get this message 'EDDI has stopped working' and nothing else. Voice attack is still working as it should though, I tried attaching a jpeg but says invalid file,can anyone please help me out.
- Status
Another quick question as I'm on abit of a roll on another project I'm working on with EDDI 2
Is there a list of how Body Scanned and Star Scanned definitions {TXT:EDDI body scanned bodyclass} & {TXT:EDDI star scanned stellarclass} as reported from EDDI? or point me in the right direction of where they are?
I'd like a list of all of them so I can make counters for when I'm out exploring
Is there a list of how Body Scanned and Star Scanned definitions {TXT:EDDI body scanned bodyclass} & {TXT:EDDI star scanned stellarclass} as reported from EDDI? or point me in the right direction of where they are?
I'd like a list of all of them so I can make counters for when I'm out exploring
Are you starting both VoiceAttack and EDDI separately? If you are running VoiceAttack then you shouldn't start EDDI independently, as it's already running inside VoiceAttack.
If you aren't starting EDDI as well as VoiceAttack then it's probably some corruption in your configuration files. Shut down VoiceAttack, remove %APPDATA%\EDDI, and try again.
Sorry just found the stars....
Sorry if this is a newbie question: I tried a search in this thread for "lexicon" but got no results.
How much work would it be for EDDI to support a pronunciation lexicon as documented by Microsoft?
If it's not too hard to add support, I'd be very happy to collaborate on GitHub with straightening out the pronunciation of astronomical names, starting with the Greek names in the Pleiades!
Merope rhymes with Penelope, dammit!
How much work would it be for EDDI to support a pronunciation lexicon as documented by Microsoft?
If it's not too hard to add support, I'd be very happy to collaborate on GitHub with straightening out the pronunciation of astronomical names, starting with the Greek names in the Pleiades!
Merope rhymes with Penelope, dammit!
It looks like https://github.com/cmdrmcdonald/EliteDangerousDataProvider/blob/master/SpeechResponder/Help.md is what you are referencing. I wasn't aware of that file before, but I'll definitely examine it now. Thanks!
When you are editing scripts there is a 'Help' button on the edit window, which links to this file.
Sorry if this is a newbie question: I tried a search in this thread for "lexicon" but got no results.
How much work would it be for EDDI to support a pronunciation lexicon as documented by Microsoft?
If it's not too hard to add support, I'd be very happy to collaborate on GitHub with straightening out the pronunciation of astronomical names, starting with the Greek names in the Pleiades!
Merope rhymes with Penelope, dammit!
There are a number of elements in EDDI that contain phonetic pronunciations. If you find any that are missing (there are many, as I've only added them as I run in to them) then feel free to provide their IPA translations here or submit a pull request directly.
That said, Merope already has a phonetic translation of ˈmɛrəpiː which sounds correct to me. In this case it's possible that you either have phonetic speech disabled or that whatever voice you have is failing to read the IPA correctly.
Hi JGM,
Speaking of pronunciations, could you change the pronunciation of "Luyten's Star" to "Lʌyten's star". It's my home system so I hear it often and Luyten was a Dutch astronomer and in Dutch we pronounce Luyten as Lʌyten. Eddi says something like Lou-yten's star. Not a big deal of course but if you could change it that would be great.
Is there anywhere online that I can hear the correct pronunciation?
EDDI 2.1 is ready for beta testing. If you are interested in beta testing then feel free to download at http://www.mcdee.net/elite/EDDI-2.1.0-b1.exe and give it a try. Please report your experiences here to let me know how it's going.
The changelog for 2.1 is as follows:
Note that there are some items that I have yet to fully work through, notably the new VoiceAttack variables aren't listed in the documentation yet. This is because they're dynamic and so difficult to auto-generate. If you are interested in them then you can check the %APPDATA%\EDDI\eddi.log for entries that contain the phrase 'setJsonValues' to see what variables are being created.
The changelog for 2.1 is as follows:
- Fix material name for Cadmium
- Add ability to set state variables from VoiceAttack. Details on how to use this are in the VoiceAttack documentation
- Add option to write speech responder output to a file. This is an option that can be checked in the speech responder tab, and writes all speech to %APPDATA%\EDDI\speechresponder.out
- Add module definitions for SRV, fighter and training loadouts
- Provide new API for EDDI versioning. This allows EDDI to provide more information about updates to users, and is a precursor for automatic updates
- Update local system database with details from the journal and companion API. This ensures that this data is always as up-to-date as possible
- ModificationCraftedEvent now has details of commodities used in crafting as well as materials
- Provide update and MOTD information in VoiceAttack window if applicable
- Update mission accepted and completed events to contain more fields. Details on the new fields are in the relevant documentation
- Update location event with details of station name and type where available
- Add events when entering and leaving a station's no-fire zone. Details about the individual events are in the relevant documentation
- Add powerplay events. Details on the new events are in the relevant documentation
- Ensure that personality names do not contain illegal file or path characters to avoid issues when saving them
- Send EDDN messages with "Unknown Commander" when commander name is not known
- Use recursive/dynamic method to populate VoiceAttack variables. This provides many more VoiceAttack variables than were previously available; details are in the relevent documentation
- Add VoiceAttack 'disablespeechresponder' and 'enablespeechresponder' contexts to temporarily disable and enable the speech responder. Details on these are in the VoiceAttack documentation
- Unconditionally disable EDDN and EDSM responders whilst in CQC. This ensures that no data is accidentally sent to these systems
- Add 'target' to BountyAwardedEvent for Elite release 2.2.03 and above
- Add 'distance' to JumpedEvent. This provides the distance jumped, in light years
- Remove reference to 'last jump' in VoiceAttack documentation (this is provided by the JumpedEvent)
- Add 'Voice' parameter for VoiceAttack's 'say' and 'speech' commands to allow individual over-rides of default Voice
- Add VoiceAttack 'setspeechresponderpersonality' context to change the speech responder's personality. Details on this is in the VoiceAttack documentation
- Updated EDDI's default scripts:
- Added scripts for new events 'Entered CQC', 'Power commodity fast tracked', 'Power commodity delivered', 'Power commodity obtained', 'Power salary claimed', 'Power expansion vote cast', 'Power defected', 'Power left', and 'Power joined'
- Updated script for 'Mission completed' event to provide more detail on the accepting faction and reward
- Updated script for 'Mission accepted' event to provide a warning about illegal passengers
- Updated script for 'Jumping' event to recognise when last system's allegiance is null (as opposed to empty)
- Updated 'Docking denied' script to provide info on the reason
- Updated 'Location' script to provide correct information when docked at ground stations
- Updated 'Body scanned' script to provide additional information about rotation period of the planetary
- Updated 'Galnet news published' script to read full contents of interesting items
Note that there are some items that I have yet to fully work through, notably the new VoiceAttack variables aren't listed in the documentation yet. This is because they're dynamic and so difficult to auto-generate. If you are interested in them then you can check the %APPDATA%\EDDI\eddi.log for entries that contain the phrase 'setJsonValues' to see what variables are being created.
Yes there is. If you go to https://www.ivona.com/ and pick Dutch/Ruben as voice and then type "Luyten's" you can hear it.
Wow a changelog almost as long as that for Elite beta 2.2.03
I'll start testing tomorrow but already have a question about Elite beta. Is it possible to block sending info to EDSM while playing Elite Beta. I don't want my travels in Elite Beta to show up in my EDSM flight logs. In the previous Elite Beta after a session I manually deleted the logs in EDSM that were send but maybe it could be an option in EDDI. Or do I just have to uncheck the EDSM responder before I start playing in Elite Beta ?
Wow a changelog almost as long as that for Elite beta 2.2.03
I'll start testing tomorrow but already have a question about Elite beta. Is it possible to block sending info to EDSM while playing Elite Beta. I don't want my travels in Elite Beta to show up in my EDSM flight logs. In the previous Elite Beta after a session I manually deleted the logs in EDSM that were send but maybe it could be an option in EDDI. Or do I just have to uncheck the EDSM responder before I start playing in Elite Beta ?
Uncheck the EDSM and EDDN responders, restart EDDI, and you'll be fine.
There's no new VAP; not sure if the beta has a VAP in it (it should, but I didn't check) but you can just carry on with the existing one.
- Status