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.
Hello @naten11, it sounds like you have upgraded Cura from quite an old version because for some time now the behaviour has changed to what it does now. i.e. it always starts the layer at the same location irrespective of where the previous layer finished. It now behaves this way because the gcode for the the layers is computed concurrently rather than sequentially so it doesn't know where the last layer finished when computing the gcode for the next layer.
Thanks for the information @smartavionics! So is this behavior automatically added once the gcode is compiled and unable to be turned off? Would downloading a previous version be the only way?
In the Cura 5.8 stable release, everyone can now tune their Z seams to look better than ever. Method series users get access to new material profiles, and the base Method model now has a printer profile, meaning the whole Method series is now supported in Cura!
We are happy to announce the next evolution in the UltiMaker 3D printer lineup: the UltiMaker Factor 4 industrial-grade 3D printer, designed to take manufacturing to new levels of efficiency and reliability. Factor 4 is an end-to-end 3D printing solution for light industrial applications
Recommended Posts
burtoogle 516
Hello @naten11, it sounds like you have upgraded Cura from quite an old version because for some time now the behaviour has changed to what it does now. i.e. it always starts the layer at the same location irrespective of where the previous layer finished. It now behaves this way because the gcode for the the layers is computed concurrently rather than sequentially so it doesn't know where the last layer finished when computing the gcode for the next layer.
Link to post
Share on other sites
naten11 0
Thanks for the information @smartavionics! So is this behavior automatically added once the gcode is compiled and unable to be turned off? Would downloading a previous version be the only way?
Link to post
Share on other sites