{"action":"opened","issue":{"url":"https://api.github.com/repos/MatterHackers/MatterControl/issues/807","repository_url":"https://api.github.com/repos/MatterHackers/MatterControl","labels_url":"https://api.github.com/repos/MatterHackers/MatterControl/issues/807/labels{/name}","comments_url":"https://api.github.com/repos/MatterHackers/MatterControl/issues/807/comments","events_url":"https://api.github.com/repos/MatterHackers/MatterControl/issues/807/events","html_url":"https://github.com/MatterHackers/MatterControl/issues/807","id":157089775,"number":807,"title":"MatterControl Slice Settings export is not the same as MatterSlice config files","user":{"login":"larsbrubaker","id":1158332,"avatar_url":"https://avatars.githubusercontent.com/u/1158332?v=3","gravatar_id":"","url":"https://api.github.com/users/larsbrubaker","html_url":"https://github.com/larsbrubaker","followers_url":"https://api.github.com/users/larsbrubaker/followers","following_url":"https://api.github.com/users/larsbrubaker/following{/other_user}","gists_url":"https://api.github.com/users/larsbrubaker/gists{/gist_id}","starred_url":"https://api.github.com/users/larsbrubaker/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/larsbrubaker/subscriptions","organizations_url":"https://api.github.com/users/larsbrubaker/orgs","repos_url":"https://api.github.com/users/larsbrubaker/repos","events_url":"https://api.github.com/users/larsbrubaker/events{/privacy}","received_events_url":"https://api.github.com/users/larsbrubaker/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-05-26T22:06:00Z","updated_at":"2016-05-26T22:06:00Z","closed_at":null,"body":"@dattas commented on [Fri Jan 16 2015](https://github.com/MatterHackers/MatterSlice/issues/5)\n\nHello,\r\n\r\nI've written an OctoPrint plugin that will allow users to use MatterSlice with OctoPrint. I've run into an issue where if I export Slice Settings from MatterControl, then try to use that file with -c with MatterSlice, the values don't match up and thus the slice settings are not useful in this instance. Are there plans to either change the settings to be the same values as the slice settings from MatterControl or perhaps a flag to indicate the settings are from MatterControl via a --from-mattercontrol/-mc or something similar?\r\n\r\nShould I post this on MatterControl's repo instead?\r\n\r\nThanks!\n\n---\n\n@larsbrubaker commented on [Mon Jan 19 2015](https://github.com/MatterHackers/MatterSlice/issues/5#issuecomment-70535508)\n\n@dattas \r\n\r\nSo you are running into some very interesting legacy behavior. We started slicing in MatterControl with Slic3r, and our internal settings in the database and therefore the settings files, are all slic3r or slic3r styled. The settings that MatterSlice uses are are translated before being written to the config file. You can find the settings that were sent to MatterSlice in C:\\Users\\[username]\\AppData\\Local\\MatterControl\\data\\gcode on windows. You can also find them in the gcode output at the end of the file. You would just need to remove the \"; \" from the start of each line.\n\n---\n\n@dattas commented on [Mon Jan 19 2015](https://github.com/MatterHackers/MatterSlice/issues/5#issuecomment-70539319)\n\n@larsbrubaker Thanks for the work around on finding that config. Any plans to make this available via a dropdown or something similar? I don't think people will like having to hunt for the config file or parse it out of a sliced file if they want to use MatterSlice outside of MatterControl\n\n---\n\n@larsbrubaker commented on [Thu May 26 2016](https://github.com/MatterHackers/MatterSlice/issues/5#issuecomment-222008053)\n\nYes, we will add this to our road map.\n\n"}}
{"actor":{"display_login":"larsbrubaker"}}