Release EDDI - Windows app for immersion and more

Status
Thread Closed: Not open for further replies.
Hey guys, new CMDR here, picked up ED just a few days ago, then stumbled upon EDDI yesterday and immediately installed it. Great work on this app, I really love it!

My problem is that EDDI doesn't say anything when I scan a planet or star, which is really sad since I want to become an explorer once I get the funds for a decent ship. EDDIs netlog monitor is working (she's giving info about the system I'm about to jump into), so that can't be the cause. I created a new personality in the speech responder tab but I haven't changed the entries for star/planet scanned or star/planet report and indeed when I click on test in that tab, it's working just as it should, it simply doesn't pick up my completed scans ingame.

I'm at a loss, do I need a better scanner than the basic discovery scanner for it to work? Or do I need the surface scanner? And yes, I know the difference between discovering a star/planet with an active scan and actually "scanning" the body when I get closer to it; the latter one should trigger the event, which isn't working. Can anyone point me in the right direction as to what I might be doing wrong?

I have similar issue, but in my case it is the present contextual system report not being given to me (using "tell me about this system" command returns me "I am not sure what system you are asking about").
The scanned body report does work fine for me but maybe it's beacuse I do have the surface scanner installed. You should try installing one.
Maybe to fix my issue I need advanced discovery scanner instead of the intermediate discovery scanner?
 
Last edited:
Hey guys, new CMDR here, picked up ED just a few days ago, then stumbled upon EDDI yesterday and immediately installed it. Great work on this app, I really love it!

My problem is that EDDI doesn't say anything when I scan a planet or star, which is really sad since I want to become an explorer once I get the funds for a decent ship. EDDIs netlog monitor is working (she's giving info about the system I'm about to jump into), so that can't be the cause. I created a new personality in the speech responder tab but I haven't changed the entries for star/planet scanned or star/planet report and indeed when I click on test in that tab, it's working just as it should, it simply doesn't pick up my completed scans ingame.

I'm at a loss, do I need a better scanner than the basic discovery scanner for it to work? Or do I need the surface scanner? And yes, I know the difference between discovering a star/planet with an active scan and actually "scanning" the body when I get closer to it; the latter one should trigger the event, which isn't working. Can anyone point me in the right direction as to what I might be doing wrong?

I'm fairly sure it's not you or your ship loadout.

Previous star/planets scan event scripts used the data directly from the Journal event, in which you would get a real-time report of your scan data. Your data would also be pushed to the EDDB server.

Now with the 'contextual data' feature, it appears that the scripts now call the BodyDetails() function which communicates to the EDDI server and pulls the 'body' data from a database that is (generally) a 24 hour-old copy of the EDDB database. If EDDB does not have any record of the body, you will get the "I'm not sure which star/planet you are asking about" message.

What I'm not sure of is whether jgm takes your scan data and merges it into his local copy of the EDDB database to keep it up-to-date between EDDB database updates.
 
Last edited:
Hey guys, new CMDR here, picked up ED just a few days ago, then stumbled upon EDDI yesterday and immediately installed it. Great work on this app, I really love it!

My problem is that EDDI doesn't say anything when I scan a planet or star, which is really sad since I want to become an explorer once I get the funds for a decent ship. EDDIs netlog monitor is working (she's giving info about the system I'm about to jump into), so that can't be the cause. I created a new personality in the speech responder tab but I haven't changed the entries for star/planet scanned or star/planet report and indeed when I click on test in that tab, it's working just as it should, it simply doesn't pick up my completed scans ingame.

I'm at a loss, do I need a better scanner than the basic discovery scanner for it to work? Or do I need the surface scanner? And yes, I know the difference between discovering a star/planet with an active scan and actually "scanning" the body when I get closer to it; the latter one should trigger the event, which isn't working. Can anyone point me in the right direction as to what I might be doing wrong?

You need a detailed surface scanner. Without this Elite doesn't write an entry to the journal so there is nothing to trigger EDDI's response.
 
I'm fairly sure it's not you or your ship loadout.

Previous star/planets scan event scripts used the data directly from the Journal event, in which you would get a real-time report of your scan data. Your data would also be pushed to the EDDB server.

Now with the 'contextual data' feature, it appears that the scripts now call the BodyDetails() function which communicates to the EDDI server and pulls the 'body' data from a database that is (generally) a 24 hour-old copy of the EDDB database. If EDDB does not have any record of the body, you will get the "I'm not sure which star/planet you are asking about" message.

