EDDI: A(nother) Voice Attack Plugin

Status
Thread Closed: Not open for further replies.
Yep this is a bug with the VA profile, where it isn't feeding the spoken callsign to EDDI's speak command. I'll fix this for the next release. Thanks for reporting it.



That should contain whatever the last event was. Current events include changing system or environment (supercruise/normal space), docking and changing ship. The former two should be triggered automatically whenever you jump, the latter two when you say "i have docked" or "ship handover complete".

If you aren't seeing any events when you jump system (more easily recognised by EDDI telling you about your destination) then it's probably down to the path to the netlog files being incorrect. The best way of obtaining this is to start up Elite itself, then go in to EDDI's configuration options and hit 'obtain'. This will try to fetch the path from the running process, which is the more reliable way of doing this.

Yeah and official bug, rather than me being a PEBCAK.

EDDI is working fine, I get all the voices when exiting and entering supercruise/star systems. I was just wondering why it stated an Event wasn't set, but I understand now, me thinks.
 
Last edited:
With 1.0, I've only had to restart the process once in four hours of playing, usually I'd have to restart the process approximately once per hour. Looking good, thanks.
 
The 'Access to NetLog is Enabled' confirms that EDDI is monitoring for netlog changes, but if the path is wrong it won't ever see any.

From your previous posts it looks like the path to your logs should be C:\Program Files (x86)\Frontier\EDLaunch\Products\elite-dangerous-64\Logs Could you set this in the configuration app and restart Voice Attack to see if it works when you change system?

If it doesn't work please could you send me the contents of the netlog, along with %APPDATA%\EDDI\eddi.log (if anything).

Ok, for my initial pro-active testing I still have some issues with EDDI ... BUT, I am not ready to call it quits on my testing...
I noticed last night the the AppConfigLocal.xml had:
<NetworkVerboseLogging="1"Port="0"upnpenabled="1"LogFile="netLog"DatestampLog="1">
</Network>

And that MAY have been better as:
<Network VerboseLogging="1"Port="0"upnpenabled="1"LogFile="netLog"DatestampLog="1">
</Network>
(To separate the command from the attribute, which COULD be a issue)

Second I realized my own potential screw-up on last night's fail could be because I had the VA Edit profile opened the whole time. Which can affect some of the Actions because the wrong active window.

So... TODAY's test will be with VA running the way it was intended, that the AppConfigLocal.xml may run better (or fail, but logic says attribute can't be touching command like that... they're not even dating...for shame)

So...ummm... ~Quiet on the set - Take 3~
 
one thing i have notice is when changing ships... its still calling the old ship name the new ship name for some reason its not updating to the new ship

cheers
 
I've updated to 1.0 and now whenever the plugin is called I get the error message "UNABLE TO INVOKE PLUGIN, PLUGIN NOT VALID FOR THIS VERSION OF VOICE ATTACK" in an infinite loop.

I wiped the eddi folder and unzipped again and also deleted all eddi command from my profile and back in again.

any ideas?

edit: it's ok link to the api had been lost. I forgot that when you delete the folder for an update it wipes the link out and you have to run the config again :)
 
Last edited:
I've updated to 1.0 and now whenever the plugin is called I get the error message "UNABLE TO INVOKE PLUGIN, PLUGIN NOT VALID FOR THIS VERSION OF VOICE ATTACK" in an infinite loop.

I wiped the eddi folder and unzipped again and also deleted all eddi command from my profile and back in again.

any ideas?

There is an issue where you need to be logged in to the companion API otherwise you can see this error. If you shut down VA, run the 'configuration' and ensure that you are logged in on the 'Companion App' tab, and then restart VoiceAttack does the issue persist?
 
The module summary worked fine but the module report and module overviw make no sound

Could this be my error I get from the not seeing my logs properly?
 
Last edited:
The module summary worked fine but the module report and module overviw make no sound

Could this be my error I get from the not seeing my logs properly?

Is this the module outfitting items? The report should give full details of any items that you can outfit to save money, the overview will only say something if there is something worth saying. What does the summary say?
 
Is this the module outfitting items? The report should give full details of any items that you can outfit to save money, the overview will only say something if there is something worth saying. What does the summary say?

((EDDI: module swapout summary)) - Tells me what can I swap out here
When I say "What can I swap here"

((EDDI: module swapout report)) - Doesn't say anything
When I saw "Swap Report"

((EDDI: module swapout overview)) - Doesn't say anything
When I say "Swap overview"


Now, since the 1st one works I know I am using it right
 
((EDDI: module swapout summary)) - Tells me what can I swap out here
When I say "What can I swap here"

((EDDI: module swapout report)) - Doesn't say anything
When I saw "Swap Report"

((EDDI: module swapout overview)) - Doesn't say anything
When I say "Swap overview"


Now, since the 1st one works I know I am using it right

If the module swapout summary works then the module swapout report should provide you with the same but more detailed information. But as you are calling these through your own commands it's hard to tell if there are any issues in them.

If you want to carry out a quick check of the features then you can edit them and add a hotkey. This will give you an idea of what it should provide when called.
 
i have to say something? hrm more stuff to tell it.. dang it :D

Yes unfortunately there is no way of EDDI knowing most things that happen in-game, with the exception of changes of system and jumping between supercruise and normal space. It would be wonderful if FD added a few more events to their netlog, but until then we're stuck with telling EDDI manually.
 
Yes unfortunately there is no way of EDDI knowing most things that happen in-game, with the exception of changes of system and jumping between supercruise and normal space. It would be wonderful if FD added a few more events to their netlog, but until then we're stuck with telling EDDI manually.

That's a shame I understand that FD is being cautious on what access they give for api's to prevent hackers/botters
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom