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?
We don't often release an alpha version of Ultimaker Cura... So what's different this time? This Alpha contains such a huge slicing engine overhaul that we really need your help!
We wish to celebrate and honor the innovators that push forward the field, technology and world. We opted to not present it as a competition or ranked list. Every innovator has earned his spot on that list in their own way. We also look at the 3D printing industry as a whole and not limit the list to those only using Ultimaker.
Recommended Posts
burtoogle 495
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