No description, website, or topics provided.
Pull request Compare This branch is 3376 commits ahead of cmdrmcdonald:develop.
Latest commit 22947d9 Oct 16, 2018
Permalink
Failed to load latest commit information.
BuildInstaller #71 CA2237 mark serializable Exceptions as such Sep 22, 2017
CargoMonitor Fixed double report of 'Cargo updated', haulage object 'prrivate set'… Oct 15, 2018
CompanionAppService Merge branch 'l10n_develop' into develop Aug 24, 2018
DataDefinitions Fixed double report of 'Cargo updated', haulage object 'prrivate set'… Oct 15, 2018
DataProviderService EDDP uses English state names, not ednames. And we don't need to repo… Oct 13, 2018
EDDI Roll develop to b3, before we forget. Oct 14, 2018
EDDNResponder New translations EddnResources.resx (German) Sep 17, 2018
EDDPMonitor Merge branch 'hotfix/828-eddp-states' into develop Oct 8, 2018
EDSMResponder Right align buttons rather than full-width Oct 10, 2018
Events Convert glide event to set a boolean rather than a string and include… Oct 10, 2018
GalnetMonitor Merge pull request #877 from EDCD/l10n_develop Oct 14, 2018
JournalMonitor Fix "Unknown ED name All..." error which can occur during ship repairs. Oct 13, 2018
MaterialMonitor New translations MaterialMonitor.resx (Italian) Oct 8, 2018
MissionMonitor Fixed Mission warning 'minutes' remaining and 'Entered normal space' … Oct 15, 2018
ShipMonitor Fixed double report of 'Cargo updated', haulage object 'prrivate set'… Oct 15, 2018
SpeechResponder Fixed Mission warning 'minutes' remaining and 'Entered normal space' … Oct 15, 2018
SpeechService Fix #837. Oct 13, 2018
StarMapService Merge branch 'hotfix/rollbar-io-exception' into develop May 20, 2018
StatusMonitor Convert glide event to set a boolean rather than a string and include… Oct 10, 2018
Tests Fix #762 Oct 13, 2018
Utilities Roll develop to b3, before we forget. Oct 14, 2018
VoiceAttackResponder New translations VoiceAttack.resx (German) Sep 17, 2018
docs Update `Localization_for_devs.md` to describe adding new languages. May 13, 2018
graphics reinstate logo.bmp May 11, 2018
images Update documentation Nov 15, 2016
.gitattributes Init Jan 20, 2016
.gitignore Squashed commit of the following: Apr 26, 2018
Contributors.md Update contributors list Oct 31, 2017
Development dependencies.md Document development dependencies Sep 14, 2017
EDDI.sln Mission Monitor shell. Sep 1, 2018
Installer.iss Roll develop to b3, before we forget. Oct 14, 2018
LICENSE.md Ref. PR #188. Convert .md files to UTF-8 (for files not already saved… Oct 27, 2017
README.md Add CrowdIn status May 10, 2018
TROUBLESHOOTING.md Update Readme.md & Troubleshooting.md Jan 6, 2018
VoiceAttack.md Ref. PR #188. Convert .md files to UTF-8 (for files not already saved… Oct 27, 2017
appveyor.yml Remove AppVeyor branches filter Sep 15, 2018
build-installer.cmd Log start and end of installer compilation PDB zipping Sep 14, 2017
crowdin.yml Update Crowdin configuration file May 10, 2018

README.md

Build status Crowdin

EDDI: The Elite Dangerous Data Interface

EDDI is a companion application for Elite: Dangerous, providing responses to events that occur in-game using data from the game as well as various third-party tools.

EDDI reads data from a variety of sources to provide players with additional information whilst in-game, and also with events that can trigger such things as spoken responses or VoiceAttack actions. The basic flow of EDDI is shown below:

Monitors are pieces of code that check for information, for example a new Galnet article being published or an entry to Elite's journal. Monitors pass information on the event to EDDI.

EDDI takes events and carries out operations based on them. For example, if the event says that the player has changed system then EDDI will fetch updated system information from EDDB. Once it has gathered all of the required information it will notify each responder of the event.

Responders take the events, along with any information that has been gathered by EDDI, and carry out actions. For example the EDSM responder sends details of any jumps that the player makes to EDSM so that they have a permanent record of their flight logs, the speech responder provides a spoken response to events, the VoiceAttack responder provides variables to VoiceAttack scripts and runs specific scripts when events occur, etc.

Monitors and responders can be configured from the EDDI UI, and can be individually enabled or disabled as required.

Installing and Configuring EDDI

EDDI can be installed standalone or as a VoiceAttack plugin.

Download the EDDI installer from https://github.com/EDCD/EDDI/releases. By default it will install in C:\Program Files (x86)\VoiceAttack\Apps\EDDI, which is fine regardless of if you have VoiceAttack or not, but of course you can change it if you wish (although note that if the installation is not in a subdirectory of your VoiceAttack's Apps directory then it will not be able to be used as a VoiceAttack plugin).

Alternatively you can compile EDDI from the sources at https://github.com/EDCD/EDDI.

When you start EDDI it will bring up a window with a number of tabs. Each tab explains its function and how to configure it, so you will be best served to read each tab and set it up according to your liking.

Using EDDI with VoiceAttack

Initial EDDI integration with VoiceAttack is automatic, but there is a lot that you can do to integrate EDDI with your own VoiceAttack scripts. Full details of what you can do with EDDI and VoiceAttack are on the VoiceAttack EDDI page.

Upgrading EDDI

If you are upgrading from EDDI 1 EDDI it is recommended that you uninstall your existing version of EDDI and remove your %APPDATA%\EDDI directory prior to upgrading to the new one. This ensures that there is a clean installation and reduces the chances of problems occurring.

If you are upgrading from another version of EDDI 2 the installer will take care of changes so you just need to run it.

EDDI Voices

EDDI uses the standard Windows TTS (text-to-speech) voices. The voice needs to be visible to Windows' TTS system to be made available to EDDI: this usually takes place when you install the voice. If you cannot see a voice in EDDI then check the Windows TTS settings.

If you want to have a high-quality voice other than that available with Windows then the best choices are to purchase voices from either Ivona or Cereproc. Though both provide great voices, Ivona voices typically adhere more closely to published SSML standards and provide fuller functionality for phonetic speech and other advanced features like pauses in the middle of speech and correct pronunciation of names (ships, powers, systems, etc.).

Troubleshooting

If you are experiencing problems with EDDI then your first port of call should be the troubleshooting page. If this does not fix your problem then please check the Known issues below:

If you have an issue with EDDI then please report it.

Uninstalling EDDI

If you want to uninstall EDDI then you can do so through the Windows control panel. Any data that EDDI creates is stored in the %APPDATA%\EDDI directory, and this can also be removed on uninstall.