EDDI: A(nother) Voice Attack Plugin

Status
Thread Closed: Not open for further replies.

foxpur

foxpur
Urrrr... this is new...

"22:02:49 - UNABLE TO INVOKE PLUGIN. PLUGIN NOT VALID FOR THIS VERSION OF VOICEATTACK."

but still use beta 1.5.8.14 of VA and ver 1.0.0 of your EDDI.... ummm... (in my best Professor Farnsworth impression) Wha??

EDIT: SOLVED! For some reason I lost some of the configuration. (Sadly, even those I got rid of my other ED Versions it still fails on my logs directory)
 
Last edited:

jgm

jgm
Soopyyy said:
Ah, where is the configuration.exe?
Click to expand...

It's in the same directory as the EDDI plugin, so by default it should be c:\Program Files(x86)\VoiceAttack\Apps\EDDI (or similar).

- - - - - Additional Content Posted / Auto Merge - - - - -

tehface said:
any way we can change the callsign of the ships in the configuration.exe ?

thanks
Click to expand...

The only way would be to hand-edit the ships.json file in %APPDATA%\EDDI although if you change the format of the callsign it could break things.
 

Jetkar

Jetkar
@jgm one thing which is annoying is that every time EDDI is updated we have to request user authentication access for ED api with FD. Their must be way to save this for future EDDI updates so we don't need to re-run the configuration program unless absolutely necessary.
 
Last edited:

jgm

jgm
Jetkar said:
@jgm one thing which is annoying is that every time EDDI is updated we have to request user authentication access for ED api with FD. Their must be way to save this for future EDDI updates so we don't need to re-run the configuration program unless absolutely necessary.
Click to expand...

It should survive, as the tokens are stored in %APPDATA%\EDDI and this shouldn't be removed in the upgrade.
 

tehface

tehface
jgm said:
It's in the same directory as the EDDI plugin, so by default it should be c:\Program Files(x86)\VoiceAttack\Apps\EDDI (or similar).

- - - - - Additional Content Posted / Auto Merge - - - - -



The only way would be to hand-edit the ships.json file in %APPDATA%\EDDI although if you change the format of the callsign it could break things.
Click to expand...

ah ok i'll have a poke... thanks heaps
 

jgm

jgm
Soopyyy said:
Hrmm, now it wont detect the logs file, even though I am 100% positive its the correct location...
Click to expand...

When you start VoiceAttack you should see:

  • Plugin support enabled
  • Profile startup: '((EDDI: startup))'
  • Plugin 'EDDI 1.0.0' initialized

If you do see this please could you paste the contents of %APPDATA%\EDDI\netlog.json here along with a sample netlog file where you have changed system? Thank you.
 

jgm

jgm
foxpur said:
Yeah... It IS KINDA HARD TO FIND... hint! hint! ;)
Click to expand...

I've added a direct download link to the OP, although given that it was in the middle of the installation instructions I hope this doesn't lead to a rash of people who download it without reading the instructions on how to install/configure it.
 

foxpur

foxpur
jgm said:
I've added a direct download link to the OP, although given that it was in the middle of the installation instructions I hope this doesn't lead to a rash of people who download it without reading the instructions on how to install/configure it.
Click to expand...

Be sure it is a READ Me First file... could make it PART of the configuration file with a note it is ALSO in the Read Me First... kind of MASS OVERKILL :)
 

CMD Malandark

CMD Malandark
Throughout EDDI's development I have noticed that EDDI will occasionally lose it's credentials to the FD API for no reason at all. It runs fine for a few days, then for no reason at all it cant connect to the API, forcing me to re-enter my ED email & password into the configuration app in order to access the API again. I sometimes run EDMarketConnector every couple of days which I have had installed for the past couple of months and this has never asked me to relog into the FD API.
 

foxpur

foxpur
CMD Malandark said:
Throughout EDDI's development I have noticed that EDDI will occasionally lose it's credentials to the FD API for no reason at all. It runs fine for a few days, then for no reason at all it cant connect to the API, forcing me to re-enter my ED email & password into the configuration app in order to access the API again. I sometimes run EDMarketConnector every couple of days which I have had installed for the past couple of months and this has never asked me to relog into the FD API.
Click to expand...

I literally was JUST logging in to say the same issue.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom