Jump to content

Cura3.1 Unable to save gcode: 'Scene' object has no attribute 'gcode_list'


MakerJ

Recommended Posts

Posted · Cura3.1 Unable to save gcode: 'Scene' object has no attribute 'gcode_list'

Hello,

I just installed Cura 3.1 and all attempts to slice and save a gcode file have unsuccessful. I am not sure how to resolve this. I've tried with many simple files. The error is:

 

Could not save... 'Scene' object has no attribute 'gcode_list'

 

Thanks!

  • Link to post
    Share on other sites

    Posted · Cura3.1 Unable to save gcode: 'Scene' object has no attribute 'gcode_list'

    G-code list is new in Cura 3.2. Are you using a plugin in 3.1 that's intended for 3.2? (for example the OctoPrint version that was moved to the plugin browser?).

  • Link to post
    Share on other sites

    Posted · Cura3.1 Unable to save gcode: 'Scene' object has no attribute 'gcode_list'
    2 hours ago, ctbeke said:

    G-code list is new in Cura 3.2. Are you using a plugin in 3.1 that's intended for 3.2? (for example the OctoPrint version that was moved to the plugin browser?).

     

    Thanks for the suggestion. This is an out of the box install. I haven't installed any additional plugins aside from what already comes installed. That being said, looking at the list of plugins that comes pre-installed, they are all enabled(box is checked). 

  • Link to post
    Share on other sites

    Posted · Cura3.1 Unable to save gcode: 'Scene' object has no attribute 'gcode_list'
    9 hours ago, ctbeke said:

    G-code list is new in Cura 3.2.

    No it is not.

     

    gcode_list is what it was until Cura 3.2. In Cura 3.2 it was refactored to gcode_dict (to support multiple buildplates)

  • Link to post
    Share on other sites

    Posted · Cura3.1 Unable to save gcode: 'Scene' object has no attribute 'gcode_list'

    Omg you're totally right, it's the other way around. My bad, brainfart.

     

    So it tries to access the G-code before it's generated (or correctly stored in the Scene). I'm not sure why though...

  • Link to post
    Share on other sites

    Posted · Cura3.1 Unable to save gcode: 'Scene' object has no attribute 'gcode_list'

    Unable to save gcode: 'Scene' object has no attribute 'gcode_list':  It does that when the project is not yet sliced.

  • Link to post
    Share on other sites

    Posted · Cura3.1 Unable to save gcode: 'Scene' object has no attribute 'gcode_list'
    3 hours ago, DSX76 said:

    Unable to save gcode: 'Scene' object has no attribute 'gcode_list':  It does that when the project is not yet sliced.

     

    Doh.....I feel like an idiot now. 

     

     

  • Link to post
    Share on other sites

    Posted · Cura3.1 Unable to save gcode: 'Scene' object has no attribute 'gcode_list'

    You shouldn't be able to click "save" or "print" though when it's not sliced.

  • Link to post
    Share on other sites

    Posted · Cura3.1 Unable to save gcode: 'Scene' object has no attribute 'gcode_list'
    28 minutes ago, ctbeke said:

    You shouldn't be able to click "save" or "print" though when it's not sliced.

    No, not with the dedicated button; that will say 'Prepare'. But you can (at least try to) save it from the menu 'File -> Save As...' and select either *.gcode or *.stl, which obviously will result in this error message. 

  • Link to post
    Share on other sites

    Posted · Cura3.1 Unable to save gcode: 'Scene' object has no attribute 'gcode_list'
    40 minutes ago, ctbeke said:

    You shouldn't be able to click "save" or "print" though when it's not sliced.

     

    It was totally operator error on my part. To reproduce the issue, I just simply load the .stl file, then go to Save As and select .gcode as the Save as Type. I wasn't actually clicking on Prepare to initiate the slicing. :facepalm:

  • Link to post
    Share on other sites

    Posted · Cura3.1 Unable to save gcode: 'Scene' object has no attribute 'gcode_list'

    There's a point to be made about not having gcode (or other sliced output) as an output option in Save As. Save As... and saving the sliced output should be separated, because they are two quite different things.

  • 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
    • Our picks

      • UltiMaker Cura 5.7 stable released
        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. 
         
          • Like
        • 18 replies
      • S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
        (Sorry, was out of office when this released)

        This update is for...
        All UltiMaker S series  
        New features
         
        Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
          • Like
        • 0 replies
    ×
    ×
    • Create New...