Discussion Is EDDI still a thing?

I've been away for only a few weeks, and now I've returned, EDDI doesn't seem to work anymore, in both Odyssey and Horizons. Specifically, EDDI variables are, to put it mildly, inaccurate. For instance, fuel status percent ("{DEC:Status fuel percent") always returns "not set", and "INT:System total bodies" always returns "1", regardless of actual number.

Is this a known issue or is it just me?
 
Hmm. The fuel percentage seems to have worked itself out after some restarting, but the system variables are still returning zero or 1.

If anyone else uses {INT:System total bodies}, {INT:System scanned bodies}, or {INT:System mapped bodies, I'd be grateful if you'd let me know if it works for you, or not.
 
Yes, EDDI is still a thing. :)
Your status will depend on whether you are actually in-game when you check it or not. When you aren't in-game, status reverts to a neutral state.
Try doing a discovery scan "honk" before checking {INT:System total bodies} (since the discovery scan sets the value)?
 
In that case, you might try opening a bug report at https://github.com/EDCD/EDDI/. It would be helpful if you would include a copy of your .log files from %appdata%/EDDI/ so that we can identify any exceptions which have been recorded. A verbose log would allow us to verify the precise variables that are being set (or not). Furthermore, you might include a copy of your VoiceAttack command to assist with our replication efforts. o7
 
I have just come back to Elite after a haitus of about 4 months. I find that the EDDI plugin for VA doesn't report any of the Explorer info it used to, ie completed scans, scan values, planets to scan after a Honk. EDDI does work fine as a standalone though?
 
EDDI still works both standalone and as a VA plugin. If EDDI is not working in VA for you, please check that the plugin is being initialized?
 
Back
Top Bottom