Release EDDI 3.3 - Bring your cockpit to life

I used the fix batch from @Darkcyde and @Parduz. It worked without any problems. Thanks again for that. What does EDDI use the SQL database for?
As far as I know there are only station names and system names in the database. I can't imagine that the database has anything to do with the problems.
I have only had these problems twice so far. I will test a bit more later. Unfortunately, my time for ED is a little limited at the moment.

Translated with DeepL.com (free version)
 
I used the fix batch from @Darkcyde and @Parduz. It worked without any problems. Thanks again for that. What does EDDI use the SQL database for?
As far as I know there are only station names and system names in the database. I can't imagine that the database has anything to do with the problems.
I have only had these problems twice so far. I will test a bit more later. Unfortunately, my time for ED is a little limited at the moment.

Translated with DeepL.com (free version)
I believe that the database is mainly used as a local store for recent system data, so that EDDI doesn't have to query the servers so much. Things like planet info, or faction status, or trade data. The data is timestamped, and when it gets too old, then it is refreshed from the servers.

At least, that's my understanding of its main use, but I could be wrong. I'm sure @T'kael will be able to clarify. 😊
 
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?
The .log files located in %appdata%\EDDI should be recording an exception when EDDI crashes. Would you please open a ticket on the EDDI GitHub page and include a zipped copy of one of the .log files where you know this crash occurred so that I can investigate?
 
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:
I've had this happen to me as well, albeit rarely and usually only after as long play session. I've never been able to track down a smoking gun. I'll continue to keep this in mind though.
 
I believe that the database is mainly used as a local store for recent system data, so that EDDI doesn't have to query the servers so much. Things like planet info, or faction status, or trade data. The data is timestamped, and when it gets too old, then it is refreshed from the servers.

At least, that's my understanding of its main use, but I could be wrong. I'm sure @T'kael will be able to clarify. 😊
It stores Galnet data and basically everything EDDI knows about star systems, bodies, factions, stations, etc. including some information that EDSM doesn't store. Data is considered "stale" after a little while and we refresh the data through EDSM if we need to access it again once it has gone stale (primarily to refresh faction data like states).
 
The .log files located in %appdata%\EDDI should be recording an exception when EDDI crashes. Would you please open a ticket on the EDDI GitHub page and include a zipped copy of one of the .log files where you know this crash occurred so that I can investigate?

Send you a message with a link.

Many thanks.
 
EDDI has gone dormant on me.

Can't open from VA/HCS any more. Command to open is recognized, but it isn't opening.

Report of landing pad position at Starport isn't working.

Deleted the db - no fix this time.
 
Do you have a connection to Frontier's cAPI ?
Just tested at my place (Germany near Berlin). Stand alone start of EDDI ok and start via VA also ok.
Have you ever looked at the EDDI.log ?
 
Last edited:
Do you have a connection to Frontier's cAPI ?
Just tested at my place (Germany near Berlin). Stand alone start of EDDI ok and start via VA also ok.
Have you ever looked at the EDDI.log ?
Stand alone opens fine. I checked the log for any obvious errors - none found. "System Report" responds properly when invoked from VA. Using the voice command to open the EDDI panel is recognized in VA but nothing happens. Landing pad position report approaching a Station also has stopped working.

Connection to Frontier is "connected"
 
Mostly cleaned up now and running well, but I have to delete EDDI.sqlite before I start up or it goes dormant after a while.

EDIT: All fixed
 
Last edited:
I have a problem with the API.
How can I check whether the API connection to Frontier is really established or not? The value of "capi" is "false" but the authorization for the account is OK.
1710870252509.png
 
;) That was already clear to me. Thanks anyway. What surprises me is that yesterday I was able to connect without any problems
and now I can't although everything seems OK with FD (see picture).
 
;) That was already clear to me. Thanks anyway. What surprises me is that yesterday I was able to connect without any problems
and now I can't although everything seems OK with FD (see picture).
I thought that might be the case...

Missed the picture - sorry.

I guess DNS and firewall would be the next places to look, but I did see some chatter on Discord about some of the 3rd party sites having some issues.

I've had no problem this afternoon.
 
Aha, thank you ! Interesting info ! I have contacted FD. Let's see if they answer (it was hell to get to the point where you can describe your problem ...
if they have such ELITE programming ... oh god oh god oh god ...). I've just seen that the contact would have been very simple in the launcher. :rolleyes:
Here was the last entry in the json file when the API still worked:
worked:
Code:
{
  "accessToken": null,
  "refreshToken": null,
  "tokenExpiry": "2024-03-18T23:37:28.5013394Z"
}
Yesterday evening a new file was written without content or with a date 1000-00-00... or something like that, today nothing happens.
The API to INARA and EDSM are working. :oops:
 
Hello especially to @T'kael and @VerticalBlank 👋:). The FD support has replied to my mail. Here is the text:
A member of the Frontier Customer Support team has sent you a message (243907).

Support Agent Ikaros (Frontier Developments)

20 Mar 2024, 10:33 GMT

Hey CMDR,

Thanks for getting in touch.

EDDI tool is a third party tool so this could be an issue on their end.

We'd recommend reaching out to the developer VerticalBlank via XXX to see if further assistance can be provided.

If this is confirmed to be an issue on Elite API's side, please ask the developer to reach out to us directly so that we can investigate further.

Kind regards,
Support Agent Ikaros
Frontier Developments Customer Support
The information in this email is confidential and solely for the use of the intended recipient(s). If you receive this email in error, please notify the sender and delete the email from your system immediately. In such circumstances, you must not make any use of the email or its contents.
To add additional comments, please reply to this email.

This email is a service from Frontier Developments.
Can you take a look at this? There don't seem to be any problems with other CMDRs (e.g. @GJ51). What could be "broken" in my case? :unsure:
Hint:
Elite Odyssey is an EPIC account connected to FD
Game works so far, log files are read by EDDI ect. ...
EDDI v.4.0.3 is installed as a plugin from VA (latest version)
 
Last edited:
Hello especially to @T'kael and @VerticalBlank 👋:). The FD support has replied to my mail. Here is the text:
Can you take a look at this? There don't seem to be any problems with other CMDRs (e.g. @GJ51). What could be "broken" in my case? :unsure:
Hint:
Elite Odyssey is an EPIC account connected to FD
Game works so far, log files are read by EDDI ect. ...
EDDI v.4.0.3 is installed as a plugin from VA (latest version)
Please edit and remove the email address, I think it's considered personal info.
 
Back
Top Bottom