EDDI: A(nother) Voice Attack Plugin

Status
Thread Closed: Not open for further replies.

jgm

jgm
foxpur said:
Well, (*prepares to run and hide*), I removed the old install and put the new beta in, and filling out the configuration.exe.... and wouldn't you know it.... "Unfortunately we were unable to locate your product directory." is still there ..
Click to expand...

A couple of things. First, you don't need to remove the %APPDATA%\EDDI directory when you upgrade. Did you do this? If not, then the old settings should still be in place, so if they vanished that is strange.

Can I just confirm exactly what you did with attempting to find the log location? The process I would expect would be:

  • Start up configuration.exe
  • Start up Elite: Dangerous (not just the launcher, the full game)
  • Hit 'Obtain' on the Netlog tab
 

foxpur

foxpur
jgm said:
A couple of things. First, you don't need to remove the %APPDATA%\EDDI directory when you upgrade. Did you do this? If not, then the old settings should still be in place, so if they vanished that is strange.

Can I just confirm exactly what you did with attempting to find the log location? The process I would expect would be:

  • Start up configuration.exe
  • Start up Elite: Dangerous (not just the launcher, the full game)
  • Hit 'Obtain' on the Netlog tab
Click to expand...

Nope...
Started Config,
Hit Obtain...

I have Not started Elite because Elite isn't required to get EDSM logs (usually...)
NOTE: it just swtched to "Obtaining Log", 9.25 mins
I will see if I can log in with this machine... (The one I am going my VA work today isn't the one I usually use to game one)

EDIT: Log obtained, 11min

So everything pass the Configuartion.exe except telling me my log files aren't there (and really... they ARE there... honest)
 
Last edited:

jgm

jgm
foxpur said:
I have Not started Elite because Elite isn't required to get EDSM logs (usually...)
Click to expand...

It does say in the NetLog tab that you need to start Elite: Dangerous before you hit the Obtain button.

The reason for this is that the logs could be pretty much anywhere on the filesystem, and although there are a few "standard" locations none of them are guaranteed, and depend on how (steam or direct) and when (pre-Horizons or Horizons) you installed the product, as well as if you are running season 1 or 2. The only way to know for sure where the product logs are is to pull them from the running process. You are of course, able to type the directory in yourself if you are sure of where they are but there's no way for the configuration system to confirm that it's the right directory without you forcing a system change entry in them.

Note that this isn't anything to do with the EDSM functionality, it's just finding the logs directory location.

Regarding the time taken to pull the exploration logs: it's pulling additional system data for each of the systems you have in the your EDSM list. Given the large amount of time this is taking I'll tweak it so that it won't pull the additional system data on sync and instead fetch it when you next visit the system. Thanks for the feedback on this.
 

foxpur

foxpur
jgm said:
Regarding the time taken to pull the exploration logs: it's pulling additional system data for each of the systems you have in the your EDSM list. Given the large amount of time this is taking I'll tweak it so that it won't pull the additional system data on sync and instead fetch it when you next visit the system. Thanks for the feedback on this.
Click to expand...

Just doing beta reporting :)
And started VA and it didn't crash and no smoke.
 

foxpur

foxpur
Potential bug:

12:11:56 - Unable to get value from URI - Unable to connect to the remote server
12:11:54 - Recognized : 'tell me about this system'

Everything else so far seems to work, details from the API provide this data I assume.
 

bAdbUd

bAdbUd
foxpur said:
Potential bug:

12:11:56 - Unable to get value from URI - Unable to connect to the remote server
12:11:54 - Recognized : 'tell me about this system'

Everything else so far seems to work, details from the API provide this data I assume.
Click to expand...

I'm using the BETA version and I don't have this problem when saying that command.

It's cool now it's connecting to EDSM and the extra configuration for Voices to use.7
 

bAdbUd

bAdbUd
I haven't seen anyone post lately about lag. This has continued to happen since many versions ago.

So I ask, is it just me experiencing lag?
 

bAdbUd

bAdbUd
foxpur said:
It likes you :)
I am getting a small bit of lag, but seems inconsistent.
Click to expand...

Yes it is inconsistent, but when it happens VA is next to useless and has to be quit and restarted. Although sometimes if I tolerate the lag it seems to resolve itself after a short period of time. Also sometimes there's no lag at all, or a variety of lag issues. Occasionally VA crashes altogether.

However it's not all bad news as it works more often than it doesn't
 

jgm

jgm
bAdbUd said:
Yes it is inconsistent, but when it happens VA is next to useless and has to be quit and restarted. Although sometimes if I tolerate the lag it seems to resolve itself after a short period of time. Also sometimes there's no lag at all, or a variety of lag issues. Occasionally VA crashes altogether.

However it's not all bad news as it works more often than it doesn't
Click to expand...

Unfortunately the lag is down to VoiceAttack rather than EDDI. I recreated the lag by creating a bunch of random commands on a fresh VoiceAttack install without EDDI present and running it at the same time as Elite.
 

sutex

sutex
The startup script, appears before the plugins are loaded message, in VA, Does this matter ? It loads first very fast.
 

jgm

jgm
sutex said:
The startup script, appears before the plugins are loaded message, in VA, Does this matter ? It loads first very fast.
Click to expand...

No this doesn't matter. The plugin initialisation is asynchronous, but the startup script takes this in to account and doesn't expect the plugin to be initialised. It just sits in the event loop and waits for something to happen.
 

Straha Yeagar

S
I have been loving this plugin and working with it alongside KICS 4. I have been making my own simulated banter with star bases and stations, and would absolutely love to be able to set different TTS voices on a command by command basis, and even better would be to be able to randomize the voice of various responses...if that makes any sense?
 

jgm

jgm
straha20 said:
I have been loving this plugin and working with it alongside KICS 4. I have been making my own simulated banter with star bases and stations, and would absolutely love to be able to set different TTS voices on a command by command basis, and even better would be to be able to randomize the voice of various responses...if that makes any sense?
Click to expand...

It should be possible to do this but would require some customisation elements, namely a list of voices that the user would want to allow EDDI to use for the "random voice" allocations. I'll see what I can do for the 1.2 release.
 

Straha Yeagar

S
jgm said:
It should be possible to do this but would require some customisation elements, namely a list of voices that the user would want to allow EDDI to use for the "random voice" allocations. I'll see what I can do for the 1.2 release.
Click to expand...

Thanks for even entertaining this idea. I am not a developer, but thinking about what you already have in place, perhaps being able to set a name variable for the individual voices in the configuration sort of like the ship name, and then invoke the with the say command...so like this...

say - would use the default voice
say [voice1] - named voice 1
say [voice2] - named voice 2
say [voice1,voice2] - random between voice1 and voice2
etc...

I know probably easier said than done :)
 

jgm

jgm
sutex said:
- - - - - Additional Content Posted / Auto Merge - - - - -

TOOLS I use for ED are
ED-IBE
https://github.com/Duke-Jones/ED-IBE/releases
and ED Toobox
http://edtb.xyz/?q=download

Would like too see EDDI to be able to communicate with these tools
Click to expand...

What sort of communication would you want, and what would it provide that we don't have today?

I'm generally against multi-tool integration as it makes setup too complex. Of course, if these tools wanted to use the features of EDDI if available that would be fine but each seems to have a different target market, with VoiceAttack's being embedded in VoiceAttack and the others being more of a client/server architecture.
 

sutex

sutex
jgm said:
What sort of communication would you want, and what would it provide that we don't have today?

I'm generally against multi-tool integration as it makes setup too complex. Of course, if these tools wanted to use the features of EDDI if available that would be fine but each seems to have a different target market, with VoiceAttack's being embedded in VoiceAttack and the others being more of a client/server architecture.
Click to expand...



The VA feature is whats missing from both the tools I use , wondering how EDDI may help ,
 
Last edited:

Straha Yeagar

S
I did notice that when using this variable with the (spoken) command, it give a "Not set" message...

From the github page...

- Ship callsign (spoken) (text): the callsign of the ship as shown in EDDI configuration as would be spoken

{TXT: Ship callsign (spoken)}


However using the simple {TXT: Ship callsign} works fine, but the dash in the XXX-1234 callsign is read as 'minus' so not as spoken...

I did work around this by manually editing the ship.json and took out the '-' and spelled out 'dash' so the call sign is literally XXX dash 1234 now.

Please note...in the above...I inserted spaces after {TXT:...} so it would read correctly instead of having a frown face...{TXT:Ship callsign} My actual script is correct without the spaces...
 
Last edited:
Status
Thread Closed: Not open for further replies.
Back
Top Bottom