Ultimaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.
I would agree that a post-processor is a good idea, tho it obviously avoids 2 rather important issues
1) a lot of people are having problems with getting to any g-code at all - the vast majority of example files I tested for example all had at least one fault - inside-out or non-manifold geometry, flipped normals, self-intersection, infinitely thin planes, etc etc.
2) the ideas are excellent, but creating UI to make it intuitive and easy is.. well, not so easy. there's a matter of designing that which I'd suggest is what this thread tackles first before any code gets written
Link to post
Share on other sites
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Often getting started is the most difficult part of any process. A good start sets you up for success and saves you time and energy that could be spent elsewhere. That is why we have a onboarding course ready for
Ultimaker S5 Pro Bundle, Ultimaker S5, Ultimaker S3 Ultimaker 2+ Connect.
They're ready for you on the Ultimaker Academy platform. All you need to do to gain access is to register your product to gain free access.
Ready? Register your product here in just 60 seconds.
Recommended Posts
alaris2 1
I would agree that a post-processor is a good idea, tho it obviously avoids 2 rather important issues
1) a lot of people are having problems with getting to any g-code at all - the vast majority of example files I tested for example all had at least one fault - inside-out or non-manifold geometry, flipped normals, self-intersection, infinitely thin planes, etc etc.
2) the ideas are excellent, but creating UI to make it intuitive and easy is.. well, not so easy. there's a matter of designing that which I'd suggest is what this thread tackles first before any code gets written
Link to post
Share on other sites