EDDI: A(nother) Voice Attack Plugin
- Thread starter jgm
- Start date
- Status
At least we get a notice that makes it clear where to fix it.
me too with this so atleast it's consistent 
also, is there any way to turn off the effects you added for the tts? It was fine until a few days ago but something has now changed the voice so it sounds terrible, all fuzzy and distorted.
also, is there any way to turn off the effects you added for the tts? It was fine until a few days ago but something has now changed the voice so it sounds terrible, all fuzzy and distorted.
@jgm I am getting a similar problem again ....I did tell you this before
there is no notice about how to fix it... get plugin error.. i made the assumption it was the login stuff in the config...
me too with this so atleast it's consistent
also, is there any way to turn off the effects you added for the tts? It was fine until a few days ago but something has now changed the voice so it sounds terrible, all fuzzy and distorted.
There is no way of turning this off at the moment, although the next release will have this ability. If the voice is fuzzy and distorted it's probably because your hull is damaged. Try repairing it and saying "ship handover completed" to see if that fixes it.
- - - - - Additional Content Posted / Auto Merge - - - - -
Yeah unfortunately there is no easy way of flagging this for two reasons. First, the plugin initialisation runs asynchronously so there is no place I can run a "if the companion app didn't work then complain" command on startup. Second, some people want the EDSM and netlog integration without the companion app piece so might have it off on purpose.
I'm slowly going through the various commands that will have missing data if one or another piece of data is not being gathered and tweaking them to respond accurately, but the only sure-fire way of knowing the state of the companion app is to hit ctrl-alt-shift-e and see if it is stated as enabled or not.
aha that is actually very cool jgm....just one slight problem, I am on distant worlds and will not be returning to a station for 6 more months
aha that is actually very cool jgm....just one slight problem, I am on distant worlds and will not be returning to a station for 6 more months
Okay that's a problem then. I'm working on the next release for a couple of weeks' time but if you need a custom version that doesn't distort the voice on hull damage I can send you one over to help out in the meantime.
Last edited:
that would be most appreciated, thank you.
I inserted the following highlighted script inside the ((EDDI:event loop)) and it does a pretty good job in letting me know when EDDI loses the API connection the moment this command is executed by EDDI.
Set Boolean [EDDI event loop active] to True
Start Loop While [EDDI event loop active] Equals True
Execute external plugin, 'EDDI 1.0.0' and wait for return
Begin Text Compare : [{TXT:EDDI plugin profile status}] Equals 'Disabled'
Say, 'Warning, EDDI is not connected to the FD API, please re-run the configuration app found in the EDDI folder.' (and wait until it completes)
Write '[Red] Warning, EDDI is not connected to the FD API, please re-run the configuration app found in the EDDI folder....' to log
End Condition - Exit when condition met
Begin Text Compare : [EDDI event] Equals 'System change'
Execute command, '((SC: System Report))' (and wait until it completes)
Else If Text Compare : [EDDI event] Equals 'Environment change'
Execute command, '((EDDI: event handler for change of environment))' (and wait until it completes)
.....
........
...........
Snip
Last edited:
Yeah I considered putting it in the event loop but then it requires an event to trigger before the check is made. Ideally VoiceAttack would allow you to run a command after EDDI has initialised but there is no way to do this in the current version.
One of the things that I'm looking at for the next release of EDDI is better integration with EDSM. At the moment it just sends details on each system you visit but adding co-ordinates without having to switch to a third party app would be nice.
Here is my idea so far: when you enter a system EDDI lets you know if the system's location is currently unknown. If you want to add co-ordinates then the way that you would do this is roughly as follows:
It's relatively clunky in a number of locations but VoiceAttack is very limited in this situation. Regarding the systems to measure distances: I'd put in a few obvious systems that would be handy for trilateration (Sol, Maia, 17 Draconis, Robigo, probably a few more) and users could add their own by copying an existing VoiceAttack command and tweaking it with the name of their favourite system.
My question for those of you using EDDI is: is this something that you would use, and if so do you have any suggestions on how to improve it?
Here is my idea so far: when you enter a system EDDI lets you know if the system's location is currently unknown. If you want to add co-ordinates then the way that you would do this is roughly as follows:
- Fire up the galaxy map and pick one of a number of pre-set named stars (for example Sol)
- Say to EDDI "Distance to Sol"
- EDDI will respond with "How far is it to Sol, in light years?"
- Say to EDDI "one hundred and twenty three point four five"
- Say to EDDI "Repeat distance"
- EDDI will respond with the distance it thinks you said
- If EDDI has the correct distance then say to EDDI "Distance confirmed" and it will send the distance to EDSM
- If not then say "Distance to Sol" again and try again
It's relatively clunky in a number of locations but VoiceAttack is very limited in this situation. Regarding the systems to measure distances: I'd put in a few obvious systems that would be handy for trilateration (Sol, Maia, 17 Draconis, Robigo, probably a few more) and users could add their own by copying an existing VoiceAttack command and tweaking it with the name of their favourite system.
My question for those of you using EDDI is: is this something that you would use, and if so do you have any suggestions on how to improve it?
I love the samples you put out, and really wanted to try EDDI out for myself.
I installed the latest beta VA, downloaded EDDI and did all the configuration. Everything seems ok. But:
Every time I start VA with EDDI, the EDDI: event loop runs into a neverending 'not set' loop. But I cannot figure out what is not set.. (looked at the event loop, but I am no programmer and I pretty soon stopped trying to figure out where the problem might be..)
Could you pm me the contents of %APPDATA%\EDDI\eddi.log and %APPDATA%\EDDI\speech.log and I'll try to work out what the problem is?
First, thanks for this terrific addon! It really adds some things that really personalize the experience. However, I am having some trouble. For some reason, once it a while, I get this "10:15:29 PM - UNABLE TO INVOKE PLUGIN. PLUGIN NOT VALID FOR THIS VERSION OF VOICEATTACK." Reading over and over again in the VA window. I am using Pre release v1.5.8.14 of VA. Is this not the correct version or is there something else I need to look into.
Thanks again for all your hard work and dedication.
Thanks again for all your hard work and dedication.
Re-run the configuaration.exe and re-enter your data that get's randomly wiped
QUESTION or FEATURE REQUEST:
When entering a system EDDI gives me that system information however the only part that is wrong is the number of times I've entered said system, however it's only correct if I've entered a system for the first time whilst using EDDI, it does not get any details from my logs or EDSM, even though the EDSM API key has been set. So have I set something up incorrectly or doesn't EDDI use the information from the LOGS/EDSM? If the latter is there a way (feature request) to let EDDI get the real information from either my logs or EDSM?
I know precisely how many times I've entered a system via EDDiscovery and also EDTB which also has a VA plugin that uses this information correctly, it even tells me the first time I entered said system.
Which brings me smoothly on to another question? I think EDDI and EDTB provide very similar functionality but do things slightly differently, with EDTB only pipping up in VA when asked for information rather than with EDDI being proactive and responding to commands, plus EDTB has a web front end. I think it would be great to have these two tools somehow work (merged) together as one tool. But that's me not considering you and the creator of EDTB future development goals. Just a thought.
RANDOM PROBLEM:
Also I've noticed that about 1 in 3 startups of VA with EDDI it fails to start up correctly and I get the error "UNABLE TO INVOKE PLUGIN. PLUGIN NOT VALID FOR THIS VERSION OF VOICEATTACK" which means I have to run the Configuration again. So the issue is that EDDI losses the configuration details somehow. There doesn't seem to be a way of reproducing this problem it just happens sometimes. Has anyone else noticed this? Yes I'm using the beta version of VA.
When entering a system EDDI gives me that system information however the only part that is wrong is the number of times I've entered said system, however it's only correct if I've entered a system for the first time whilst using EDDI, it does not get any details from my logs or EDSM, even though the EDSM API key has been set. So have I set something up incorrectly or doesn't EDDI use the information from the LOGS/EDSM? If the latter is there a way (feature request) to let EDDI get the real information from either my logs or EDSM?
I know precisely how many times I've entered a system via EDDiscovery and also EDTB which also has a VA plugin that uses this information correctly, it even tells me the first time I entered said system.
Which brings me smoothly on to another question? I think EDDI and EDTB provide very similar functionality but do things slightly differently, with EDTB only pipping up in VA when asked for information rather than with EDDI being proactive and responding to commands, plus EDTB has a web front end. I think it would be great to have these two tools somehow work (merged) together as one tool. But that's me not considering you and the creator of EDTB future development goals. Just a thought.
RANDOM PROBLEM:
Also I've noticed that about 1 in 3 startups of VA with EDDI it fails to start up correctly and I get the error "UNABLE TO INVOKE PLUGIN. PLUGIN NOT VALID FOR THIS VERSION OF VOICEATTACK" which means I have to run the Configuration again. So the issue is that EDDI losses the configuration details somehow. There doesn't seem to be a way of reproducing this problem it just happens sometimes. Has anyone else noticed this? Yes I'm using the beta version of VA.
Last edited:
I'm working on better EDSM integration for the next release. It will include the ability to sync EDDI's local data with EDSM, so if you have your full log in EDSM you can hit this button once on configuration and it will pull down the current state of your logs for things like last visit and total number of visits. It will also pick up on any notes you have made in EDSM and allow you to set and clear notes from within EDDI.
EDTB is quite focused on the web frontend, which is a big difference to EDDI which is purely voice activated. I'm thinking of EDDI as much more something that can be used to provide a better VoiceAttack experience, especially for those with VR or single monitors, rather than another screen. That said there could well be some information sharing that would be worthwhile, but I'm wary of making EDTB a requirement for EDDI to run.
Yeah this is a very frustrating issue. It's most likely down to some cookies I'm either setting or not setting, but there are some issues with C# (the language in which EDDI is written) and cookie handling when a webserver does redirects like FD's does. I've made a few changes after looking at other code that talks to the companion app and will continue to try to hunt this one down.
I'm pleased to announce the beta release of the next version of EDDI. There are various bug fixes and a number of new features:
If you are interested in testing the beta please download it at http://www.mcdee.net/elite/EDDI-1.1.0-beta1.zip Standard instructions for upgrading apply. Details on how to use the new features is available at https://github.com/cmdrmcdonald/EliteDangerousDataProvider/blob/develop/README.md
Please let me know if you encounter any problems with the beta, or have any feedback on the new features. Thanks.
- Added configuration option to set insurance excess percentage
- Added Insurance (decimal): the percentage insurance excess (usually 5, 3.75 or 2.5)
- Added Ship limpets carried (int): the number of limpets carried by the ship
- Added 'generate callsign' plugin context
- Added configuration of the ship voice
- Added configuration option to sync EDSM data with local information
- Added ability to set and recollect notes from EDSM
- Added ability to carry out trilateration of systems for EDSM
- Added phonetic pronunciation for ship names
If you are interested in testing the beta please download it at http://www.mcdee.net/elite/EDDI-1.1.0-beta1.zip Standard instructions for upgrading apply. Details on how to use the new features is available at https://github.com/cmdrmcdonald/EliteDangerousDataProvider/blob/develop/README.md
Please let me know if you encounter any problems with the beta, or have any feedback on the new features. Thanks.
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 ..
This may be what causes many of the things I try to do with EDDI from working regularly. I mean, I know my log folder by heart and "C:\Program Files (x86)\Frontier\EDLaunch\Products\elite-dangerous-64\Logs" is definitely it...
Is there a cache where the older settings could be holding up?
EDIT: Obtaining the EDSM log still working, about 5 minutes so far.
Last edited:
- Status