Release EDDI - Windows app for immersion and more

Status
Thread Closed: Not open for further replies.
@J. Calvert (Joshua) This works for me:
state variable.jpg
Note that I am using "State Variable" (capitalized V) and that I'm calling the variable from VoiceAttack using {TXT:EDDI state jumpingdetails}
 
Last edited:
I added the line to the script but it only says "Jump details are" and then nothing else until the regular start (Destination confirmed...).

Here are my files:

https://www.dropbox.com/s/lafl1j0o1ixpfsc/eddi.log.txt?dl=0
https://www.dropbox.com/s/sadjfsb6bfo2bvi/eddi 2.3 b2.json?dl=0
https://www.dropbox.com/s/lipol49ccpjgtvu/000 Multi-Crew JP 2.2b-Profile.vap?dl=0

Right, I've taken a look at this and there is something strange going on with VoiceAttack. As far as I can tell there is an item in the speech queue that is hanging VoiceAttack, because when I run the "Eddi speak up" command it doesn't even say the first line. As a workaround I changed the VoiceAttack say options for this first command in "Eddi speak up" so that "This completes all currently-playing text-to-speech" is checked and it now behaves.

You also need to change your "Emma status" command so that it sets "State variable" to "jumpingdetails" before invoking EDDI's setstate.

This said, you should try to track down whatever it is that is hanging VoiceAttack in the first place, as you're going to have similar issues with other commands not working and/or causing high CPU until this is fixed.

UPDATE:

Sorry forgot the main thing that was wrong. If you look at this command:

GYLdnPt.jpg

you'll see that you are setting State variable to the value of the variable 'jumpingdetails' not the text value 'jumpingdetails', which means that the command won't work.
 
Last edited:
@J. Calvert (Joshua) This works for me:
Note that I am using "State Variable" (capitalized V) and that I'm calling the variable from VoiceAttack using {TXT:EDDI state jumpingdetails}

