Thank you so much!!
- Status
Thank you so much!!
Bit of a bug
Hey I absolutely love your program and use it all the time with voice attack but I have a bit of a bug.
My ship monitor is not updating. It's listing 3 ships I had a week ago and not updating at all, even through multiple resets and a fresh install. Is there a good way to fix this?
Hey I absolutely love your program and use it all the time with voice attack but I have a bit of a bug.
My ship monitor is not updating. It's listing 3 ships I had a week ago and not updating at all, even through multiple resets and a fresh install. Is there a good way to fix this?
It's a known bug, already in the works afaik.
Expect the awesome new EDDI-Team to release something alongside 2.4 or shortly thereafter (my estimate).
You could look things like that up here: https://github.com/EDCD/EDDI/issues
Awesome, thanks for the info and the quick reply.
Thanks to a lot of sterling work by the entire team, we are very happy to announce a handover build 2.3.1 and a public beta 2.4.0-b2. Both are available from the new release page. (Before you ask, we burned the 2.4.0-b1 version number in our testing of the auto-update mechanism.)
You can see the readme and the wiki on GitHub. These are also linked in-app on the "EDDI" tab, as is the change log.
2.3.1 is our minimal-change transitional build and behaves exactly the same as 2.3 except that it uses the new update servers.
2.4.0-b2 is our first cut at getting ready for ED 2.4, though it will also work just fine with ED 2.3. It is a work in progress and you can expect to see more betas this coming week as support for the new events in ED 2.4 gets completed. Here is the changelog.
2.4.0-b2 has been very stable for us and we'd love to have as many of you as possible helping us test it.
As we don't have access to jgm's servers, we can't make EDDI 2.3 aware of these new builds. However once you manually install either 2.3.1 or 2.4.0-b2 then EDDI will resume auto-updating as normal. When you manually install, Windows Defender will probably object to the installer because it isn't code-signed. Just click "More info" then "Run anyway". This won't be an issue for auto-updating going forward. One more thing: for security reasons your credentials will be cleared on the "Frontier API" tab and you will need to log in again in the usual way.
Very many thanks to my teammates T'kael, Hoodathunk and Darkcyde for doing a ton of work in a very short time.
To everyone else: enjoy!
You can see the readme and the wiki on GitHub. These are also linked in-app on the "EDDI" tab, as is the change log.
2.3.1 is our minimal-change transitional build and behaves exactly the same as 2.3 except that it uses the new update servers.
2.4.0-b2 is our first cut at getting ready for ED 2.4, though it will also work just fine with ED 2.3. It is a work in progress and you can expect to see more betas this coming week as support for the new events in ED 2.4 gets completed. Here is the changelog.
2.4.0-b2 has been very stable for us and we'd love to have as many of you as possible helping us test it.
As we don't have access to jgm's servers, we can't make EDDI 2.3 aware of these new builds. However once you manually install either 2.3.1 or 2.4.0-b2 then EDDI will resume auto-updating as normal. When you manually install, Windows Defender will probably object to the installer because it isn't code-signed. Just click "More info" then "Run anyway". This won't be an issue for auto-updating going forward. One more thing: for security reasons your credentials will be cleared on the "Frontier API" tab and you will need to log in again in the usual way.
Very many thanks to my teammates T'kael, Hoodathunk and Darkcyde for doing a ton of work in a very short time.
To everyone else: enjoy!
Last edited:
If this still happens with 2.4.0-b2 please let us know.
how do we upgrade from the previous version, do we just run the exe?
Yes, the exe on the GitHub release page is the installer.
As VerticalBlank, said, yes... but with a recommendation that you should delete the original 'EDDI' folder first to ensure you get a clean install... either in your 'ProgramFiles' folder if you're not using EDDI with VoiceAttack or in the Voice Attack 'Apps' folder if you are.
With this very minor update (for reasons VerticalBlank previously explained) you shouldn't have to touch any of your EDDI files in your user AppData/Roaming/EDDI folder.
Last edited:
Since, as of this writing, we are still on game version 2.3, will installing the EDDI 2.4b2 cause any problems? There will be a lot of events that will never happen until 2.4 drops, that is. Also, some events that are in 2.3 might change in 2.4. Most engineers and programmers just love to change things.
2.4b2 will be fine with ED 2.3, I'm running it myself.
No need, the installer is specifically designed to run on top of an existing installation because that's a requirement for the auto-updater to work properly.
I noticed a while back that EDDI supports an option to have TTS output to a text file in real time.
Does anyone know of a utility that will display subtitles over the top of the game window when reading from that file and detect changes in real time?
Or this more of a feature request for the next version of EDDI?
- S
Does anyone know of a utility that will display subtitles over the top of the game window when reading from that file and detect changes in real time?
Or this more of a feature request for the next version of EDDI?
- S
I noticed a while back that EDDI supports an option to have TTS output to a text file in real time.
Does anyone know of a utility that will display subtitles over the top of the game window when reading from that file and detect changes in real time?
Or this more of a feature request for the next version of EDDI?
- S
Bump... That would be indeed wonderful...
This caught my eye ,don't have access to jgm's servers, Ages ago I asked jgm , to allow players to run the 'server' themselves , ie 2nd PC.
Is this possible ?, that's if EDDI is going to a to 'another server' to crunch data.. and send it back . again not that sure how it's set up.
Last edited:
Getting EDDI off of its dependence on the EDDP server is being investigated, but no immediate changes are in the works.
FWIW, I think individual servers are not the way to go. It would be a nightmare for developers to respond to individual issues on personal server installation, setups, and operation. Too many variables that developers can't control and the cost/benefit ratio would be exhorbitantly high.
Last edited:
To qualify, I was specifically talking about the server that tells EDDI when an update is available. That is now hosted on GitHub so that all the dev team have access.
This thought had indeed occurred. My only hesitatiion is that it feels rude to do that without asking jgm first. However, he's not currently answering our hails so I think we'll review things once EDDI 2.4 is out of beta.
- Status