Release EDDI 3.3 - Bring your cockpit to life

Importing EDDI.vap into HCS or any other voicepack isn't actually necessary... you can import EDDI.vap as its own profile then configure whatever other profile you'd like to include commands from EDDI.vap. The benefit of this approach is that it's very easy to update either profile without needing to re-import the other... it's very modular.
Yes - Thank you for clarifying that. It is what I do, but worded it poorly in my post.
 
Last edited:
A very good thread with long shelf life but for me if I said it once I will say it again. If there was an option,..oh lets say in outfitting to clean or customize the interior of the boats I would be all in. I understand that the bumps and scrapes make for a used interior feel but in combination with a new paint scheme and engineering it really would be nice to have that virtual bottle of armor all or clean up so the interior of your pride and joy is as nice on the inside as the exterior. Just saying that you spend a lot of time in there. Should be a pleasure and not give you the feel that you need a virtual tetanus shot getting in and out of the pilots position.
Are you sure you have the correct thread, brother? These nice guys have nothing to do with the Elite: Dangerous code, models, or in-game appearance. These guys made a 3rd party tool called EDDI to add a layer of functionality over the game. Just FYI

Cheers!

P.S. I like your suggestion, if you find the correct place to suggest it to FD, I'd support it for sure!! My Python has some cables that look dangerous as hell just beside my captain's chair. Only a matter of time before I get electrocuted ;)
 
Last edited:
The EDDI team have done great work adding the stuff I've made in the past into EDDI, like the monitors (cargo, mission, legal) and now the exploration stuff.
To clarify for anyone else reading this, and to be fair to my teammates, I want to emphasise that they have done an awful lot more than merely migrating functionality from DC's scripts into the executable!

A vast amount of work has gone into the new monitors and they make things possible that simply weren't beforehand -- such as asking for the nearest Interstellar Factors or solving the "Travelling Salesman Problem" when you have multiple missions stacked.

As always, see the change log for full details.
 
We're please to announce that EDDI version 3.4.1-rc2 is now available. Full release notes are here. Highlights:
* Fixed a bug that could disable the cargo monitor with translated versions of EDDI.
* Fixed a bug that caused EDSM synchronization to slow to a crawl, and optimized database access. Resynchronizing with EDSM will speed database access and is recommended for all pilots.
* Fixed the character encoding in the French personality file.
* The Body mapped event now makes available all of the same body data as Body scanned.
* Added new event Ring mapped (the Body mapped event will no longer trigger when probing a ring).
* Reinstated ship export to EDShipyard, as its developer has returned.
 
We're please to announce that EDDI version 3.4.1-rc2 is now available. Full release notes are here. Highlights:
* Fixed a bug that could disable the cargo monitor with translated versions of EDDI.
* Fixed a bug that caused EDSM synchronization to slow to a crawl, and optimized database access. Resynchronizing with EDSM will speed database access and is recommended for all pilots.
* Fixed the character encoding in the French personality file.
* The Body mapped event now makes available all of the same body data as Body scanned.
* Added new event Ring mapped (the Body mapped event will no longer trigger when probing a ring).
* Reinstated ship export to EDShipyard, as its developer has returned.
Something ain't right...

EDDI v.3.4.1-rc2

I click login to Frontier API and the program closes.
 
In future we will soft fail if EDDI is built without the Frontier API configured. (This can happen because FD require us to keep our client ID for it secret, so it can't be checked into GitHub. More details here.)
 
In future we will soft fail if EDDI is built without the Frontier API configured. (This can happen because FD require us to keep our client ID for it secret, so it can't be checked into GitHub. More details here.)
Hmm, can't seem to comment on the Wiki page directly. A "better" way to do this is to #include your client secret and don't commit that file. Instead, commit a GPG-encrypted version of that file (which can be encrypted to all registered developers of the app). Prior to building, decrypt the file. Since the decrypted version isn't part of the repository, there's no way to accidentally commit it. Also, since the encrypted version -is- part of the repo, there's no way to lose it or use the wrong version if you ever need to change it.

ie:
ClientId.cs:
#include "client_id_eddi.hc"
....

Git commit:
....
ClientId.cs
client_id_eddi.hc.gpg
 
Top Bottom