Happening to me too.
Release EDDiscovery 18.X is now out! New modules panel upgrade and Engineering
- Thread starter robbyp
- Start date
Happening to me too.
Hi all..fairly new to this game and just the other day a friend recommended I check out this tool. He especially loved the voice add-on (VoicePackv4). I just installed the latest version 8.2.7 and went to Manage Add-ons to install it, but I don't see it as an option. At least I assume that's what I'm suppose to do based on this page. https://github.com/EDDiscovery/EDDis...ng-voice-packs Am I misunderstanding something?
The add-ons I see are: JKMV1, KeyPressesV2, KeyPressesV3, obsv1, SoundBlasterV1, and video1.
Thanks for any help!
The add-ons I see are: JKMV1, KeyPressesV2, KeyPressesV3, obsv1, SoundBlasterV1, and video1.
Thanks for any help!
Been having an issue with ED crashing every now and again whilst flying through systems.
Eventually sent a ticket to FDev. They thought it was being caused by a 3rd party ap - most likely EDD, not sure if you've heard about it or any tips?
Told them I'd rather have the functionality of EDD and put up with the occasional crash
!
Eventually sent a ticket to FDev. They thought it was being caused by a 3rd party ap - most likely EDD, not sure if you've heard about it or any tips?
Told them I'd rather have the functionality of EDD and put up with the occasional crash
!
That's very unlikely that EDDiscovery would be making ED crash. (1) it's rock solid for me and (2) as a programmer I can't see how that's even possible.
Considering that ED has API calls that EDD uses, it's quite possible. Maybe EDD is requesting information that isn't ready yet, and the game crashes instead of returning a null response.
IMO, it's lazy for them to say that the problem is being caused by the 3rd party ap - the fix for the crash will have to be implemented by ED devs, not the EDD devs. Though the EDD devs will probably have to get involved to figure out what command is causing the crash, to turn the ticket from "ED sometimes crashes while using EDD" to "ED crashes when API.Function() gets called with {foo,bar} arguments"
Source: found several ways to crash the WoW client while working with the Auctioneer dev team.
The API that EDD (and several other apps) call is a server API. EDD isn't connected to the client app in any way. Moreover the server in question is down at the moment, and the latest build of EDD has its API calls turned off.
EDD is a great app. It is a system hog, though.
Waiting for the API to be turned back on.
Waiting for the API to be turned back on.
What's wrong with the ingame 1?
It was an accident. 8.3.2 is now out with a fix.
Apologies if this has been asked.. but is there any word yet on when the Companion API will be working again? Is it on Frontier's end where things need to get fixed? (still getting the "Companion API is temporarily disabled due to changed in the API by Frontier for 2.4.As Arnie says, I'll be back!" warning message).
I keep thinking it says Amie
No. We don't call any functions in ED. ED writes a file, and we read it. We do not interact with Elite dangerous in any other way. So your supposition is completely incorrect.
We have reduced processor usage to <1% (found out why it was hogging) Mine runs with practically no usage of processing when its just sat there. Obv if you do something it peaks.
First runs after installation will be hoggy while it syncs with EDSM and creates databases. Dep. on your internet connection it may take 30mins or so to do this.
Screenshots views are now in a panel pop out or on one of the four configurable panels in history. Settings are on the settings page for screenshots.
This is in aid of removing all the special major tabs except history and settings, and moving the functionality of them to panels (they are like this for historical reasons). We will be making the tabs fully configurable in number and in content, so you can have many major tabs with your chosen mix of panels.
Last edited:
We will be turning this back on today or tomorrow, dependent when either Finwen or I can get time..
Or at least once the Companion API settles down. It's still failing a lot.
My apologies.