EDDI: A(nother) Voice Attack Plugin

Status
Thread Closed: Not open for further replies.
not installed beta eddi yet, ans was playing in normal game....

That suggests a problem with FD's companion API. Unfortunately I can't fire up E:D from here so can't check to be sure. EDDI does not retain information about your current ship between instances, however, so it's unlikely to be a problem on its end.
 
cheers....
the pack allows me to manually tell it what ship im in, so i just yelled PYTHON at it and it overrode it for me ;-)
 
  • Like (+1)
Reactions: jgm
Just chiming in as I set this up tonight and woah Billy, possibly my favorite Elite add-on so far. It really is fantastic and adds even more immersion to the sim. Excellent job!
 
Is this with EDDI 1 or 2? If 1 then please follow the troubleshooting instructions at https://github.com/cmdrmcdonald/EliteDangerousDataProvider/blob/master/TROUBLESHOOTING.md. If 2 then please check out https://github.com/cmdrmcdonald/EliteDangerousDataProvider/blob/feature/journal/VoiceAttack.md If you still don't have any luck then please send me the contents of %APPDATA%\eddi.log and I'll take a look.

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



I'm not seeing any problems with the API, although note that if there is a problem with it you'll lose some information on the systems you are visiting but all commander etc. information should still be present.

If your commander information is unavailable then this suggests a problem with EDDI's configuration so that it cannot obtain the data from Frontier's companion API, or with Frontier's API itself. If this is the case feel free to send me your %APPDATA%\eddi.log and I can see if I can find out what's wrong.

Thanks, I was playing beta and had mapped the main game.... Anyway waiting for the update to test the other features. Still not easy to jave it work in English on a French computer :)
 
Status
Thread Closed: Not open for further replies.
Top Bottom