Jump to content

Cura 3.1 Curaslicer has stopped functioning


wrek

Recommended Posts

Posted · Cura 3.1 Curaslicer has stopped functioning

Curamaker 3.1.0

Last night I sliced fine

This morning curamaker started crashing every time it tried slicing the model.

 

I have no idea what has updated or changed since last night. I've tried uninstalling and reinstalling the software.

 

Cura 3.0.4 seems to function fine so I've switched to that.

 

  • Link to post
    Share on other sites

    Posted · Cura 3.1 Curaslicer has stopped functioning

    This is the problem I keep having. The program hangs, it doesn't "crash" so it's not creating any logs that I'm aware of.  Is there a log location that I'm not finding???

    Capture2.PNG

    Capture3.PNG

  • Link to post
    Share on other sites

    Posted · Cura 3.1 Curaslicer has stopped functioning

    Cura creates logs, whether it crashes or not. In Cura go to Help -> Show configuration folder. In the folder that opens, there will be a (large) Cura.log file. That's the log @nallath is talking about.

  • Link to post
    Share on other sites

    Posted · Cura 3.1 Curaslicer has stopped functioning

    Thanks, I was looking for the log location. The windows application logs weren't helpful.  If I get back to 3.1 anytime soon, I'll get those logs but for now I just wanna print ;)

  • Link to post
    Share on other sites

    Posted · Cura 3.1 Curaslicer has stopped functioning

    Sorry for hijacking your thread wrek...

     

    What's the best way to submit logs? Through email, forum, or direct messages?

  • Link to post
    Share on other sites

    Posted · Cura 3.1 Curaslicer has stopped functioning

    Preferably on github, as that's the place where we get all of them, but sending them directly (provided that you also include a proper bug report that includes things like your system, what were you doing, what did yo expect was going to happen, what actually happend)

  • Link to post
    Share on other sites

    Posted · Cura 3.1 Curaslicer has stopped functioning
    On 1/8/2018 at 11:08 PM, wrek said:

     If I get back to 3.1 anytime soon, I'll get those logs but for now I just wanna print ;)

     

    Even if you uninstalled 3.1, you can still get at the logs that it created.

    Open the start menu and start typing %APPDATA%\cura\3.1 (and press enter). The cura.log file is in the folder that opens.

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