Release Elite: Dangerous Market Connector (EDMC)

Status
Thread Closed: Not open for further replies.

Deleted member 38366

D
I'm having a bit of an issue with EDMC after taking my Carrier on its Exploration tour :

  • it apparently fails to identify the current Position sometimes (especially if unexplored)
  • it has failed to update a 3 Star System (no other Bodies) to EDSM
  • it has failed to report the exact position of a System to EDSM
  • the DistanceCalc Plugin also has stopped being able to show distances to marked Systems

Basically it's acting up while onboard a Carrier and hopping to unexplored (not in EDDB/EDSM) Systems with the Carrier (?)
Anyone else getting these issues? Carrier-related? Issue with Journals?
EDMC is the latest Version 3.4.4.0 for what it's worth , never had such issues with it. DistanceCalc plugin is also updated to the latest version.

1592691789066.png


PS.
When leaving the System with a normal Ship and entering the next best Unexplored System, everything is working 100% fine as expected.

Trying to manually upload the Journals to EDSM to feed it the "lost Systems" oddly doesn't work either. EDSM doesn't recognize the System to even exist after entering it with a Carrier.
Seems there's something wrong or different with the Journal/API when being onboard a Carrier and entering an Unexplored System (?)
 
Last edited by a moderator:

gazelle

gazelle
FalconFly said:
I'm having a bit of an issue with EDMC after taking my Carrier on its Exploration tour ...
Click to expand...
It's beeing worked on. Version 3.4.6 (3.4.5 is internal only) will support the new CarrierJump event which will resolve the issue.

A workaround for now would be to exit to the main menu and log back in after every carrier jump (if you jump on the carrier), so there will be a new Location event generated.
 
Last edited:

Athan

Athan
gazelle said:
It's beeing worked on. Version 3.4.6 (3.4.5 is internal only) will support the new CarrierJump event which will resolve the issue.

A workaround for now would be to exit to the main menu and log back in after every carrier jump (if you jump on the carrier), so there will be a new Location event generated.
Click to expand...
Also note that EDSM doesn't yet process (but it will store for later processing when the programming work is done) the CarrierJump events. So until EDSM updates you'll still need to do the logout/in thing to have it properly update your location even once I release he EDMC version that handles the event.
 

Athan

Athan
For any of you who have been using the pre-release "3.50 beta0" I've just made a "3.51 beta0" release which updates this to include the bug fixes and features I've added ready for the forthcoming 3.46 full release (which will be the last release based on Python 2.7).
So if and ONLY if you have been using that '3.50 beta0' please update to Pre-release 3.51 beta0
 

Athan

Athan
Release 3.46
This should be the final release of EDMC based on Python 2.7. The next release after this, assuming this one doesn't introduce new bugs, will be based on Python 3.7. Any plugins that users have installed will need to have been updated to work under Python 3.7 by the time that next version of EDMC is released. During EDMC startup, at most once per day, you might see a popup with the text:

One or more of your enabled plugins do not yet have support for Python 3.x. Please see the list on the 'Plugins' tab of 'File' > 'Settings'. You should check if there is an updated version available, else alert the developer that they will need to update the code when EDMC moves to Python 3.x
Click to expand...

If so, do as it directs and check File > Settings > Plugins tab and see what plugins are listed in the section with the text Plugins Without Python 3.x Support.
If any of your plugins are listed in that section then they will need updating, by you or the original developer, to work with Python 3.7. See Migrating to python 3.7 for more information.
Anyone who wishes to try out the forthcoming Python 3.7-based version should see Release 3.51 beta0, but please do not install that unless you're technically savvy enough to make coherent bug reports, thankyou.
Changes in this version:
  • The CAPI CLIENT_ID has been changed to one under Athanasius' account, so when users are asked to (re-)authenticate with Frontier they'll see Elite Dangerous Market Connector (EDCD/Athanasius) as the application asking for permission. There's been no change to the use of the data Frontier then gives access to.
  • Updated translations (as of 2019-09-26 in general and 2019-11-04 for Polish).
  • Linux: Should now appear on task bar whilst in dark mode theme.
  • INARA: Send correct opponentName for Interdicted and Interdiction events.
  • Send SAASignalsFound events to EDDN.
  • Add Agronomic Treatment introduced for a community goal.
  • Fix Detailed Surface Scanner rating.
  • Fix for the "Inara 400 The reputation value exceeds the valid range" error.
  • Minimum interval between checks for a new version of EDMC has been reduced from 47 hours to 8 hours.
  • There is a new option, within the 'Configuration' tab, 'Disable Automatic Application Updates Check when in-game' which when active should prevent update checks from showing a popup whilst you're in-game. You can still use Help > Check for updates to trigger a manual check.
  • Support added for the journal CarrierJump event, triggered when you're docked on a Fleet Carrier as it performs a jump. This is now sent to: EDDN, Inara, EDSM. NB: EDSM doesn't yet support this event at the time of writing, so will still not track such Carrier Jumps in your Flight Log or current location. Generally when EDSM is updated to handle such new events it will back-process stored unrecognised events.
 
Status
Thread Closed: Not open for further replies.
Top Bottom