the api connection errors out everytime you try to set it up. i'm using Version 2.4.0-b4
- Status
woot! Finally i got a connection this morning! First try and BAAAN! "api is functional" ... Hope others can get back to EDDI at its full as well!
Thanks for the report. Which version of EDDI was this with please? Both are believed fixed in internal dev builds, but I'd have to check to see whether those fixes are in a public beta yet.
Oh, i'm sorry for holding that back. Always using latest version, b4 in this case. Any ETA for next release?
I'm having problems logging into Frontier API and I'musing EDDI V2.4.0-b4 both my email and password are correct so I know that they are not the issue, any-one know what s happening please.
PS. it only shows two of my four ships as well, not sure if thats connected to not being able to log in
PS. it only shows two of my four ships as well, not sure if thats connected to not being able to log in
Last edited:
It sounds like Frontier have had some success fixing the API now, I'd say it's worth trying again.
Beta 5 will include fixes for the shipyard issue but they need to be tested.
That worked apart from EDDI still only see 2 of my 4 ships
Thats what I meant by "Beta 5 will include fixes for the shipyard issue"
That may no longer be necessary. We are still seeing some issues with Coriolis export for engineered ships, but that is in hand.
EDDI 2.4 beta 5 is now available via the update mechanism or here.
Enjoy!
- EDDI can once again track how many limpets you have (and there was much rejoicing).
- The shipyard should now be populated correctly, but we are still working on exporting engineered modifications.
- Export to Coriolis is mostly working. There are some issues with very long URLs for heavily engineered ships: we are working with the Coriolis devs on it.
Enjoy!
woot shipyard is operational again! GOOOOOOD times! thank you so much for the release!
Hi,
Thank you EDDI-Team (or E-Team, A-Team...whichever you like
) for the update, API connection works again! 'Waiting-game' is over!
Best regards!
Thank you EDDI-Team (or E-Team, A-Team...whichever you like
) for the update, API connection works again! 'Waiting-game' is over!Best regards!
Hello Commanders,
I just wanted to give EDDI a try, as it seems not to require VA. But for me it doesn't do anything. What am I missing?
I downloaded EDDI and ran the setup. It installed to the default directory C:\Program Files (x86)\VoiceAttack\Apps\EDDI\ and starts. I updated to 2.4.0.b5 and it states "EDDI Status: Operational"
Frontier API is set up and logged in, the desired plugins are enabled (responders and monitors, except VoiceAttack responder and EDSM responder). I also managed to change the Windows TTS language from german to english (you can't imagine how cracy it sounds to have english pronounced with a german voice template^^)
I didn't find any entries for log paths (E is installed on another drive).
What did I miss? Or does it require VoiceAttack to configure?
DONE
Reminder to myself: Don't forget to restart your computer, when something doesn't work
I just wanted to give EDDI a try, as it seems not to require VA. But for me it doesn't do anything. What am I missing?
I downloaded EDDI and ran the setup. It installed to the default directory C:\Program Files (x86)\VoiceAttack\Apps\EDDI\ and starts. I updated to 2.4.0.b5 and it states "EDDI Status: Operational"
Frontier API is set up and logged in, the desired plugins are enabled (responders and monitors, except VoiceAttack responder and EDSM responder). I also managed to change the Windows TTS language from german to english (you can't imagine how cracy it sounds to have english pronounced with a german voice template^^)
I didn't find any entries for log paths (E
is installed on another drive).What did I miss? Or does it require VoiceAttack to configure?
DONE
Reminder to myself: Don't forget to restart your computer, when something doesn't work
Last edited:
Hello Commanders,
I just wanted to give EDDI a try, as it seems not to require VA. But for me it doesn't do anything. What am I missing?
I downloaded EDDI and ran the setup. It installed to the default directory C:\Program Files (x86)\VoiceAttack\Apps\EDDI\ and starts. I updated to 2.4.0.b5 and it states "EDDI Status: Operational"
Frontier API is set up and logged in, the desired plugins are enabled (responders and monitors, except VoiceAttack responder and EDSM responder). I also managed to change the Windows TTS language from german to english (you can't imagine how cracy it sounds to have english pronounced with a german voice template^^)
I didn't find any entries for log paths (E
What did I miss? Or does it require VoiceAttack to configure?
DONE
Reminder to myself: Don't forget to restart your computer, when something doesn't work
I'm not sure why it needed a restart. Anyhow, logs and all the config resides in %APPDATA%\EDDI if you need it.
- Status