As someone who remembers "the good old days" of running screenshots through OCR, ditto. This is fantastic.
cmdr_data()
function.I can only assume some plugin you're using has been poking where it shouldn't.
There might be some clue as to which additional plugin is causing this in your log files. As it's probably of the 'uncaught exception' type I'd check the plain log file first.
CAPI-(Live|Legacy)-<endpoint>
" as per the updated documentation.CAPI-Live-<endpoint>
" for the time being.CAPI-UNKNOWN-<endpoint>
".pts-companion.orerve.net
has been used, due to detecting an alpha or beta version of the game. However, in that case the /test
schemas will be used.config
module are for setting/getting/removing a plugin's own configuration, or detecting application shutdown in progress.data
passed to a plugin cmdr_data()
is, strictly speaking, an instance of CAPIData
, which is an extension of UserDict
. It has some extra properties on it, but these are for internal use only and no plugin should rely on them.Are you playing in Legacy ?For some reason, after installing the new update, EDMC is no longer feeding EDSM for me, and is not reading it to get the "yellow star" for new systems showing on the EDMC little grey box either. How can I fix the connection? I don't where to start looking.
I am playing the latest Odyssey. I have checked the API key codes match.
Any and all help appreciated!
I did a couple of journal imports to EDSM, and have jumped two systems since, and it has started working automatically now. I don't know what went on there but it seems back to normal. I've created an account on Github though, in case you want to see the log files (providing I can work out where they are and where to put them).@Frankymole OK, I was blind there. If you're playing Odyssey then I'll need you to open a full bug report on github, principally so I can look at your log files to see if they offer any clues.
As someone who's just done this for the first time it's fairly easy as long as you can use Windows Explorer. The instructions are all there in the ticket screen that Athan linked to. One log file is in the %TEMP%\EDMarketConnector\ directory, just paste that into the Explorer address bar. The other is in the parent directory %TEMP% so go up to that and find the EDMarketConnector.log file in the long list of files in the temp directory. That's the only tricky part, finding that one file in a big list. Drag and drop the file from Explorer onto the Github ticket browser window, you might need to move the Explorer window so that you can see where to drop the file (anywhere in the ticket text box).I did a couple of journal imports to EDSM, and have jumped two systems since, and it has started working automatically now. I don't know what went on there but it seems back to normal. I've created an account on Github though, in case you want to see the log files (providing I can work out where they are and where to put them).
[EDMarketConnector.log](https://github.com/EDCD/EDMarketConnector/files/10111760/EDMarketConnector.log)
[EDMarketConnector-debug.log](https://github.com/EDCD/EDMarketConnector/files/10111763/EDMarketConnector-debug.log)
Thank you, that is really helpful!As someone who's just done this for the first time it's fairly easy as long as you can use Windows Explorer. The instructions are all there in the ticket screen that Athan linked to. One log file is in the %TEMP%\EDMarketConnector\ directory, just paste that into the Explorer address bar. The other is in the parent directory %TEMP% so go up to that and find the EDMarketConnector.log file in the long list of files in the temp directory. That's the only tricky part, finding that one file in a big list. Drag and drop the file from Explorer onto the Github ticket browser window, you might need to move the Explorer window so that you can see where to drop the file (anywhere in the ticket text box).
Once you've done that you will see a couple of links appear in the text like this:
Code:[EDMarketConnector.log](https://github.com/EDCD/EDMarketConnector/files/10111760/EDMarketConnector.log) [EDMarketConnector-debug.log](https://github.com/EDCD/EDMarketConnector/files/10111763/EDMarketConnector-debug.log)
Make sure that that code appears in the right place in your ticket text and that you don't mess it up in any way.
I had this exact same problem after installing the previous update, it didn't seem to send anything for a while, and then just started working.
webbrowser.open(<url>)
.EDMC.exe -n
had been broken for a while, it now functions once more.gameversion
from Journals has been moved from INFO to DEBUG. This returns the output of any EDMC.exe
command to the former, quieter, version.uploaderID
string being sent to EDDN. Such messages are still accepted by the EDDN Gateway, and the Relay then obfuscates this field anyway. So, at worse, this would make it look like the same uploader was in lots of different places. This has been fixed.replay.jsonl
was being emitted even when there was no file to convert. This has been fixed.cmdr_data_legacy()
, which mirrors the functionality of cmdr_data()
, but for Legacy data only. See PLUGINS.md for more details.cmdr_data()
and cmdr_data_legacy()
is now correctly typed as CAPIData
. This is a sub-class of UserDict
, so you can continue to use it as such. However, it also has one extra property, source_host
, which can be used to determine if the data was from the Live or Legacy CAPI endpoint host. See PLUGINS.md for more details.config.get_int('theme')
, then be aware that we've finally moved from hard-coded values to actual defined constants. Example use would be as in:from config import config
from theme import theme
active_theme = config.get_int('theme')
if active_theme == theme.THEME_DARK:
...
elif active_theme == theme.THEME_TRANSPARENT:
...
elif active_theme == theme.THEME_DEFAULT:
...
else:
...
NavRoute.json
will now be loaded during 'catch-up' when EDMarketConnector is (re-)started. The synthetic StartUp
(note the capitalisation) event that is emitted after the catch-up ends will have state['NavRoute']
containing this data.Fileheader
event from detecting a subsequent new Journal file will blank this data again. Thus, if you're interested in "last plotted route" on startup you should react to the StartUp
event. Also, note that the contents will indicate a NavRouteClear
if that was the last such event.develop
branch, please don't. Whilst we try to ensure that any code merged into this branch doesn't contain bugs, it hasn't at that point undergone more thorough testing. Please use the stable
branch unless otherwise directed.edmc_data
as a part of reviewing the latest update to coriolis-data
.edmc_data
up to date. Any plugins attempting to use that data should look at alternatives, such as FDevIDs/outfitting.csv.Very admirable, the effort to support Legacy-mode CMDRs.Pre-Release 5.7.0-rc1
This release allows CAPI queries for Legacy players. This means that the 'Update' button functionality is restored, along with "Automatically update on docking".
- We now test against, and package with, Python 3.11.1, 32-bit.
- As noted above, Legacy players now have CAPI functionality once more. Plugin developers check below for how you can determine the source galaxy of such data.
- Due to a bug it turned out that a workaround for "old browsers don't support very long URLs" had been inactive since late 2019. As no-one has noticed or complained we've now removed the defunct code in favour of the simple
webbrowser.open(<url>)
.
Testing showed that all of Firefox, Chrome and Chrome-based Edge worked with very long URLs without issues.EDMC.exe -n
had been broken for a while, it now functions once more.- Some output related to detecting and parsing
gameversion
from Journals has been moved from INFO to DEBUG. This returns the output of anyEDMC.exe
command to the former, quieter, version.Bugs
- A corner case of "game not running" and "user presses 'Update' button" would result in an empty
uploaderID
string being sent to EDDN. Such messages are still accepted by the EDDN Gateway, and the Relay then obfuscates this field anyway. So, at worse, this would make it look like the same uploader was in lots of different places. This has been fixed.- The message about converting legacy
replay.jsonl
was being emitted even when there was no file to convert. This has been fixed.Plugin Developers
- An erroneous statement about "all of Python stdlib" in PLUGINS.md has been corrected. We don't/can't easily include all of this. Ask if any part of it you require is missing.
- In order to not pass Legacy data to plugins without them being aware of it there is now a new function
cmdr_data_legacy()
, which mirrors the functionality ofcmdr_data()
, but for Legacy data only. See PLUGINS.md for more details.- The data passed to
cmdr_data()
andcmdr_data_legacy()
is now correctly typed asCAPIData
. This is a sub-class ofUserDict
, so you can continue to use it as such. However, it also has one extra property,source_host
, which can be used to determine if the data was from the Live or Legacy CAPI endpoint host. See PLUGINS.md for more details.- If any plugin had been attempting to make use of
config.get_int('theme')
, then be aware that we've finally moved from hard-coded values to actual defined constants. Example use would be as in:
But remember that all tkinter widgets in plugins will inherit the main UI current theme colours anyway.Code:from config import config from theme import theme active_theme = config.get_int('theme') if active_theme == theme.THEME_DARK: ... elif active_theme == theme.THEME_TRANSPARENT: ... elif active_theme == theme.THEME_DEFAULT: ... else: ...
- The contents of
NavRoute.json
will now be loaded during 'catch-up' when EDMarketConnector is (re-)started. The syntheticStartUp
(note the capitalisation) event that is emitted after the catch-up ends will havestate['NavRoute']
containing this data.
However, theFileheader
event from detecting a subsequent new Journal file will blank this data again. Thus, if you're interested in "last plotted route" on startup you should react to theStartUp
event. Also, note that the contents will indicate aNavRouteClear
if that was the last such event.
PLUGINS.md has been updated to reflect this.- If you've ever been in the habit of running our
develop
branch, please don't. Whilst we try to ensure that any code merged into this branch doesn't contain bugs, it hasn't at that point undergone more thorough testing. Please use thestable
branch unless otherwise directed.- Some small updates have been made in
edmc_data
as a part of reviewing the latest update tocoriolis-data
.
We make no guarantee about keeping these parts ofedmc_data
up to date. Any plugins attempting to use that data should look at alternatives, such as FDevIDs/outfitting.csv.
A future update might remove those maps, or at least fully deprecate their use by plugins. Please contact us now if you actually make use of this data.
It was mostly that I was very cautious with 5.6.0. It turned out that the work I did there to ensure CAPI did not work for Legacy players until I tested things enabled it being easy to then enable it for them.Very admirable, the effort to support Legacy-mode CMDRs.
webbrowser.open(<url>)
.EDMC.exe -n
had been broken for a while, it now functions once more.gameversion
from Journals has been moved from INFO to DEBUG. This returns the output of any EDMC.exe
command to the former, quieter, version.uploaderID
string being sent to EDDN. Such messages are still accepted by the EDDN Gateway, and the Relay then obfuscates this field anyway. So, at worse, this would make it look like the same uploader was in lots of different places. This has been fixed.replay.jsonl
was being emitted even when there was no file to convert. This has been fixed.cmdr_data_legacy()
, which mirrors the functionality of cmdr_data()
, but for Legacy data only. See PLUGINS.md for more details.data
passed to cmdr_data()
and cmdr_data_legacy()
is now correctly typed as CAPIData
. This is a sub-class of UserDict
, so you can continue to use it as such. However, it also has one extra property, source_host
, which can be used to determine if the data was from the Live or Legacy CAPI endpoint host. See PLUGINS.md for more details.config.get_int('theme')
, then be aware that we've finally moved from hard-coded values to actual defined constants. Example use would be as in:from config import config
from theme import theme
active_theme = config.get_int('theme')
if active_theme == theme.THEME_DARK:
...
elif active_theme == theme.THEME_TRANSPARENT:
...
elif active_theme == theme.THEME_DEFAULT:
...
else:
...
NavRoute.json
will now be loaded during 'catch-up' when EDMarketConnector is (re-)started. The synthetic StartUp
(note the capitalisation) event that is emitted after the catch-up ends will have state['NavRoute']
containing this data.Fileheader
event from detecting a subsequent new Journal file will blank this data again. Thus, if you're interested in "last plotted route" on startup you should react to the StartUp
event. Also, note that the contents will indicate a NavRouteClear
if that was the last such event.develop
branch, please don't. Whilst we try to ensure that any code merged into this branch doesn't contain bugs, it hasn't at that point undergone more thorough testing. Please use the stable
branch unless otherwise directed.edmc_data
as a part of reviewing the latest update to coriolis-data
.edmc_data
up to date.