Release EDDI 3.3 - Bring your cockpit to life

T'kael

T'kael
nepomuk said:
Hi @T'kael , I've been looking around a bit on the EDDI page on github. Are you the only one still working/developing with EDDI?
I didn't find @Darkcyde and @VerticalBlank there and Hoodathunk is unfortunately no longer with us.
What I would like to say is, if you need help or simple work, please let me know. If I can help, I would be happy to do so.
Unfortunately I am not a programmer and have no idea about C#.

Greetings nepomuk
Click to expand...
I didn't either before I joined the team with VerticalBlank and Hoodathunk. If you are interested then you are welcome to give it a try. 😃 It turns out that there are a lot of resources out there for budding programmers.
 

Parduz

Parduz
nepomuk said:
That's more or less what I thought. Although there are quite a few people on the EDDI github site, @T'kael is the only one who is pushing EDDI forward.
Hmm, @T'kael would have to say how we "one-armed people" :ROFLMAO: could help him. I think colleague @Parduz would not be averse either, if his time permits.
Click to expand...
eheh :)
While i'm a C/C++ and VB(A) programmer, and i think that learning (basic) C# should not be too hard (i mean: EDDI is well developed, it is not something to be invented from scratch) there's one thing that keep me .... far ... from making "official" code, and that thing is that i'm (mostly) self-taught.
(Modern) programming requires some .... style? some "methods" and a bunch of knowhow that i lack totally. I'm good at problem solving, i can build an UI (that's half of my job, the other half is making microprocessor firmwares) but i'm pretty sure that half of the code i could write for EDDI will need to be revised.

Anyway i'd be happy to help for a specific task, if asked for.
 

nepomuk

nepomuk
Hello @VerticalBlank (and @T'kael), ohhh I apologise so much. Yes, I know you are here and also on the translation site "crowdin.com".
But I missed you on the github page. Maybe you use a different pseudonym there. My English is not good (it's even quite bad), so I often use deepL.
And maybe that's why I misunderstood the connection to HoodaThunk. Sorry !

And thanks for the Discord link. (y)
Unfortunately, I'm not a programmer and can therefore contribute little or nothing to the code. But I feel the same way as @Parduz.
If there is work that is easy but time-consuming for you, then maybe I could help (maybe type something, search, replace or similar ...)
 

Parduz

Parduz
I'd have another feature request: 😬
a way to use a specific voice for the entire script.
Maybe something like a function SetVoice(voice).

The purpose is to allow non-english speakers to set an english voice at the top of untranslated scripts, or -as example- in the Message received event, where the NPC messages are all in English.
Right now it will require to add a Voice() at each spoken line, which is almost not feasible.
 

nepomuk

nepomuk
Hello everyone, I need your help. One function of EDDI and Voice Attack does not work for me. What am I doing wrong? :unsure:
I want to transfer a variable created in VA to EDDI. My settings in VA:

My call in EDDI:

It always outputs "void".

EDIT: Ok, found my mistake myself. ;)
 
Last edited:

nepomuk

nepomuk
Hello together (once again) ;) ...
... and again a question (about Cottle), I want to create a list in one script and have this list announced in another script. I can not get this to work.
Example:
Script 1 (collection): {set testlist to []} {set testlist to cat(testlist, [testlist-next])} Script 2 (output): {List(testlist)}

I think it must be assembled with SetState(), but I didn't get the syntax right. And I didn't find any help at the Cottle online help, unfortunately.
Maybe one of the specialists can help me. (@T'kael , @Darkcyde ... :) )

Thanks a lot !
 

Darkcyde

Darkcyde
nepomuk said:
Hello together (once again) ;) ...
... and again a question (about Cottle), I want to create a list in one script and have this list announced in another script. I can not get this to work.
Example:
Script 1 (collection): {set testlist to []} {set testlist to cat(testlist, [testlist-next])} Script 2 (output): {List(testlist)}

I think it must be assembled with SetState(), but I didn't get the syntax right. And I didn't find any help at the Cottle online help, unfortunately.
Maybe one of the specialists can help me. (@T'kael , @Darkcyde ... :) )

Thanks a lot !
Click to expand...
Yes you will need to make it a State variable, but you will also need to make it one string. SetState can't handle arrays (yet) so you need to join the list items together first with Join(), and then in the second script Split() it back up again.

So something like this:
Code: 
{set testlist to join(testlist, "_")}
{SetState("test_list", testlist)}
You could also try to shorten it to {SetState("test_list", join(testlist, "_"))}

Then:
Code: 
{set testlist to split(state.test_list, "_")}

This should do what you need I think. :)

EDIT: Note the separator "_". If this underscore character will be in your list data, then just choose a different character, or even a short string like "+-". ;)
 
Last edited:

T'kael

T'kael
For those who haven't yet seen the announcement: https://forums.frontier.co.uk/threads/update-14-and-beyond-live-and-legacy-modes.610714/
@VerticalBlank and I are still thinking about how we can support this change, but EDDI will in all likelihood not have support for live/legacy at the release of update 14. I recommend sticking to just one game mode (either live or legacy) rather than swapping between the two to prevent EDDI from incorrectly capturing / using data from the other game mode. o7
 

Parduz

Parduz
If i'm not getting it wrong, the problem is that all the 3rd party sites collecting galaxy data will have either to double the database or pick one mode (or give up entirely, which is what i fear mostly). So EDDI is .... "tied" to the decisions they will take, right?

I mean: per se the Voice Assistant will still work as before, the problem will be from "what universe" there will be picked the additional infos about the star system, etc etc.
Or am i missing something?
 

T'kael

T'kael
Parduz said:
If i'm not getting it wrong, the problem is that all the 3rd party sites collecting galaxy data will have either to double the database or pick one mode (or give up entirely, which is what i fear mostly). So EDDI is .... "tied" to the decisions they will take, right?

I mean: per se the Voice Assistant will still work as before, the problem will be from "what universe" there will be picked the additional infos about the star system, etc etc.
Or am i missing something?
Click to expand...
Essentially. 3rd party sites will want to support the "live" galaxy so data that EDDI receives from 3rd party APIs (particularly things like BGS data, faction state data, etc.) will very likely only match that mode. Likewise, EDDI will probably need to be updated to provide the details needed to allow 3rd party sites to segregate data from "live" and "legacy" galaxies. We do not yet know how the changes will affect the data from the Frontier API either. And finally, any configuration data we save from one galaxy (e.g. missions, cargo, your shipyard, etc.) won't necessarily be valid in the other because player progress will not be synchronized between galaxies either.
 
Last edited:

nepomuk

nepomuk
Darkcyde said:
Yes you will need to make it a State variable, but you will also need to make it one string. SetState can't handle arrays (yet) so you need to join the list items together first with Join(), and then in the second script Split() it back up again.

So something like this:
Code: 
{set testlist to join(testlist, "_")}
{SetState("test_list", testlist)}
You could also try to shorten it to {SetState("test_list", join(testlist, "_"))}

Then:
Code: 
{set testlist to split(state.test_list, "_")}

This should do what you need I think. :)

EDIT: Note the separator "_". If this underscore character will be in your list data, then just choose a different character, or even a short string like "+-". ;)
Click to expand...
Phew, not as easy as I thought :oops: ... Thank you (y) , I will try it (maybe tonight).
 

Darkcyde

Darkcyde
nepomuk said:
Phew, not as easy as I thought :oops: ... Thank you (y) , I will try it (maybe tonight).
Click to expand...
Hehe! It's not too bad. 😊 You just need the first one at the end of your first script, and the second one at the start of your second script. After that, your scripts should be just as you probably already have them.

If you have lots of lists to share between scripts, then there will need to be one set of these commands for each list, things may get a little complicated then, but not by much. That's what I had to do when I made my first 'databases' for cargo and missions back in 2017, before EDDI did them natively. 😆
 

Parduz

Parduz
T'kael said:
🎺🎊🎺 I am pleased to announce that EDDI version 4.0.2-b1 is now available. The change log is available here and the update is available from inside the application or from the installer here.
Click to expand...
banana.gif


(now i can write new posts without making @Amodin angry :D :p )
 
You must log in or register to reply here.
Back
Top Bottom