Release EDDI 3.3 - Bring your cockpit to life

Haven't played EDO for a few weeks but when I started EDDI today I cannot get it to connect to the Frontier Authorization screen just get a continuous reset connection/failed to authenticate loop. I can sign in to my Frontier Account and connect and update my data via INARA just cannont get EDDI to connect. Anyone got any solutions?.
 
I think there was a problem with an older version. Have you deleted/uninstalled everything and installed the latest version?
 
I figured it out. I have both Firefox and Edge installed as well, but for the last while I have the DuckDuckGo browser set as default and Frontier it seems doesn't like having all their tracking cookies deleted. I made a temp change and set Edge as default and EDDI connected to the Frontier authentification page straight away.
 
I stopped playing Elite for a couple of years. EDDI updated when I started using it again and seems to be working fine, however the EDDSystems.sqlite and EDDUser.sqlite files don't seem to have changed since 2022. Have these files moved or is EDDI saving logs somewhere else now? I wrote a program that reads EDDUser.sqlite to organise my screenshots but it can't see any new ones.
 
I stopped playing Elite for a couple of years. EDDI updated when I started using it again and seems to be working fine, however the EDDSystems.sqlite and EDDUser.sqlite files don't seem to have changed since 2022. Have these files moved or is EDDI saving logs somewhere else now? I wrote a program that reads EDDUser.sqlite to organise my screenshots but it can't see any new ones.
Hmm, I only seem to remember there being an 'EDDI.sqlite' file that stores all system data for the systems you've visited (plus some you haven't), and a few other bits and pieces. I don't remember there being any other .sqlite files. But I could wrong, as I haven't really looked at that side of EDDI until the last year or so. I'm sure @T'kael will be able to provide a proper answer to your questions.

As for log location, they are stored in %AppData%\Roaming\EDDI as the default location.


There was probably a problem with the SQL databases. CMDR @Darkcyde has repaired something. I think he'll be in touch soon. ;)
Ah, this is for when the EDDI.sqlite file sometimes seems to 'go out of sync' with scanning systems. Here's an excerpt from the readme for the repair tool, that better explains it:
"... to repair missing (null) 'systemAddress' data for bodies and fixed stations (orbital and surface) in the EDDI database. It will also attempt to repair missing (null) 'systemaddress' field data. This one is different to that of bodies and stations, and seems to be a key field for systems in the database. These can sometimes be missing due to them being old (before this information existed?) or due to errors in the database."

EDIT: I've just found an old back-up of EDDI from 2017 (version 2.1.0) that I have laying around (don't ask!), and that also only has an EDDI.sqlite file, no other .sqlite files. I don't know if older versions of EDDI had the files you mention though.
 
Last edited:
Hmm, I only seem to remember there being an 'EDDI.sqlite' file that stores all system data for the systems you've visited (plus some you haven't), and a few other bits and pieces. I don't remember there being any other .sqlite files. But I could wrong, as I haven't really looked at that side of EDDI until the last year or so. I'm sure @T'kael will be able to provide a proper answer to your questions.

As for log location, they are stored in %AppData%\Roaming\EDDI as the default location.



Ah, this is for when the EDDI.sqlite file sometimes seems to 'go out of sync' with scanning systems. Here's an excerpt from the readme for the repair tool, that better explains it:
"... to repair missing (null) 'systemAddress' data for bodies and fixed stations (orbital and surface) in the EDDI database. It will also attempt to repair missing (null) 'systemaddress' field data. This one is different to that of bodies and stations, and seems to be a key field for systems in the database. These can sometimes be missing due to them being old (before this information existed?) or due to errors in the database."

EDIT: I've just found an old back-up of EDDI from 2017 (version 2.1.0) that I have laying around (don't ask!), and that also only has an EDDI.sqlite file, no other .sqlite files. I don't know if older versions of EDDI had the files you mention though.
Sorry, it was EDDiscover, not EDDI, that was creating the logs I was using. It's been so long I had forgotten they were seperate applications.
 
I'm also having problems at the moment, but I think it's the cAPI. Announcements do not come at all or are delayed. If I query the cAPI, my CMDR gets a reputation of 0 % for all powers!
 
I'm also having problems at the moment, but I think it's the cAPI. Announcements do not come at all or are delayed. If I query the cAPI, my CMDR gets a reputation of 0 % for all powers!
Have you reviewed your .log file? The CompanionAppService may have recorded some information about what cAPI is sending (particularly if you temporarily activate verbose logging).
 
No, detailed logging was not switched on. Yesterday evening the problems (delayed announcements to no announcements at all) ...
... nothing changed, today VA started with EDDI and ED, everything OK again. :rolleyes:

An entry in the log from yesterday:
2024-02-28T20:34:05 [Info] JournalMonitor:ParseJournalEntry Active expansions... Horizons: True, Odyssey: False.
 
Last edited:
EDDI seems to randomly crash for me. No errors or anything. Just happily playing and then i realize i'm no longer getting voice info from EDDI. Go and check, and EDDI has closed down.

Any ideas?
 
Do you use EDDI stand alone or as a plugin from Voice Attack?

I use EDDI as a plugin from VA. In the last few days I've been playing more often and EDDI hasn't crashed.
The day before yesterday there were delays in the announcement but no crashes (the API had problems).

Have you changed or adjusted anything on your PC in the last few days?

Have you looked at the log files? You can find them here: c:\Users\UserName\AppData\Roaming\EDDI\

Sorry, I don't have any more ideas for now.
 
Problems with delayed voice output again. EDDI stand alone works without problems, if EDDI is to work together with VA, there are these delays.
Everything was still OK in the afternoon. Now problems since about 21:00 UTC.
What could be the reason for this?
ED, VA and EDDI were on the whole time. There was a break in play between 17:00 UTC and 21:00 UTC. That was all. :rolleyes:
 
Previous page mentions EDDI going quiet around Thargoid shutdowns. I've created a "restart voice attack" batch file that I run via voice command as my workaround. Might help you guys to do the same?
 
Thanks for the tip. This is the first time I have encountered this problem. Another CMDR had already told me about these problems.
He thinks it is related to VA. I will test this as best I can.
 
Have you tried renaming EDDI.sqlite to something like OLDEDDI.sqlite and then restarting?

EDDI will generate a new sqlite db and you can repopulate travel history on the EDSM tab.

Fixed all the similar issues that I had.
 
I've had EDDI 'go quiet' a few times, but it still produced output to the speechresponder.out file, so it was still operating normally, just not producing any sound. I've usually been a bit busy in game to investigate, but I do seem to remember it happened once when I had to close the game down, but I'd kept EDDI\VA open. Restarting VA fixed it though.
 
Back
Top Bottom