Jump to content
Ultimaker Community of 3D Printing Experts

Cura 2.4 release bug


Recommended Posts

Posted · Cura 2.4 release bug

This worked in 2.3and 15.n and 14.n, did I use 13.n, think so, but does not work in2.4

When you create a customised printer definition and enter in all the settings and start/end gcode it is all saved.

If you modify any of the settings they are saved

BUT if you modify the start gcode the changes are NOT saved and so do not appear in the generated gcode

  • Link to post
    Share on other sites
    Posted · Cura 2.4 release bug

    I can't reproduce the problem. Just created a new printer and then edited it and added the word "hello" to the start gcode. If I slice something, I see:

     

    ;FLAVOR:RepRap;TIME:1482;Filament used: 0.331544m;Layer height: 0.1;Generated with Cura_SteamEngine 2.4.0M104 S205M109 S205G28 ;HomeG1 Z15.0 F6000 ;Move the platform down 15mm;Prime the extruderG92 E0G1 F200 E3G92 E0hello

     

  • Link to post
    Share on other sites
    Posted · Cura 2.4 release bug

    Are you using "Other" printers (I think, I do not have Cura on this laptop) which has a list of 3rd party printers OR are you using "Customised" printers and creating one from nothing? My problem is with "Customised" printers.

  • Link to post
    Share on other sites
    Posted · Cura 2.4 release bug

    I have a couple of questions:

    * What exactly are you changing in the gcode? Note that lines that start with a ; probably don't save, but that should not affect printing.

    * Have you tried if this still reproduces with Cura 2.5?

    * Can you try with a clean configuration (ie rename the appdata\local\cura folder to appdata\local\cura.bak so a new configuration is created)? I ask this not as a solution, but just to know if it may have something to do with your specific configuration folder.

  • Link to post
    Share on other sites
    Posted · Cura 2.4 release bug

    I have just upgraded 2.4 to 2.6.1 and this problem has been fixed, allowing customised printer start/end gcode to be amended :)

  • 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!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
    ×
    ×
    • Create New...