What I'm not sure of is whether jgm takes your scan data and merges it into his local copy of the EDDB database to keep it up-to-date between EDDB database updates.

So then can I replace the scripts downloaded with EDDI 2 with the scripts found here http://snafets.de/elite/eddi_scripts/index.php?show=16#script_1710, for more real-time contextual system info? or are the scripts found from that link not compatible with EDDI 2 using voice attack?
 
Last edited:
Yes, it's possible. My code loops through the modules installed on the ship and looks for a match (I'd welcome any improvements that the community can offer):

SRV check (with an additional variable for whether it's enabled since on some ships I'll turn it off to save power)
Code:
{set installed to 0}
{set enabled to 0}


{for compartment in ship.compartments:
    {if compartment.module.name = "Planetary Vehicle Hangar":
        {set installed to 1}
        {if compartment.module.enabled:
           {set enabled to 1}
        }
    }
}


{SetState("srv_installed", installed)}
{SetState("srv_enabled", enabled)}

Fighter bay check
Code:
{set fighterbay to 0}


{for compartment in ship.compartments:
   {if compartment.module.name = "Fighter Hangar":
      {set fighterbay to 1}
   }
}


{SetState("fighterbay", fighterbay)}

Here's an example... I use this in my touchdown script:
Code:
{_ SRV Check _}
{F("SRV check")}
{Pause(2000)}
{if state.srv_installed && state.srv_enabled:
   SRV Ready {Occasionally(2, "for deployment.")}.
|elif state.srv_installed:
   If you are planning an excursion, please enable the Planetary Vehicle Hangar.
|else:
   No planetary vehicle hangar has been installed.
}

Very nice. I was looking for a way to check if modules are present in EDDI. I have been doing it in Voice Attack, but I wanted to do it in EDDI so that I could have it tell me if a star is scoopable only if I have a fuel scoop equipped. With your code I was able to set my jumping script to read out the star type and if it's scoopable.
 
You need a detailed surface scanner. Without this Elite doesn't write an entry to the journal so there is nothing to trigger EDDI's response.

Ok, that's probably it, then. Thanks for clarifying!

Sadly, my tiny Hauler, meant for trading as much as it possibly can to get me the credits I need for a bigger ship has no room for the Surface Scanner. I'll have to wait for my next ship. :D
 
You need a detailed surface scanner. Without this Elite doesn't write an entry to the journal so there is nothing to trigger EDDI's response.

Ok, thanks... didn't occur to me that the Journal event might not be triggering, but now I'm especially perplexed on how BodyDetails() gets the Journal 'Scan' event data when BodyDetails() is 'outside' the 'Body scanned' & 'Star scanned' event scripts and their associated event objects.
 
Last edited:
So then can I replace the scripts downloaded with EDDI 2 with the scripts found here http://snafets.de/elite/eddi_scripts/index.php?show=16#script_1710, for more real-time contextual system info? or are the scripts found from that link not compatible with EDDI 2 using voice attack?

in this script I don't see anything that might cause a problem so you could just switch the "System report" script out. You could even download the complete personalty but it is for 2.1 and miss the new context feature other than that there should be no problems. Some new responses might be empty and you have to edit them (or reset to default)
 
When or how is the ship object updated? I'm using voice attack to check ship health and call the "damage check" script. But my crippled ship will say "100% health" "fully operational" etc. Sometimes it updates after I dock. Sometimes not.
 
When or how is the ship object updated? I'm using voice attack to check ship health and call the "damage check" script. But my crippled ship will say "100% health" "fully operational" etc. Sometimes it updates after I dock. Sometimes not.

You can use the profile function of EDDI in Voice Attack. From the Voice Attack Documentation for EDDI:

[h=3]profile[/h]This function obtains the latest information from the Elite servers. It will give you up-to-date information on your ship (including its loadout and cargo), the station you are docked at, and your credit balance and rankings.

To use this function in your own commands use the 'Execute an external plugin function' command with the plugin context set to 'profile'.

Please note that you should be careful when using this function. EDDI internally restricts you to calling it once per minute, but even then this should not be used too frequently as it puts a load on Frontier's servers.

Also note that the information returned by this function is not guaranteed to be totally up-to-date, because the remote server can take a few seconds to sync its information with the changes that have taken place. If you do want to use this command then it is recommended that in your script you do something like say "Obtaining information", waiting for a couple of seconds, then calling the profile command. This means that if you call this directly after carrying out an operation (for example purchasing cargo) you are more likely to have the full information available to you in the rest of the script.
 
Last edited:
Ok, thanks... didn't occur to me that the Journal event might not be triggering, but now I'm especially perplexed on how BodyDetails() gets the Journal 'Scan' event data when BodyDetails() is 'outside' the 'Body scanned' & 'Star scanned' event scripts and their associated event objects.

BodyDetails() et al use the EDDP backend database to obtain data about systems, stars, bodies, stations etc. The data is also cached locally, so in this case when the body scan completes the information is added to the local cache as well as posted on EDDN. A subsequent call to BodyDetails() will pick up the new data either from EDDP or locally, including the updates from the body scan (if any).
 
I tried several scripts for the NPC cargo scan commenced event, but none of them worked. I thought it might have to do with the complexity of the scripts, checking whether I had valuable cargo on board and who was scanning me, but even if I clear the whole thing and just write the word test in there, EDDI simply remains completely silent when my ship is scanned by someone. Is that event broken?
 
I tried several scripts for the NPC cargo scan commenced event, but none of them worked. I thought it might have to do with the complexity of the scripts, checking whether I had valuable cargo on board and who was scanning me, but even if I clear the whole thing and just write the word test in there, EDDI simply remains completely silent when my ship is scanned by someone. Is that event broken?

It should work. Note that it specifically requires a cargo scan, so if you're being scanned by authorities or bounty hunters the event won't trigger. You can tell if it's a cargo scan because they will send you an appropriate message (and in fact it is this that EDDI uses as a trigger).
 
Station Economies not working

I have script that reads off the docked station details. With the latest update, reading out the station economies is not working. Has anything changed?

My code that reads out the info:
Code:
{P(station.name)}, in the {P(system.name)} system is controlled by the {P(station.faction)} faction, in a state of {P(station.state)}, with a {P(station.government)} government, and {system.security} security level. It is a {station.model}. This station is {(station.distancefromstar)} light seconds from the star and aligned to {P(station.allegiance)}, with an economy of 

{for economy in station.economies:
  {economy}
}
 
I have script that reads off the docked station details. With the latest update, reading out the station economies is not working. Has anything changed?

My code that reads out the info:
Code:
{P(station.name)}, in the {P(system.name)} system is controlled by the {P(station.faction)} faction, in a state of {P(station.state)}, with a {P(station.government)} government, and {system.security} security level. It is a {station.model}. This station is {(station.distancefromstar)} light seconds from the star and aligned to {P(station.allegiance)}, with an economy of 

{for economy in station.economies:
  {economy}
}

Yep, as per the changelog we only have access to the primary economy. This is because secondary economy information isn't available from journal updates.
 
It should work. Note that it specifically requires a cargo scan, so if you're being scanned by authorities or bounty hunters the event won't trigger. You can tell if it's a cargo scan because they will send you an appropriate message (and in fact it is this that EDDI uses as a trigger).

I often get a message like "[DIRECT][Internal Security Service]: You're clean. Proceed, pilot." or something of the sort AFTER the scan is completed, so I guess these are the messages you mean? EDDI however still remains silent :(
 
I often get a message like "[DIRECT][Internal Security Service]: You're clean. Proceed, pilot." or something of the sort AFTER the scan is completed, so I guess these are the messages you mean? EDDI however still remains silent :(

That's not a cargo scan, that's a kill warrant scan.
 
I'm having the oddest issue atm, v2.2

Whenever I jump into Shinrarta Dezhra I get no ((EDDI Jumping)) or ((EDDI Jumped)) events being executed. All other systems seem fine. The only thing I could point this to was that I originally had my home system in eddi set to Shinrarta. I cleared it and changed it to another system though and still no events being run in Shinrarta. The journal has the jumps in so I'm cafuffled :)
 
I'm having the oddest issue atm, v2.2

Whenever I jump into Shinrarta Dezhra I get no ((EDDI Jumping)) or ((EDDI Jumped)) events being executed. All other systems seem fine. The only thing I could point this to was that I originally had my home system in eddi set to Shinrarta. I cleared it and changed it to another system though and still no events being run in Shinrarta. The journal has the jumps in so I'm cafuffled :)

Could you turn on debugging, jump in to Shinrarta Dezhra, then send the logs over? I'll take a look and see.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom