Release EDDI 3.3 - Bring your cockpit to life

nepomuk

nepomuk
Hello @Saltyseadog , I have always taken my/our character GerDA (German Data Assistant) with me from version to version. There were actually no problems with its use. The use of the SetState() variables (when reading from: state.xxx_yyyy to GetState('xxx_yyyy') ) had to be adjusted. As far as I know, that was all. Our GerDA uses parts translated into German from the original character, Darkcyde's character and scripts we created ourselves.

Greetings from nepomuk 🙋‍♂️

Translated with DeepL.com (free version)
 

Darkcyde

Darkcyde
Saltyseadog said:
Yes, that right.
Click to expand...
Hi Saltyseadog,

The version of my personality that I have on here at the moment, should be used with v4.0.4 (and before). I am working on a version that is more compatible with the new changes in v4.1.0, and I intend to release that shortly after v4.1.0 is fully released. EDDI v4.1.0 will be required for my new version to work properly, as it makes use of many of the new features that v4.1.0 will have.

Hope that helps! 😊

DC
 

pFVD

P
Just a quick post. You can use this NaturalVoicesSapiAdapter to get Microsoft's Natural/Azure voices that it uses for Windows 11 Narrator to EDDI's speech engine. Follow the installation instructions on the Github page, download the voices you want to use in Narrator (Win+Ctrl+N in Windows 11), and you should find them accessible in the EDDI config. I've not got the "online" voices working, but the others all seem to work fine (I've tested Sonia and Aria) and sound much better than the usual standard Windows TTS.

I don't know if this info has been posted before (I couldn't find it in a search) but just incase it hasn't, thought I'd post it now.
 
Last edited:

Darkcyde

Darkcyde
pFVD said:
Just a quick post. You can use this NaturalVoicesSapiAdapter to get Microsoft's Natural/Azure voices that it uses for Windows 11 Narrator to EDDI's speech engine. Follow the installation instructions on the Github page, download the voices you want to use in Narrator (Win+Ctrl+N in Windows 11), and you should find them accessible in the EDDI config. I've not got the "online" voices working, but the others all seem to work fine (I've tested Sonia and Aria) and sound much better than the usual standard Windows TTS.

I don't know if this info has been posted before (I couldn't find it in a search) but just incase it hasn't, thought I'd post it now.
Click to expand...
I've just given this a try, and I like it. I've downloaded all the English Narrator voices, and tested them in the Text-to-Speech tab. They all work OK. Some are a little faster than others, but I can live with that.

Now to go and see how EDDI uses them for NPC messages! 😁
 

T'kael

T'kael
pFVD said:
Just a quick post. You can use this NaturalVoicesSapiAdapter to get Microsoft's Natural/Azure voices that it uses for Windows 11 Narrator to EDDI's speech engine. Follow the installation instructions on the Github page, download the voices you want to use in Narrator (Win+Ctrl+N in Windows 11), and you should find them accessible in the EDDI config. I've not got the "online" voices working, but the others all seem to work fine (I've tested Sonia and Aria) and sound much better than the usual standard Windows TTS.

I don't know if this info has been posted before (I couldn't find it in a search) but just incase it hasn't, thought I'd post it now.
Click to expand...
I am not familiar with this program or its author. Feel free to use this if you wish but please understand that I have not evaluated this program and cannot endorse / vouch for it.
 

Joe Cool

Joe Cool
I'm an avid explorer and experiencing issues with EDDI 4.0.4 seemingly reporting bodies to scan incorrectly.
The problem is evident both with the provided default and my custom profiles. Reverting to 4.0.3 resolves the issue.

It'll take a bit of effort to detail the problem fully and accurately (hence no issue raised as yet) but generally it's things like reporting a body left to scan despite the system already being fully scanned at the initial honk.

I've seen no mention of this elsewhere so am a little paranoid that it's just me, hence the reach out. Anybody else?
 

nepomuk

nepomuk
Hi @Joe Cool , don't worry, you're not the only one. I've had that too. But I can't really help you either, as the scripts for the voice output in German have been changed. Maybe @Darkcyde or @T'kael can say something about it if they have time. My suggestion: If the script from version 4.0.3 announces everything correctly, then you can also use it for version 4.0.4 or try it out. You create a copy of the original character and copy the content of the 4.0.3 script into the script of your character_4.0.4 copy. Nothing can ‘break’ there.
Just give it a try. ;)

Translated with DeepL.com (free version)
 

T'kael

T'kael
Joe Cool said:
I'm an avid explorer and experiencing issues with EDDI 4.0.4 seemingly reporting bodies to scan incorrectly.
The problem is evident both with the provided default and my custom profiles. Reverting to 4.0.3 resolves the issue.

It'll take a bit of effort to detail the problem fully and accurately (hence no issue raised as yet) but generally it's things like reporting a body left to scan despite the system already being fully scanned at the initial honk.

I've seen no mention of this elsewhere so am a little paranoid that it's just me, hence the reach out. Anybody else?
Click to expand...
If this is occurring then I'll need some solid info to diagnose this (verbose log files from an instance where this occurred and perhaps a copy of your EDDI.sqlite file from %appdata%/EDDI).
 

Joe Cool

Joe Cool
T'kael said:
If this is occurring then I'll need some solid info to diagnose this (verbose log files from an instance where this occurred and perhaps a copy of your EDDI.sqlite file from %appdata%/EDDI).
Click to expand...
Thanks for the reply T'kael. As work is currently progressing on 4.1 (and I'm running 4.0.3 without issue) my inclination would be to wait on a 4.1 release and then test that.

That said I'm very happy to: -
1. Do my best to capture video evidence of my experience for evaluation by those wiser than me
2. If deemed worthy of investigation, provide diagnostic information as requested
 
Last edited:

nepomuk

nepomuk
Hello everyone (especially @T'kael and @Darkcyde ), I have noticed something that I was not aware of. I'm currently travelling in deep space and scanning the systems. When I come across systems with more than one sun, the first ‘HONK’ only announces the main star. If I carry out the ‘HONK’ a second time, I will also be notified of other suns if they are present. This is not due to EDDI. In my opinion, EDDI is doing everything right. After the HONK, there is the ‘FSSDiscoveryScan’ event in the journal and at the same time or shortly afterwards (at least it is entered in the list of the journal afterwards) there is the ‘Scan (detailed)’ event. EDDI reacts to the FSSDiscoveryScan but the other suns are only recognised with the ‘Scan (detailed)’. This means that EDDI can only recognise the other suns as undiscovered bodies, although the suns are discovered with the second event. EDDI therefore only makes a correct announcement after a second HONK. Can this be corrected via EDDI?
1726834400053.png


EDIT1:
Sorry, I must have made a mistake. I probably used the wrong variable (instead of {scannedbodies} - variable is calculated, the suns are subtracted, {system.scannedbodies} - system variable, which is fixed). I'll test it again, but I'm pretty sure that's the case.

EDIT2:
Ok, I tested it again yesterday. It's a bit confusing, but it's as I described at the beginning. Here's another example and what I observed.
1. Jump into an unexplored (for me) system. ED event “FSDJump” >> EDDI event “Jumped”. Then comes “Scan/Autoscan” - detection of the main star (and possibly very close objects) and the clusters.
2. Triggering the HONK. ED event “FSSDiscoveryScan” and detect the number of objects in the system (system.totalbodies). The second or third star is NOT detected here.
Then “Scan/Autoscan” OR “Scan/Detailed” appears immediately. Both variants have occurred. I do not know what this depends on. With “Scan/Autoscan” EDDI recognizes the second or third sun, with “Scan/Detailed” the second or third sun is not recognized by EDDI. However, the values are always present in the journal.
Result: After the HONK with automatic “Autoscan”, all suns are recognized. After a HONK followed by a “Scan/Detailed”, all suns are only recognized after a second HONK.
Then another note. The command {len(SystemDetails(system.systemname).bodies)} only recognizes all bodies if they have been scanned/explored (by myself).


Translated with DeepL.com (free version)
 
Last edited:

T'kael

T'kael
nepomuk said:
Hello everyone (especially @T'kael and @Darkcyde ), I have noticed something that I was not aware of. I'm currently travelling in deep space and scanning the systems. When I come across systems with more than one sun, the first ‘HONK’ only announces the main star. If I carry out the ‘HONK’ a second time, I will also be notified of other suns if they are present. This is not due to EDDI. In my opinion, EDDI is doing everything right. After the HONK, there is the ‘FSSDiscoveryScan’ event in the journal and at the same time or shortly afterwards (at least it is entered in the list of the journal afterwards) there is the ‘Scan (detailed)’ event. EDDI reacts to the FSSDiscoveryScan but the other suns are only recognised with the ‘Scan (detailed)’. This means that EDDI can only recognise the other suns as undiscovered bodies, although the suns are discovered with the second event. EDDI therefore only makes a correct announcement after a second HONK. Can this be corrected via EDDI?
View attachment 402000

EDIT1:
Sorry, I must have made a mistake. I probably used the wrong variable (instead of {scannedbodies} - variable is calculated, the suns are subtracted, {system.scannedbodies} - system variable, which is fixed). I'll test it again, but I'm pretty sure that's the case.

EDIT2:
Ok, I tested it again yesterday. It's a bit confusing, but it's as I described at the beginning. Here's another example and what I observed.
1. Jump into an unexplored (for me) system. ED event “FSDJump” >> EDDI event “Jumped”. Then comes “Scan/Autoscan” - detection of the main star (and possibly very close objects) and the clusters.
2. Triggering the HONK. ED event “FSSDiscoveryScan” and detect the number of objects in the system (system.totalbodies). The second or third star is NOT detected here.
Then “Scan/Autoscan” OR “Scan/Detailed” appears immediately. Both variants have occurred. I do not know what this depends on. With “Scan/Autoscan” EDDI recognizes the second or third sun, with “Scan/Detailed” the second or third sun is not recognized by EDDI. However, the values are always present in the journal.
Result: After the HONK with automatic “Autoscan”, all suns are recognized. After a HONK followed by a “Scan/Detailed”, all suns are only recognized after a second HONK.
Then another note. The command {len(SystemDetails(system.systemname).bodies)} only recognizes all bodies if they have been scanned/explored (by myself).


Translated with DeepL.com (free version)
Click to expand...
Yes, the journal sequencing for FSSDiscoveryScan and SystemScanComplete can be a little odd.

EDDI currently polls the journal every tenth of a second and is designed to handle multiple events found at the same time as a group. Within that group, EDDI is actually designed to re-order events so that FSSDiscoveryScan (the DiscoveryScanEvent) is handled last and any Scan events from that group are handled first.
github.com

EDDI/JournalMonitor/JournalMonitor.cs at ad524656bcc39c306cf74d41077b1d355bdf8e93 · EDCD/EDDI

Companion application for Elite Dangerous. Contribute to EDCD/EDDI development by creating an account on GitHub.
github.com github.com

If EDDI isn't reorganizing the events then that might suggest that the events are being written more than a tenth of a second apart.

If that is the case then I may need to change the strategy for handling these events.
 
Last edited:

nepomuk

nepomuk
Wow, that's very interesting. Many thanks for the information. (y):)
Unfortunately, the entries in the journal are only written by the second.
The FSSDiscoveryScan and the subsequent scan events Auto and Detailed are entered in the journal at the same second.
This is not vital now. I just noticed it and couldn't explain it. ;)🍻
 
You must log in or register to reply here.
Back
Top Bottom