Please also vote on this one: https://issues.frontierstore.net/issue-detail/69762
) cast.
So, it's been a long time since my last release. A lot longer than I had hoped. But, the time is finally here for a new one! 
As EDDI v4.1.0 is still in beta for now, take this new release as a beta too, because there are going to be changes in the next released version of EDDI that will need me to update my personality, but I'll try to be a bit faster for that one.
I wanted to release this now, before the 'Trailblazers' patch in just over a week, as I'm sure I'll want to get involved in that for a while, and I'm also sure there will be new things to add to my EDDI personality for it too.
This new version is built for EDDI v4.1.0-b3, and while some of it may work for previous releases of EDDI, most of it will not. So don't use this if you are still on EDDI v4.0.4 or lower.
The change log is big. Really big. So I'm not going to paste it in this post. Instead, I have started a new separate change log file and included it below along with the distribution ZIP file.
There is so much updated, but one of the new things is an Exobiology Report to tell you what bio species may be on a body. I've also added a new read me file listing all the preference options in all the scripts. Finally, I've tried to overhaul my autorouting system to make it more comprehensive, and more robust. It still needs a bit more testing I think, but it's in a good place right now.
Anyway, as usual, if you find anything that doesn't work quite right, or is outright bugged, please let me know and I'll try to fix it for my next release.
Enjoy, and I'll see you in The Black, Commanders! o7
DC
EDIT: See updates below.
As EDDI v4.1.0 is still in beta for now, take this new release as a beta too, because there are going to be changes in the next released version of EDDI that will need me to update my personality, but I'll try to be a bit faster for that one.
I wanted to release this now, before the 'Trailblazers' patch in just over a week, as I'm sure I'll want to get involved in that for a while, and I'm also sure there will be new things to add to my EDDI personality for it too.
This new version is built for EDDI v4.1.0-b3, and while some of it may work for previous releases of EDDI, most of it will not. So don't use this if you are still on EDDI v4.0.4 or lower.
The change log is big. Really big. So I'm not going to paste it in this post. Instead, I have started a new separate change log file and included it below along with the distribution ZIP file.
There is so much updated, but one of the new things is an Exobiology Report to tell you what bio species may be on a body. I've also added a new read me file listing all the preference options in all the scripts. Finally, I've tried to overhaul my autorouting system to make it more comprehensive, and more robust. It still needs a bit more testing I think, but it's in a good place right now.
Anyway, as usual, if you find anything that doesn't work quite right, or is outright bugged, please let me know and I'll try to fix it for my next release.
Enjoy, and I'll see you in The Black, Commanders! o7
DC
EDIT: See updates below.
Last edited:
Hi all,
Just a quick update. I've realised that the Exobiology Report does not work correctly when it's called from the 'Surface signals detected' event script. This is because of a known issue with EDDI v4.1.0-b3 regarding state variables (see here). At least, I think it is. I'll need to retest it when the next version of EDDI is released.
It should still work when called from the 'Touchdown' event (I think), and does work OK if manually run right after bio signals have been detected.
So keep this in mind when you're out looking for Exobiological samples.
o7
DC
Just a quick update. I've realised that the Exobiology Report does not work correctly when it's called from the 'Surface signals detected' event script. This is because of a known issue with EDDI v4.1.0-b3 regarding state variables (see here). At least, I think it is. I'll need to retest it when the next version of EDDI is released.
It should still work when called from the 'Touchdown' event (I think), and does work OK if manually run right after bio signals have been detected.
So keep this in mind when you're out looking for Exobiological samples.
o7
DC
Speaking of which...
I am pleased to announce that EDDI version 4.1.0 is now available. The changelog is available at https://github.com/EDCD/EDDI/releases/tag/Release/4.1.0 and the installer is available from the app or from https://github.com/EDCD/EDDI/releases/download/Release/4.1.0/EDDI-4.1.0.exe. 
I am pleased to announce that EDDI version 4.1.0 is now available. The changelog is available at https://github.com/EDCD/EDDI/releases/tag/Release/4.1.0 and the installer is available from the app or from https://github.com/EDCD/EDDI/releases/download/Release/4.1.0/EDDI-4.1.0.exe. Hello @T'kael ,
I don't know if you will be informed if the post has been closed when you make additional comments on github.
So here's a quick info from me, the translations into German have been corrected and supplemented.
Many thanks for your efforts
github.com
I don't know if you will be informed if the post has been closed when you make additional comments on github.
So here's a quick info from me, the translations into German have been corrected and supplemented.
Many thanks for your efforts
Some tabs are not translated · Issue #2701 · EDCD/EDDI
What's Wrong (please be as specific as possible) The pages (tabs) EDDI, Commander Monitor, Frontier API and Text-to-Speech are currently not translated (into German). The function is not impaired (...
github.com
@ T'kael
Many thanks again for your hard work. Much appreciated. Can't play without EDDI.
Many thanks again for your hard work. Much appreciated. Can't play without EDDI.
Ever since I upgraded to 4.1.0 I've been getting weird behavior when I jump. At least I think that's when it started happening, rather than due to an update to ED itself.
I will hear "ship name is jumping to the system" (the system name should appear there but does not). It also says "Welcome Home, Commander" both as I start jumping and when I enter the system, and frequently repeats "I don't know which system you are asking about".
One time tonight I jumped into a system and it did not do that. That particular system had already been discovered, although not by me. The next system was back to welcoming me home, though, because it was unexplored. So, I found another system where I already had data and jumped there. EDDI behaved normally.
I'm about 26K LY away from Shin Dezh, so there are a lot of unexplored systems out here.
Is it possible that this is happening due to this change in 4.1.0: "Updated star system lookups to use Spansh APIs rather than EDSM APIs."
I use EDMC to send my data to EDDN. I have an account with EDSM, but not with Spansh.
I will hear "ship name is jumping to the system" (the system name should appear there but does not). It also says "Welcome Home, Commander" both as I start jumping and when I enter the system, and frequently repeats "I don't know which system you are asking about".
One time tonight I jumped into a system and it did not do that. That particular system had already been discovered, although not by me. The next system was back to welcoming me home, though, because it was unexplored. So, I found another system where I already had data and jumped there. EDDI behaved normally.
I'm about 26K LY away from Shin Dezh, so there are a lot of unexplored systems out here.
Is it possible that this is happening due to this change in 4.1.0: "Updated star system lookups to use Spansh APIs rather than EDSM APIs."
I use EDMC to send my data to EDDN. I have an account with EDSM, but not with Spansh.
Hello @Hrdina ,
please take a look at github. The problems have already been addressed there. A possible short-term solution has also been presented.
github.com
The incorrect statement that you are already at home is probably because both variables are not assigned when comparing whether it is the home system or not.
Why ? Because the search for the correct name probably takes a little too long. Have you entered a home system in EDDI ? Then this problem should not actually occur.
At least that's how I understood @T'kael.
The second problem could also be related to this. But @T'kael isn't sure about that yet. I've also been a bit further out the last few days. I didn't have the problem with the system not being recognized. Some time ago, when there was a similar problem, I had changed the query of state variables. That tells us @T'kael or @Darkcyde. I don't remember that. Instead of querying the variable with
So you could give it a try.
Translated with DeepL.com (free version)
please take a look at github. The problems have already been addressed there. A possible short-term solution has also been presented.
Keep calling all system my Home and spam "I'm not sure which system you're asking about" · Issue #2702 · EDCD/EDDI
Expected Only call a system my Home when it match the system configured on EDDI Observed Each time I jump to a system, EDDI welcome me Home, and start spamming one or two "Im' not sure which system...
github.com
Why ? Because the search for the correct name probably takes a little too long. Have you entered a home system in EDDI ? Then this problem should not actually occur.
At least that's how I understood @T'kael.
The second problem could also be related to this. But @T'kael isn't sure about that yet. I've also been a bit further out the last few days. I didn't have the problem with the system not being recognized. Some time ago, when there was a similar problem, I had changed the query of state variables. That tells us @T'kael or @Darkcyde. I don't remember that. Instead of querying the variable with
state.xxx_yyy, you should use GetState(xxx_yyy). This is still in my scripts and I haven't had any problems so far. T'kael says that it is not related to this, but it doesn't do any harm either.So you could give it a try.
Translated with DeepL.com (free version)
Last edited:
Thanks @nepomuk I'll have a look at GitHub tonight or over the weekend.Hello @Hrdina ,
please take a look at github. The problems have already been addressed there. A possible short-term solution has also been presented.
The incorrect statement that you are already at home is probably because both variables are not assigned when comparing whether it is the home system or not.Keep calling all system my Home and spam "I'm not sure which system you're asking about" · Issue #2702 · EDCD/EDDI
Expected Only call a system my Home when it match the system configured on EDDI Observed Each time I jump to a system, EDDI welcome me Home, and start spamming one or two "Im' not sure which system...
Why ? Because the search for the correct name probably takes a little too long. Have you entered a home system in EDDI ? Then this problem should not actually occur.
At least that's how I understood @T'kael.
The second problem could also be related to this. But @T'kael isn't sure about that yet. I've also been a bit further out the last few days. I didn't have the problem with the system not being recognized. Some time ago, when there was a similar problem, I had changed the query of state variables. That tells us @T'kael or @Darkcyde. I don't remember that. Instead of querying the variable withstate.xxx_yyy, you should useGetState(xxx_yyy). This is still in my scripts and I haven't had any problems so far. T'kael says that it is not related to this, but it doesn't do any harm either.
So you could give it a try.
Translated with DeepL.com (free version)
I've been using EDDI for a long time, and have had Shinrarta set as my home system for years. I'll have to check to see whether that's become un-set somehow.
While I've not yet got around to sitting down to fully test the release 4.1.0, I have also noticed some problems. In my case, I've seen that ShipName() isn't always being spoken, and (I thought) that some state variables were being 'forgotten'. However, looking at the reports of other commanders problems, I am beginning to think that maybe it's not the state variables, but an intermittent problem with executing functions?
Most of the problems I've seen people report could be attributed to SystemDetails() and BodyDetails() not returning a value. It would also explain the problems I've been having too. Yes, it could be a problem with state variables being passed to those functions, but that wouldn't explain why ShipName() also is intermittent, as that has nothing passed to it.
I need to get around to actually testing this, but with it being so random and intermittent, I'd need to do a lot of playing just to see if it happens first. Anyway, 'food for thought' as they say. It may be a cause or a red herring.
Most of the problems I've seen people report could be attributed to SystemDetails() and BodyDetails() not returning a value. It would also explain the problems I've been having too. Yes, it could be a problem with state variables being passed to those functions, but that wouldn't explain why ShipName() also is intermittent, as that has nothing passed to it.
I need to get around to actually testing this, but with it being so random and intermittent, I'd need to do a lot of playing just to see if it happens first. Anyway, 'food for thought' as they say. It may be a cause or a red herring.
The fact that the problem may have something to do with the status variables is just a guess on my part, because I haven't had this problem yet.
And with the “Star report” I still have the query with GetState
The fact that the ship's name was not said occurred maybe twice or three times with a distance of approx. 6000 ly.
And the problem with “Hello, you are at home ...” occurred exactly once for me. But the problem can be easily avoided by assigning the home station
and checking for an empty variable.
But I'm afraid you might be right that the problem lies deeper. But we'll have to rely on @T'kael for that.
And with the “Star report” I still have the query with GetState
{set reportbody to BodyDetails(GetState('eddi_context_star_star'), system.systemname)}.The fact that the ship's name was not said occurred maybe twice or three times with a distance of approx. 6000 ly.
And the problem with “Hello, you are at home ...” occurred exactly once for me. But the problem can be easily avoided by assigning the home station
and checking for an empty variable.
But I'm afraid you might be right that the problem lies deeper. But we'll have to rely on @T'kael for that.
I had a look at my Commander Responder settings, and sure enough a number of values there (Home System, Home Station, Squadron System, Squadron Faction) were all cleared. I know that I didn't do that, so I suspect it was something that happened when I moved to version 4.1. Reading the github discussion gave me the impression that I'm not the only one who saw that.
I re-entered those Home System values, quit EDDI, then restarted to make sure the settings stuck. This seems to have fixed the "Welcome Home" problem, but I am still having issues with EDDI saying things like "<ship name> is jumping to the system" and "I don't know which system you are asking about".
I'm using the default EDDI personality, so haven't modified any of the responses.
I noticed that Tkael added the Bug tag to this issue, so hopefully that means he already knows all of the above.
I re-entered those Home System values, quit EDDI, then restarted to make sure the settings stuck. This seems to have fixed the "Welcome Home" problem, but I am still having issues with EDDI saying things like "<ship name> is jumping to the system" and "I don't know which system you are asking about".
I'm using the default EDDI personality, so haven't modified any of the responses.
I noticed that Tkael added the Bug tag to this issue, so hopefully that means he already knows all of the above.