Release EDDI - Windows app for immersion and more

Status
Thread Closed: Not open for further replies.
I tried m8 but I get sending log failed

I just checked and it appears that you have a huge EDDI.log file, due to leaving verbose logging on over an extended period.

Best thing to do will be to shut down EDDI, remove %APPDATA%\EDDI\eddi.log, restart EDDI and from there try the jump/send process as mentioned above. And turn off verbose logging afterwards :)
 
will do but that's odd as I've never had verbose logging on before

sent the log now

Thanks. Looks like your local database has been corrupted, please could you shut down EDDI and remove %APPDATA%\EDDI\EDDI.sqlite file then restart EDDI? If you have EDSM integration then re-fetch your EDSM logs on the relevant EDDI tab to keep details of how many times you have visited each system.
 
I finally got enough credits to buy my first ship dedicated to exploration ( https://coriolis.edcd.io/outfit/cobra_mk_iii/02A4D4A3D1A3D4C----0202340p43v62i2f.Iw18AxkA.Aw1-kA== ) and immediately tested EDDI with the scanner. This time, she finally does speak, but unfortunately, there seems to be problem in the script Body scanned that I got from http://snafets.de/elite/eddi_scripts/index.php?show=4#script_438

When she gets to the point of describing the atmosphere of the scanned body, EDDI just omits that entire segment and jumps straight to volcanism. I don't understand why, since the code specifically checks if the body has an atmosphere or not end even has an else case at the end of the segment, so EDDI should be saying something no matter which body I scan.

Has the event.atmosphere variable been removed or I am still doing something wrong?
 
I finally got enough credits to buy my first ship dedicated to exploration ( https://coriolis.edcd.io/outfit/cobra_mk_iii/02A4D4A3D1A3D4C----0202340p43v62i2f.Iw18AxkA.Aw1-kA== ) and immediately tested EDDI with the scanner. This time, she finally does speak, but unfortunately, there seems to be problem in the script Body scanned that I got from http://snafets.de/elite/eddi_scripts/index.php?show=4#script_438

When she gets to the point of describing the atmosphere of the scanned body, EDDI just omits that entire segment and jumps straight to volcanism. I don't understand why, since the code specifically checks if the body has an atmosphere or not end even has an else case at the end of the segment, so EDDI should be saying something no matter which body I scan.

Has the event.atmosphere variable been removed or I am still doing something wrong?

try {reportbody.atmosphere}. The body scanned event calls a new body report event. So you have to get with the new lingo.
 
I finally got enough credits to buy my first ship dedicated to exploration....

Congrats on the new ship, one tiny piece of advice if I must - put on a stronger shield. 3Ds are paper and while sure, this is an exploration build you'd be amazed how quickly on botched landing can take them all the way down. While in the bubble if you get interdicted, commander or NPC, you're only going to survive a few shots. One last tip - if you do get interdicted by something big enough to mass lock you, say an Anaconda, don't low wake into Supercruise pick another system and jump there. When high waking to another system you can't get mass locked by anything so you'll escape faster that way.
 
Does anyone have a really comprehensive profile for VoiceAttack that integrates with EDDI? The default one that comes with EDDI is very, very basic. There's only like 20 commands in total.
 
I finally got enough credits to buy my first ship dedicated to exploration ( https://coriolis.edcd.io/outfit/cobra_mk_iii/02A4D4A3D1A3D4C----0202340p43v62i2f.Iw18AxkA.Aw1-kA== ) and immediately tested EDDI with the scanner. This time, she finally does speak, but unfortunately, there seems to be problem in the script Body scanned that I got from http://snafets.de/elite/eddi_scripts/index.php?show=4#script_438

When she gets to the point of describing the atmosphere of the scanned body, EDDI just omits that entire segment and jumps straight to volcanism. I don't understand why, since the code specifically checks if the body has an atmosphere or not end even has an else case at the end of the segment, so EDDI should be saying something no matter which body I scan.

Has the event.atmosphere variable been removed or I am still doing something wrong?

I put off uploading a new version while I tested changes. Sorry about that. Revised script uploaded.
 
try {reportbody.atmosphere}. The body scanned event calls a new body report event. So you have to get with the new lingo.
I added {set reportbody to BodyDetails(state.eddi_context_body_name, state.eddi_context_body_system)} at the top of the script and now atmosphere reporting works, Thanks very much :D

However, in the meantime I've noticed that while the volcanism reporting in the same script works fine as long as there is any volcanism on the scanned body; EDDI omits the volcanism segment if it doesn't have any, although the code would indicate that she should at least say that there is no volcanic activity. I tried replacing event.volcanism with reportbody.volcanism, but that just made her omit the segment in all cases. Any other ideas on how to get a negative report out of the segment?

Congrats on the new ship, one tiny piece of advice if I must - put on a stronger shield. 3Ds are paper and while sure, this is an exploration build you'd be amazed how quickly on botched landing can take them all the way down. While in the bubble if you get interdicted, commander or NPC, you're only going to survive a few shots. One last tip - if you do get interdicted by something big enough to mass lock you, say an Anaconda, don't low wake into Supercruise pick another system and jump there. When high waking to another system you can't get mass locked by anything so you'll escape faster that way.
If by low-waking and high-waking you mean that I should directly jump to another system instead of trying to get beack into supercruise (still learning the slang terms, relatively new to the game here :p ) that's a nice tip and I'll keep it in mind, thanks. However, until now, I've always been able to evade interdiction attempts (which afaik were all by NPCs so they might have been of the easy sort, not sure if it's harder if a CMDR attempts to interdict me), so I never had the situation before.

As for the shields, I flew around in a Hauler without any shields for the past week, so I know what being careful when flying in tight spaces is all about ;) I'm really not sure if I need a bigger shield since it's going to reduce my jump range. So I'll try landing on a few planets soon and see what that is like before I buy one; those 232k insurance money won't be that big a problem if I mess it up :p

Thank you for the tips anyways, much appreciated :D

EDIT: I had half an hour before I needed to go to work so I thought I could try some landings, now the servers go down for maintenance for half an hour... Great timing xD
 
Last edited:
I put off uploading a new version while I tested changes. Sorry about that. Revised script uploaded.

Hey man, looked at your scripts... I like the direction you're going with them.

I do have one comment/concern... have you fully tested the 'Mission accepted' and 'MissionType' scripts? I haven't tried them but I can't see how they would work because you're not using State Variables to pass info between the two. @jgm is very specific that "Cottle does not retain state between templates".

For example, when calling 'MissionType', you shouldn't assume that the event object is still within the 'Mission accepted' context and should pass event.name as a State Variable. Also, shouldn't type, part1 & part2 be State Variables for use in the 'Mission accepted' and 'MisFacState' scripts?


Cheers!
 
Last edited:
I added {set reportbody to BodyDetails(state.eddi_context_body_name, state.eddi_context_body_system)} at the top of the script and now atmosphere reporting works, Thanks very much :D

However, in the meantime I've noticed that while the volcanism reporting in the same script works fine as long as there is any volcanism on the scanned body; EDDI omits the volcanism segment if it doesn't have any, although the code would indicate that she should at least say that there is no volcanic activity. I tried replacing event.volcanism with reportbody.volcanism, but that just made her omit the segment in all cases. Any other ideas on how to get a negative report out of the segment?

I wouldn't recommend putting any response there, but if you want to...
Code:
{_ Volcanism}
{set volcanism to token(reportbody.volcanism,"volcanism","")}

{if reportbody.volcanism = "":
   there's no volcanism on gas giants you silly goose
|elif find(volcanism, "magma") > 0:
   {volcanism} flows on the surface.
|elif find(volcanism, "geysers") > 0:
   {volcanism} 
   {OneOf("detected", "are present")}
   on the surface.
|elif len(reportbody.volcanism) > 0:
     The {reportbody.bodyclass} exhibits signs of volcanism, such as {volcanism}.
}
of course you could make a check for gas giants, but yea
 
Last edited:

EDDI isn't a pure VoiceAttack application. The existing commands are generally enough to get EDDI to respond to most requests it is able to handle, especially now that context is in place, but if you're looking for things like handling landing gear, docking requests etc. then that's not really EDDI-specific functionality and you might want to look at something like the HCS voicepacks for that side of things.

Unless, of course, someone out there has their own VoiceAttack profile integrated with EDDI and would be willing to share.
 
EDDI isn't a pure VoiceAttack application. The existing commands are generally enough to get EDDI to respond to most requests it is able to handle, especially now that context is in place, but if you're looking for things like handling landing gear, docking requests etc. then that's not really EDDI-specific functionality and you might want to look at something like the HCS voicepacks for that side of things.

Unless, of course, someone out there has their own VoiceAttack profile integrated with EDDI and would be willing to share.

I have a vap that is quite good. Though it requires a ED key binding update as it also complements an x52Pro profile. Basically, I combined the work of a few others along with a few tweaks of my one to have one comprehensive package. Likely i could share if you have an x52Pro hotas as well, or would not mind a custom key binding for ED?!

Basically, what I use would include:
- custom vap
- custom ED keybinding
- custom x52 ED profile
- custom EDDI profile
 
Last edited:
I have a vap that is quite good. Though it requires a ED key binding update as it also complements an x52Pro profile. Basically, I combined the work of a few others along with a few tweaks of my one to have one comprehensive package. Likely i could share if you have an x52Pro hotas as well, or would not mind a custom key binding for ED?!

Basically, what I use would include:
- custom vap
- custom ED keybinding
- custom x52 ED profile
- custom EDDI profile

YES PLEASE!!! I have an X52 as well, this would be perfect! Is it TTS or do you use voice packs? I just spent $40 on British Amy TTS so I'm hoping to use a profile that has TTS instead of voice packs.
 
I wouldn't recommend putting any response there, but if you want to...
Code:
{_ Volcanism}
{set volcanism to token(reportbody.volcanism,"volcanism","")}

{if reportbody.volcanism = "":
   there's no volcanism on gas giants you silly goose
|elif find(volcanism, "magma") > 0:
   {volcanism} flows on the surface.
|elif find(volcanism, "geysers") > 0:
   {volcanism} 
   {OneOf("detected", "are present")}
   on the surface.
|elif len(reportbody.volcanism) > 0:
     The {reportbody.bodyclass} exhibits signs of volcanism, such as {volcanism}.
}
of course you could make a check for gas giants, but yea

Nope, not working :( That script just makes EDDI omit the entire volcanism segment, no matter if the scanned body has any or not. Also, I wasn't talking solely of gas giants, there are other smaller bodies without volcanism.

Also I spoke too soon about CMDR Smiors fix for the atmosphere segment, I realized that it simply makes EDDI assume that EVERY scanned body has no atmosphere.

I admit that I am lost with these scripts. I have some slight coding knowledge, but I just don't get why I have to take a detour with a reportbody object when the variables list clearly shows that event.atmosphere and event.volcanism should work just fine. Which they don't.

Another thing that I noticed, how come there are no variables for event.mass or event.radius in the Scanned body event? Would make sense to add those infos, wouldn't it?

Still loving everything about EDDI, don't get me wrong, I'm just an info addict who wants to make her work even more awesome :D
 
I am continuing to have great fun with EDDI and some limited integration with Voice Attack.

In recent days I have been sourcing and editing some film wav audio files to be triggered by EDDI events and played by VA, examples include the 'combat drop' music and speech from the film Aliens which is played each time I launch a fighter, the 'emergency destruct sequence is now activated' alarm and sounds again from the film Aliens, played whenever the ship self destruct is activated.

Various klaxons, sirens, red alert sounds for being interdicted, under attack etc.

In terms of 'actions' I have managed to integrate the landing gear up following lift off as this was a script shown on the EDDI site and was an easy key to map using VA.

I have also been editing the EDDI files for scans as suggestions have been flowing here. All great fun and adding a lot to the immersion.

EDIT: Also a Saitek X52PRO owner
 
Last edited:
YES PLEASE!!! I have an X52 as well, this would be perfect! Is it TTS or do you use voice packs? I just spent $40 on British Amy TTS so I'm hoping to use a profile that has TTS instead of voice packs.

I use MS Hazel and she sounds great and major bonus, is FREE!

Sure, I will package what I have into a zip to share. I will have to look up some of the original folks who I build this setup from for credit references, but all in all, for x52 pro users who have VA and EDDI, it works quite well! As for verbal dialog available, u can simply look at the VA voice activated section to see all the spoken commands... its pretty comprehensive.

will try to post this weekend!

o7
wind
 
I had a breakthrough on the atmosphere segment of the body scanned script. I came upon the idea of having EDDI read out what the variables event.atmosphere and event.pressure actually contained.

As I found out that way, event.pressure returns the surface pressure IN PASCAL or MILLIBAR. So in order to get the "number of atmospheres" as is written in the info panel ingame, I had to divide event.pressure by 101,325 as 101,325 mBar is considered one atmosphere (source: wikipedia).

However, the event.atmosphere variable turned out to be highly restrictive for use in EDDI scripts, as it doesn't just return what is written in the ingame info panel (which would be "Carbon Dioxide" for instance). Instead, it returns a string like "hot, thick carbon dioxide atmosphere", which already contains information about the density and temperature of the atmosphere, as well as the word "atmosphere" at the end of the string.

So I gave up on screwing around with event.pressure as it won't do any good of having that information repeated by that string, and finally came up with this piece of code:
{if event.pressure = 0:
{OneOf("There is no atmosphere.", "It is devoid of any atmosphere.", "The years have scoured it clean of any atmosphere.")}
|else:
{OneOf("{event.name} has a {event.atmosphere}.", "I detect a {event.atmosphere}", "There is a {event.atmosphere}")}.
}
This seems to work fine for most bodies, however, gas giants ingame have no information about their atmosphere, so EDDI interprets that as them not having one at all, which is ridiculous of course. I'll try to find a way around that over the weekend and also devote myself to the volcanism segment some more xD
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom