Release EDDI - Windows app for immersion and more

BumbleB · Aug 27, 2017

Anybody know if the EDDI Died Event has been implemented though Voice attack?

I'm trying to make a script in voice attack to write a log file to keep a log of who has killed me and where. So I can hunt them and kill them (just kidding, or am i?) on the Wiki for EDDI there are no variables for voice attack and I made an educated guess on what it could be but no joy.

Taken from the wiki....

commanders The names of the commanders who killed you

ships The ships the commanders who killed you were flying

ratings The ratings of the commanders who killed you

My guess for VA was TXT: EDDI died commanders, TXT: EDDI died ships, TXT: EDDI died ratings but got nothing back.

Can anybody help?

RomulusDK · Aug 27, 2017

BumbleB said:
Anybody know if the EDDI Died Event has been implemented though Voice attack?

I'm trying to make a script in voice attack to write a log file to keep a log of who has killed me and where. So I can hunt them and kill them (just kidding, or am i?) on the Wiki for EDDI there are no variables for voice attack and I made an educated guess on what it could be but no joy.

Taken from the wiki....

My guess for VA was TXT: EDDI died commanders, TXT: EDDI died ships, TXT: EDDI died ratings but got nothing back.

Can anybody help?

((EDDI died))
Set Text [Script] to 'died'
Execute external plugin, 'EDDI 2.3.0' (don't select speech in plugin context, unless you want the information in text to speech)
Append, '{TXT:EDDI died commanders} {TXT:EDDI died ships}' to file 'killed.txt' (killed.txt is an example of course)

Should work, no?

BumbleB · Aug 27, 2017

RomulusDK said:
((EDDI died))
Set Text [Script] to 'died'
Execute external plugin, 'EDDI 2.3.0' (don't select speech in plugin context, unless you want the information in text to speech)
Append, '{TXT:EDDI died commanders} {TXT:EDDI died ships}' to file 'killed.txt' (killed.txt is an example of course)

Should work, no?

Don't think anything is passed though. I had VA to log the died variables I guessed at but nothing came up in VA's log. Just got NOT SET in the .txt file where the {TXT:EDDI died commanders} {TXT:EDDI died ships} Do note those variables are guesses as there is not actually documentation for it in the wiki

Your way is a little different to the way i did it, Ill try your way to see if there is any difference

RomulusDK · Aug 27, 2017

RomulusDK said:
((EDDI died))
Set Text [Script] to 'died'
Execute external plugin, 'EDDI 2.3.0' (don't select speech in plugin context, unless you want the information in text to speech)
Append, '{TXT:EDDI died commanders} {TXT:EDDI died ships}' to file 'killed.txt' (killed.txt is an example of course)

Should work, no?

BumbleB said:
Don't think anything is passed though. I had VA to log the died variables I guessed at but nothing came up in VA's log. Just got NOT SET in the .txt file where the {TXT:EDDI died commanders} {TXT:EDDI died ships} Do note those variables are guesses as there is not actually documentation for it in the wiki

Your way is a little different to the way i did it, Ill try your way to see if there is any difference

Ah, I didn't check the WIKI and you are right, it seems that those variables are not set by EDDI - I didn't try out the script myself...

sutex · Aug 27, 2017

Any news of EDDI been updated ?

Tkael · Aug 28, 2017

BumbleB said:
Anybody know if the EDDI Died Event has been implemented though Voice attack?

I'm trying to make a script in voice attack to write a log file to keep a log of who has killed me and where. So I can hunt them and kill them (just kidding, or am i?) on the Wiki for EDDI there are no variables for voice attack and I made an educated guess on what it could be but no joy.

Taken from the wiki....

My guess for VA was TXT: EDDI died commanders, TXT: EDDI died ships, TXT: EDDI died ratings but got nothing back.

Can anybody help?

At current, array variables are not passed to VoiceAttack. Here are some comments from JGM on the subject: https://forums.frontier.co.uk/showt...ion-and-more?p=4684863&viewfull=1#post4684863
A workaround would be to set up a 'Died' cottle script that indexes the values into a delimited list then use the SetState function to pass that delimited list to VoiceAttack.

Hoodathunk · Aug 28, 2017

Tkael said:
At current, array variables are not passed to VoiceAttack. Here are some comments from JGM on the subject: https://forums.frontier.co.uk/showt...ion-and-more?p=4684863&viewfull=1#post4684863
A workaround would be to set up a 'Died' cottle script that indexes the values into a delimited list then use the SetState function to pass that delimited list to VoiceAttack.

Agreed.

BumbleB, take a look at Darkcyde's scripts and VA support commands for Fine & Bounties, Cargo Log, and Missions... Plenty of examples there for a methodology to implement an EDDI/VA combo to achieve your goal.

BumbleB · Aug 28, 2017

Hoodathunk said:
Agreed.

BumbleB, take a look at Darkcyde's scripts and VA support commands for Fine & Bounties, Cargo Log, and Missions... Plenty of examples there for a methodology to implement an EDDI/VA combo to achieve your goal.

oh man i was afraid of this, I've been looking though Darkcyde's scripting for a awhile trying to get my head around what happening but its way over my head. I've only just about got a handle on VA scripting and thats about it, mostly trail and error scripting, pretty messy but works after many hrs and late nights.

I've got quiet alot of scripting in VA for my streaming overlay and may take me quiet sometime to incorporate Darkcyde's scripts & VA into my own if i go that route....

Romeo Alpha · Aug 28, 2017

Just started using this today. I have most of it working but I cannot get the "shut up" or "that's enough" voice attack command to work. Any help?

.....aaaaaaaand, disregard. As soon as I asked for help it started working.

BumbleB · Aug 28, 2017

Romeo Alpha said:
Just started using this today. I have most of it working but I cannot get the "shut up" or "that's enough" voice attack command to work. Any help?

.....aaaaaaaand, disregard. As soon as I asked for help it started working.

That always happens to me, have a problem and as soon as I posted about it I solved it on my own

classic

VerticalBlank · Aug 29, 2017

Just a PSA to any EDDI users trading in rare goods: EDDI triggers a bug in Frontier's Companion API which causes the prices of rare goods to be reset to minimum values.

More details here:
https://github.com/Marginal/EDMarketConnector/issues/92
https://forums.frontier.co.uk/showthread.php?t=175338

TL;DR If you are running EDDI then the game will give you incorrect and very low prices for rare goods. To clear this up, log out of the game, quit EDDI, log back in and make a hyperspace jump.

The developers of EDMC and EDDiscovery have worked around this by suspending calls to the Companion API while you are carrying rare goods. EDDI will have to do similarly I suppose.

Nidhöggr · Aug 30, 2017

right now i would use eddi only for voice related events. remove the updates to eddn/eddb/edsm in eddi and use edmc for it. edmc is the thing for it.

an idea for future development (if forked or not): reduce eddi to immersion releated features and use edmc for everything else. this would remove some unneeded development time from one project.

there are so many cooks in so many kitchens, and everyone works - in parts - on the same menu, for one person.

VerticalBlank · Aug 30, 2017

There is a lot of overlap to be sure. But I quite like how EDDI will comment out loud on how market conditions relate to my current cargo.

robbyp · Sep 2, 2017

There is a lot of overlap. But saying some tool should not address everything is not a good idea. It's up to the Dev community to decide what to address. We at EDDiscovery wish you all well and hope that things work out

Nidhöggr · Sep 2, 2017

robbyp said:
There is a lot of overlap. But saying some tool should not address everything is not a good idea. It's up to the Dev community to decide what to address. We at EDDiscovery wish you all well and hope that things work out

mm addressing issues is one thing, doing the same thing on multiple edges and losing precious ressources, time and money is another thing, from a buisness standpoint.
greetings
-pm ;-)

Hoodathunk · Sep 3, 2017

Greetings EDDI Users Community!

T'kael, Vertical Blank, Darkcyde & I would like to announce that we are undertaking the challenging task of maintaining EDDI.

Our orders of priority are:
1. Add new Journal & API functionality in 2.4
2. Squash bugs still present from 2.3 and before.
3. Improve Ship & Cargo Monitor functionality, which involves adding Journal events not previously implemented.
4. Incorporating Darkcyde's Mission script functionality into a new 'Missions Monitor'.

It's been a steep learning curve and bit of a slog familiarizing ourselves with a mature, existing code base, but we're building up a good head of steam and starting to make good progress. At present, chances are fairly low that we will have a 2.4 beta ready for public consumption before the live release, but we will endeavor to keep that delay to a reasonable minimum.

For those interested in 'tracking' our progress, you can go to the EDCD EDDI GitHub issues page:

https://github.com/EDCD/EDDI/issues

Cheers!

BumbleB · Sep 3, 2017

Hoodathunk said:
Greetings EDDI Users Community!

T'kael, Vertical Blank, Darkcyde & I would like to announce that we are undertaking the challenging task of maintaining EDDI.

Our orders of priority are:
1. Add new Journal & API functionality in 2.4
2. Squash bugs still present from 2.3 and before.
3. Improve Ship & Cargo Monitor functionality, which involves adding Journal events not previously implemented.
4. Incorporating Darkcyde's Mission script functionality into a new 'Missions Monitor'.

It's been a steep learning curve and bit of a slog familiarizing ourselves with a mature, existing code base, but we're building up a good head of steam and starting to make good progress. At present, chances are fairly low that we will have a 2.4 beta ready for public consumption before the live release, but we will endeavor to keep that delay to a reasonable minimum.

For those interested in 'tracking' our progress, you can go to the EDCD EDDI GitHub issues page:

https://github.com/EDCD/EDDI/issues

Cheers!

I thank you a head of time for you and the efforts of the new EDDI developer team undertaking this huge project. I have been silently monitoring the teams progress on github and i'm liking what I'm seeing.

If I can help in anyway, give me a shout, I'm always good at breaking things and doing weird things that normal humans don't even think of

Bee safe, if not bee bad ö7

Nidhöggr · Sep 3, 2017

Hoodathunk said:
T'kael, Vertical Blank, Darkcyde & I would like to announce that we are undertaking the challenging task of maintaining EDDI.

may the code be with you.
good luck and have fun

Tkael · Sep 4, 2017

Nidhöggr said:
may the code be with you.
good luck and have fun

We've been making some good progress with both implementing a number of new events and fixing some bugs in the current build but we're still pretty new to this. Thankfully, JGM gave us a very solid foundation. If you're interested in contributing to the project, just follow the Github link or contact us on the EDCD (Elite Dangerous Community Developers) discord.

If you're interested in seeing what we've done so far: https://github.com/EDCD/EDDI/issues?q=is:issue+is:closed

Brigetiol1 · Sep 4, 2017

Hoodathunk said:
Greetings EDDI Users Community!

T'kael, Vertical Blank, Darkcyde & I would like to announce that we are undertaking the challenging task of maintaining EDDI.

Our orders of priority are:
1. Add new Journal & API functionality in 2.4
2. Squash bugs still present from 2.3 and before.
3. Improve Ship & Cargo Monitor functionality, which involves adding Journal events not previously implemented.
4. Incorporating Darkcyde's Mission script functionality into a new 'Missions Monitor'.

It's been a steep learning curve and bit of a slog familiarizing ourselves with a mature, existing code base, but we're building up a good head of steam and starting to make good progress. At present, chances are fairly low that we will have a 2.4 beta ready for public consumption before the live release, but we will endeavor to keep that delay to a reasonable minimum.

For those interested in 'tracking' our progress, you can go to the EDCD EDDI GitHub issues page:

https://github.com/EDCD/EDDI/issues

Cheers!

Hi A-Team

,

Thank you for taking care of EDDI! If you remember the TV series: four very different personalities were working together for good reasons, with tricky plans...

Best regards!