- Status
It looks like deleting the file "credentials.json" from %appdata%/EDDI/ will allow EDDI to start again. I'd guess that file is getting corrupted by a failure to connect the companion API and that the best option is to delete that file, then wait until JGM gives the go-ahead before trying to sign back in to the Companion App.
Last edited:
Just now home and trying EDDI with 2.3... Yes, deleting the folder stops the crashing but still can not sign in...
Unexpected problem
Please report this at http://github.com/CmdrMcDonald/EliteDangerousDataProvider/issues
Microsoft.CSharp.RuntimeBinder.RuntimeException:Cannot perform runtime binding on a null reference
at CallSite.Target(Closure,CallSite,Object,String)
at System.Dynamic.UpdateDelegate.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, Ta arg1)
at EddiCompanionAppService.CompanionAppService.ShipFromProfile(Object json)
at EddiCompanionAppService.CompanionAppService.ProfileFromJson(JObject json)
at EddiCompanionAppService.CompanionAppService.ProfileFromJson(String data)
etc, etc
Anybody get EDDI working with 2.3?!?
I'm so dependent on EDDI and companion API data with my VA scripts, I'm literally dead in the water.
Going to call it a night and hope this gets resolved tomorrow.
EDIT: Yup, what Tkael said.
Last edited:
It's working for me. Not the plugin functions, at least not the ones I use, but the basic voice responder is as for landing pad location and things it can get from the journal file. I deleted the entire EDDI folder (after saving my profiles) and it works; all except for the ship name. Calls it "Your Python" in my case. And the other things that depend on the Frontier API aren't working but it does work after a fashion.
Deleting credentials.json will allow EDDI to work. None of the functions that depend on the companion app will work until the login issue get's fixed, but everything else works.
IIRC after an Elite update the companion API is offline for some time so I think Frontier hasn't re-activated it yet.
Just want to add my experience that it worked fine for me after the 2.3 commanders update until a windows (10x64) update later that evening.
I do not use the companion app or related functions anyway, mainly I use EDDI for its VoiceAttack variables and the computerised audio filter on the TTS voice, but deleting the credentials.json file does indeed allow the EDDI configuration app to run.
I do not use the companion app or related functions anyway, mainly I use EDDI for its VoiceAttack variables and the computerised audio filter on the TTS voice, but deleting the credentials.json file does indeed allow the EDDI configuration app to run.
The problem is that the JSON returned from the Companion API has changed slightly (in particular how the ships are represented). I've made a pull-request to the main github-repo that fixes this (https://github.com/cmdrmcdonald/EliteDangerousDataProvider/pull/186), so now we just have to wait for CmdMcDonald to merge it.
Indeed, he'll get on it as soon as he can. In my experience he fixes any problems pretty damn quick. Only now I realize how much I miss EDDI2 not telling me everything. But I'm glad I got some of my own custom scripts in EDDI VA that still work cause they are triggered by the journal and not the API.
I know, I really do appreciate all the work that goes into EDDI. I dearly miss it already too!
EDDi and Voice Pack Integration
Hi all,
While we are waiting for the fix to 2.2.2 has anyone been able to integrate EDDI and the HCS Voice Packs? I've read that Astra Multi crew works and there is a read me file that helps with doing this but all efforts have failed so far.
Cmd Aldrin
Hi all,
While we are waiting for the fix to 2.2.2 has anyone been able to integrate EDDI and the HCS Voice Packs? I've read that Astra Multi crew works and there is a read me file that helps with doing this but all efforts have failed so far.
Cmd Aldrin
I use a heavily modified 'hybrid' of HCS 'Astra' and 'Multi-Crew' and large chunks of my profile are 'dead in the water' because of reliance on EDDI API variables to initialize the profile.
HCS uses their own plugin that reads the journal file. I expect that the new journal file format in 2.3 is different enough for certain events to have broken their plugin in those places, which might explain the difficulty.
HCS 'Multi-Crew' profile uses EDDI, so it should be having the same issues everyone else is experiencing with the API portion of EDDI being non-functional.
Last edited:
Please excuse me for being dumb but I am very very new to all this plug in and voice control stuff and dont understand half of what I read. When you say multi crew uses EDDI does that mean I dont have to load it or run it separately? I bought ASTRA while the upgrade was coming down, got as far as "import chosen profile" to voice attack and got lost. Some of that was because EDDI had stopped working for me which I was not sure if it was due to the voice pack or the update. I uninstalled the voice pack to check and as it stands at the moment I have ED, voice attack, and EDDI running without the API. I would like to have it so EDDI works as it does telling me about stuff I scan, where the landing pad is etc, with the voice pack doing stuff like docking power change, and the voicepack stuff where I can ask it questiongs like "what is a red dwarf". Any guidance in what profiles I need to import would be greatly appreciated.
HCS has a voice pack profile called 'Multi-Crew', created by Cmdr ThingIs, that allows you to assign multiple HCS voices to different 'jobs'. For example, you could have Astra handle communications responses, Verity handles ship functions, etc. The profile utilizes EDDI external functions and, as we all, is crippled by the current API issue.
With regards to Astra, the choice of profile is 'Basic' or 'Full House', with Full House having all the Galacto-pedia stuff. Neither of them 'require' EDDI, but again I'm guessing that their proprietary plugin also requires an update to be fully functional with the changes made in 2.3.
It's taking a bit longer to get this out than I expected. I've been using the patched version myself for a couple of hours now, and it works a treat.
I thought I'd share the one needed file with you guys, so you can use EDDI while a fix and a new release is created. I've shared it at
https://www.dropbox.com/sh/kvevq3u9...SbJOuQba?dl=0&preview=EDDI_commanders_fix.zip
You need to drop the .dll in that zip into your EDDI -folder as described in the readme.
I thought I'd share the one needed file with you guys, so you can use EDDI while a fix and a new release is created. I've shared it at
https://www.dropbox.com/sh/kvevq3u9...SbJOuQba?dl=0&preview=EDDI_commanders_fix.zip
You need to drop the .dll in that zip into your EDDI -folder as described in the readme.
Thanks so much. I have been using the unconnected and it works but not with near the immersion. Your hard work is appreciated.
Thank you for your work, it's nice to have EDDI running again.
The HCS plugin is working fine with 2.3, no problems at all. There is an update coming with new features and the fixes for the gui changes. The multi-crew profile works with or without eddi but it's obviously better with. That will change in the next few days as multi-crew will be switching to using the hcs plugin instead. I have left full functionality for using either eddi or hcs or both....using both together actually gets the best of everything as there are things in the hcs plugin that eddi doesn't do and things that eddi does that we can't do. Its a marriage made in heaven
Last edited:
- Status