Thanks for looking into it. I've changed it in "State Variable" but still no luck. The callback with {TXT:EDDI state jumpingdetails} in the VA log gives "Not Set" so that explains why it's not working (because it isn't "full") but not why it's not set to full.
 
Right, I've taken a look at this and there is something strange going on with VoiceAttack. As far as I can tell there is an item in the speech queue that is hanging VoiceAttack, because when I run the "Eddi speak up" command it doesn't even say the first line. As a workaround I changed the VoiceAttack say options for this first command in "Eddi speak up" so that "This completes all currently-playing text-to-speech" is checked and it now behaves.

You also need to change your "Emma status" command so that it sets "State variable" to "jumpingdetails" before invoking EDDI's setstate.

This said, you should try to track down whatever it is that is hanging VoiceAttack in the first place, as you're going to have similar issues with other commands not working and/or causing high CPU until this is fixed.

That's strange because i've never had problems with that but I'll look into it.

UPDATE:

Sorry forgot the main thing that was wrong. If you look at this command:


you'll see that you are setting State variable to the value of the variable 'jumpingdetails' not the text value 'jumpingdetails', which means that the command won't work.

I must have misunderstood your answer in post #1889 than because I had it like that before but changed it after you're reply. Now I've changed it back to the text value instead of the variable and EUREKA it's working now !!
Not sure if that was the solution or a combination of this and TKael's remark about the capital V in State Variable but who cares [haha]

Thanks all !!
 
I'm still getting NOT SET back instead of .. whatever it is I'm asking for ? ie System report saya ZERO no-one around ..lol

Others are reporting VA, if using it, NOT SET been reported back too
http://voiceattack.com/smf/index.php?topic=1097.0


Does anyone know what's up , it's who EDDI HSC Frontier ?

I'm not sure where you are getting 'NOT SET' but if it's in the VoiceAttack window then it's nothing to do with EDDI, as EDDI doesn't write log information to the VoiceAttack window.
 
In VA:
Code:
Set small int (condition) [n_VA_landing_pad] value to the value of [{INT:EDDI docking granted landingpad}]
Write '[Blue] n_VA_landing_pad = {INT:n_VA_landing_pad}' to log
Write '[Blue] EDDI docking granted landingpad = {INT:EDDI docking granted landingpad}' to log
Execute command, '((EVAEDDI: Andocken gewährt))' (and wait until it completes)

Output in Log:
EDDI docking granted landingpad = 16
n_VA_landing_pad = Not set

Is this an error on my side?

Edit:
Changed it to:
Code:
Set small int (condition) [n_VA_landing_pad] value to 0
Set small int (condition) [n_VA_landing_pad] value to the value of [{INT:EDDI docking granted landingpad}]
Write '[Blue] n_VA_landing_pad = {INT:n_VA_landing_pad}' to log
Write '[Blue] EDDI docking granted landingpad = {INT:EDDI docking granted landingpad}' to log
Execute command, '((EVAEDDI: Andocken gewährt))' (and wait until it completes)

Exptected to get
n_VA_landing_pad = 0
but still
n_VA_landing_pad = Not set

=> my script mus be ok.
 
Last edited:
In VA:
Code:
Set small int (condition) [n_VA_landing_pad] value to the value of [{INT:EDDI docking granted landingpad}]
Write '[Blue] n_VA_landing_pad = {INT:n_VA_landing_pad}' to log
Write '[Blue] EDDI docking granted landingpad = {INT:EDDI docking granted landingpad}' to log
Execute command, '((EVAEDDI: Andocken gewährt))' (and wait until it completes)

Output in Log:
EDDI docking granted landingpad = 16
n_VA_landing_pad = Not set

Is this an error on my side?

Edit:
Changed it to:
Code:
Set small int (condition) [n_VA_landing_pad] value to 0
Set small int (condition) [n_VA_landing_pad] value to the value of [{INT:EDDI docking granted landingpad}]
Write '[Blue] n_VA_landing_pad = {INT:n_VA_landing_pad}' to log
Write '[Blue] EDDI docking granted landingpad = {INT:EDDI docking granted landingpad}' to log
Execute command, '((EVAEDDI: Andocken gewährt))' (and wait until it completes)

Exptected to get
n_VA_landing_pad = 0
but still
n_VA_landing_pad = Not set

=> my script mus be ok.

You're mixing 'int' and 'small int'. I'd stick to 'int' everywhere.
 
You're mixing 'int' and 'small int'. I'd stick to 'int' everywhere.

THX a lot.
Code:
Set integer [n_VA_landing_pad] value to the converted value of {INT:EDDI docking granted landingpad}
Execute command, '((EVAEDDI: Andocken gewährt))' (and wait until it completes)
This did the trick
 
If you use the two, just remember that small INT is specifically for conditions that have several values, unlike the Boolean that is true or false. Normal INTs are for actual data values. Just use the right one for the right job, or stick with just INT for everything.
 
jgm, am i correct that 'message received / sent' don't fire?

edit: i should stop drinking. working as intended. reset to default seemed to do the trick, even if i couldn't see any changes upfront.
thx for the reply, jgm.
o7
 
Last edited:
I tried writing a program that would watch the journal directory and when a file was changed it would read it, extract the last line, search the line for a certain text "Message_Localised" and if found it would parse out everything but the message and read it in TTS. Worked when I manually edited the file offline, but didn't work when the game wrote to it. Still trying to figure out why. Even put in error checking but no go.
 
VA EDDI when reading Galnet News playback was slightly distorted from previous clear playbacks

With the issues I'm having ( like the NOT SET ) a Clean install of EDDI VA HSC , seems like a good idea ( maybe)

So what has to be deleted with EDDI, to enure a clean install , and do I need to save any critical data ?
 
Last edited:
'Jumped' - call system security report here rather than in 'Jumping' to guarantee up-to-date information

Had to figure out why "Jumping" wasn't working (it has NO LONGER IN USE as the description) but "Jumped" has no scripting entered, copy/pasted one to the other then modify it a bit to work in the past tense after arriving instead of during transit..
 
Had to figure out why "Jumping" wasn't working (it has NO LONGER IN USE as the description) but "Jumped" has no scripting entered, copy/pasted one to the other then modify it a bit to work in the past tense after arriving instead of during transit..

'"Jumping" has been replaced by "FSD engaged", so most of what used to happen in Jumping is now in FSD engaged. The default Jumped template just provides the system state.
 

The only problem there that I see that appears to be related to EDDI is that the cargo carried is 0. This is a known issue, due to FD removing (hopefully temporarily) the cargo information from the companion API. Feel free to add your voice to those who would like this data back at https://forums.frontier.co.uk/showthread.php/342408-Companion-API-stopped-having-Engineering-Data

If there are other specific issues please could you state exactly which command you are running, and exactly what you hear as a result and see in VoiceAttack's log window. Thank you.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom