-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import from ED: Market Connector not retrieving new engineer data correctly #28
Comments
The text file supplied is actually the raw data from the Frontier API, which is why it works in both Coriolis and ED:Shipyard. You can import this into Coriolis through the 'Import' option in the settings menu. I suspect that EDMC will be updated to provide the detailed export for Coriolis with modifications at some stage, although in general it appears that tools are moving towards using the Frontier format so EDMC might deprecate the use of the custom Coriolis export. Either way, use the text file for now until EDMC is updated. |
The old Coriolis import format (the .json file) doesn't support mods. E:D Shipyard and Coriolis now share the same data format for importing (the .txt file - a subset of the Companion API output) so the next version of EDMC will only export this format. |
Not sure if I'm missing something. I just saved the raw data for my Beluga Liner. Note that I'm not docked at any station. I copied the entire raw text and tried to import it into Coriolis. When I pasted it, I got the "Cannot parse the data". I can't proceed any further. I used the main Import under the Settings menu. |
@nemesyssoft please can you attach the file here so that we can take a look at it? |
Please could you also confirm that you are using https://coriolis.edcd.io/ and that the version number at the bottom right of the main screen is 2.2.2? |
Fixed as part of 2.2.3 release. |
EDMC exports a .json for Coriolis, and a .txt for ED:Shipyard.
The .json file doesn't seem to correctly show all the engineered components, while the .txt file does, which seems the wrong way round.
Ship Spec Exports.zip
The text was updated successfully, but these errors were encountered: