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.
Post that gcode file and someone will take a look. You could open the Gcode file in Cura and see how it looks as well. Cura uses a separate program to read in a gcode file so it wouldn't involve the slicer side.
4.9 seems to be having issues, but this sort of thing isn't one of them. (Of course you could always be the first!)
Have you tried any other prints from earlier gcode files since you noted the problem?
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!
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
Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more.
Recommended Posts
GregValiant 1,287
Post that gcode file and someone will take a look. You could open the Gcode file in Cura and see how it looks as well. Cura uses a separate program to read in a gcode file so it wouldn't involve the slicer side.
4.9 seems to be having issues, but this sort of thing isn't one of them. (Of course you could always be the first!)
Have you tried any other prints from earlier gcode files since you noted the problem?
Link to post
Share on other sites