{"action":"created","issue":{"url":"https://api.github.com/repos/prusa3d/Slic3r/issues/24","repository_url":"https://api.github.com/repos/prusa3d/Slic3r","labels_url":"https://api.github.com/repos/prusa3d/Slic3r/issues/24/labels{/name}","comments_url":"https://api.github.com/repos/prusa3d/Slic3r/issues/24/comments","events_url":"https://api.github.com/repos/prusa3d/Slic3r/issues/24/events","html_url":"https://github.com/prusa3d/Slic3r/issues/24","id":187973047,"number":24,"title":"[Request] Fix and enable Arc feature","user":{"login":"CReimer","id":1853907,"avatar_url":"https://avatars.githubusercontent.com/u/1853907?v=3","gravatar_id":"","url":"https://api.github.com/users/CReimer","html_url":"https://github.com/CReimer","followers_url":"https://api.github.com/users/CReimer/followers","following_url":"https://api.github.com/users/CReimer/following{/other_user}","gists_url":"https://api.github.com/users/CReimer/gists{/gist_id}","starred_url":"https://api.github.com/users/CReimer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/CReimer/subscriptions","organizations_url":"https://api.github.com/users/CReimer/orgs","repos_url":"https://api.github.com/users/CReimer/repos","events_url":"https://api.github.com/users/CReimer/events{/privacy}","received_events_url":"https://api.github.com/users/CReimer/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-11-08T11:55:03Z","updated_at":"2016-11-08T16:20:04Z","closed_at":null,"body":"There's already some code in Slic3r to generate Arc commands (G2, G3). Either it was never finished in the first place or it got broken over time.\r\n\r\nI was able to reenable it by adapting it to some more recent changes in Slic3r, but the generated GCode is completely wrong.\r\n"},"comment":{"url":"https://api.github.com/repos/prusa3d/Slic3r/issues/comments/259182642","html_url":"https://github.com/prusa3d/Slic3r/issues/24#issuecomment-259182642","issue_url":"https://api.github.com/repos/prusa3d/Slic3r/issues/24","id":259182642,"user":{"login":"Sebastianv650","id":10776877,"avatar_url":"https://avatars.githubusercontent.com/u/10776877?v=3","gravatar_id":"","url":"https://api.github.com/users/Sebastianv650","html_url":"https://github.com/Sebastianv650","followers_url":"https://api.github.com/users/Sebastianv650/followers","following_url":"https://api.github.com/users/Sebastianv650/following{/other_user}","gists_url":"https://api.github.com/users/Sebastianv650/gists{/gist_id}","starred_url":"https://api.github.com/users/Sebastianv650/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Sebastianv650/subscriptions","organizations_url":"https://api.github.com/users/Sebastianv650/orgs","repos_url":"https://api.github.com/users/Sebastianv650/repos","events_url":"https://api.github.com/users/Sebastianv650/events{/privacy}","received_events_url":"https://api.github.com/users/Sebastianv650/received_events","type":"User","site_admin":false},"created_at":"2016-11-08T16:20:04Z","updated_at":"2016-11-08T16:20:04Z","body":"I'm also no friend of G2 and G3. First, the Slicer has to find an approximation to fit arcs into the model. Second, the already quite overloaded 16MHz Marlin board has to approximate the circle further by breaking it up into small G0/1 moves at a resolution that has to be defined by the user in the config file first.\r\nSo you are not flexible for choosing a resolution as you can do it in Slic3r, and you transfer the calculations to the weaker CPU."}}
{"actor":{"display_login":"Sebastianv650"}}