Release EDDI - Windows app for immersion and more

Status
Thread Closed: Not open for further replies.
Just bought myself another ED account and I would love for EDDI2 to be able to link to both accounts and if I change personalities it uses a different voice.
 
Apologies for the delay, but I've just release EDDI 2.2.3. This contains a number of fixes for issues with Elite 2.3, most notably an issue that was causing EDDI to crash.[/LIST]

Awesome stuff, thanks so much for your hard work on this tool, it really adds to the immersion!

Couple of bugs:

* Fuel is no longer tracked properly, my in-game fuel-gauge is full, but EDDI thinks it's empty and warns me to refuel after every jump.

* When joining another ship via Telepresence, EDDI still thinks I'm in my own ship and announces jumps etc as if it was my ship (not sure if there actually are journal entries for telepresence..)
 
Just updated .. and in testing , getting NOT SET back as the response to my Command , and not the name of the Ship I'm in.
((shipin))
Execute external plugin, 'EDDI 2.2.3' and wait for return
Set Text [script] to 'You are currently aboard a {TXT:Ship model (spoken)}, the $='
Execute external plugin, 'EDDI 2.2.3' and wait for return
Set Text [EDDI ship script] to [Not Set]
 
Last edited:
thanx for the update!

Bug found: Exporting to Coriolis is not functioning.
Shipnames: Can this be imported through the API ?

thanx for the superb work!
 
Apologies for the delay, but I've just release EDDI 2.2.3. This contains a number of fixes for issues with Elite 2.3, most notably an issue that was causing EDDI to crash.

Please note that if you are experiencing a crash with EDDI starts then you must remove the file %APPDATA\EDDI\credentials.json for EDDI to start and for you to upgrade. If you do this then you will need to reauthenticate the companion app after upgrading. Alternatively you can download and apply the upgrade directly from https://www.mcdee.net/elite/EDDI.exe.

The full changelog is as follows:

  • Fix issue where undocumented change in Frontier API would cause EDDI to crash
  • Update netlog monitor to handle new log format
  • Add ship definition for Dolphin
  • Add module definitions for Dolphin bulkheads

You, Sir, are a real gentleman.
 
FYI at current the following items are not working:

  • Fuel and cargo information. This has been removed from the Frontier companion API
  • Engineering information for modules. This has been removed from the Frontier companion API
  • Export to Coriolis for anything other than the currently active ship. The required information has been removed from the Frontier companion API

There are possible workaround to some of these items that will be investigated as part of EDDI 2.3.
 
FYI at current the following items are not working:

  • Fuel and cargo information. This has been removed from the Frontier companion API
  • Engineering information for modules. This has been removed from the Frontier companion API
  • Export to Coriolis for anything other than the currently active ship. The required information has been removed from the Frontier companion API

There are possible workaround to some of these items that will be investigated as part of EDDI 2.3.

WHAT?? Why are they doing this??
Exporting especially engineering information was so helpful while planning ahead doing other engineering ideas...


jgm, keep up the good work!
 
2.2.3 constant crashing on start

The configuration program crashes every time on start.
I curse Frontier for this since it's probably due to some API setting that I haven't figured out how to remove.
 
Anyone happen to show a screenshot of the "setspeechresponderpersonality" command? I am not a programmer, the documentation could be in Thargoid and I would be able to understand it just as much.
 
thanx for the update!

Bug found: Exporting to Coriolis is not functioning.

The ship I'm currently flying can be exported to Coriolis. All of my stored ships can't be (but I haven't flown them since 2.0 or before...)

EDIT: NVM; @jgm already replied (I thought I was replying to one of the last posts in this thread, obviously not)
 
Last edited:
I just installed it. This is not a complaint.

Before I changed the home system and distance from home system settings I was hearing all of the BGS updates. I was just surprised to hear how much is going on in the background.
 
Indeed, he'll get on it as soon as he can. In my experience he fixes any problems pretty damn quick. Only now I realize how much I miss EDDI2 not telling me everything. But I'm glad I got some of my own custom scripts in EDDI VA that still work cause they are triggered by the journal and not the API.



So I take it, this is why I'm still gettting ' NOT SET ' spoken back at me instead of my Ship Name..... Really Really Really would like my own EDDI server running at my house , instead of 'yours' jgm :)
 
Last edited:
So I take it, this is why I'm still gettting ' NOT SET ' spoken back at me instead of my Ship Name..... Really Really Really would like my own EDDI server running at my house , instead of 'yours' jgm :)

jgm doesn't run any EDDI servers; EDDI is purely a client-side app. It -does- read data from the game journals and the Companion API however, and the Companion API is something run by FDev, so it's an "official" Elite Dangerous source..
 
The following script gives only response to Shipname() and ship.value.

Am I doing something wrong, or is this related to the changes in 2.3?

Code:
{ShipName()}
{Pause(500)}

{ship.value}

{for module in ship.bulkheads:
   {module.name}
   {module.class}
   {module.grade}
   {module.value}
   {module.cost}
   {module.enabled}
   {module.priority}
   {module.health}
}
 
Last edited:
FYI at current the following items are not working:

  • Fuel and cargo information. This has been removed from the Frontier companion API
  • Engineering information for modules. This has been removed from the Frontier companion API
  • Export to Coriolis for anything other than the currently active ship. The required information has been removed from the Frontier companion API

There are possible workaround to some of these items that will be investigated as part of EDDI 2.3.

Cargo, dang. That includes the limpet check.
And it seems like complete module information is missing, my fighter bay check also doesn't work anymore...
The nerf bat has been swung in a wiiiide angle, it seems...
:(

Hope they'll 'fix' it again soon, but i wouldn't hold my breath on that one...
 
Cargo, dang. That includes the limpet check.
And it seems like complete module information is missing, my fighter bay check also doesn't work anymore...
The nerf bat has been swung in a wiiiide angle, it seems...
:(

Hope they'll 'fix' it again soon, but i wouldn't hold my breath on that one...

It looks like all module information (not only engineering information) has been taken out of the API and was moved to the journal. I have a script checking for the presence of a discovery scanner and a docking computer but that script isn't working now. I've looked at my latest journal and it looks like the module info is there at the start of the game and is updated when you get into another one of your ships. Here's hoping JGM will be able to change EDDI into using the journal instead of the API for the module info (or, even better maybe, Frontier putting the info they removed from the API back in)
 
Last edited:
Module information (but not cargo, fuel or engineering) should be available for the active ship. I'll take a look to see why it isn't showing up.
 
Hey cmdrs! Well just here to report EDDI simple crashes all my OS and VA, and Astra and everything else really lately! Too sad to bear! I just need EDDI functions in my game! Oh man!
 
Module information (but not cargo, fuel or engineering) should be available for the active ship. I'll take a look to see why it isn't showing up.

Still getting that 'my test buggy' after returning to ship when i've been in the srv. Journal didn't improve in this case, i assume?
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom