Jump to content

Msuurmond

Dormant
  • Posts

    192
  • Joined

  • Last visited

Posts posted by Msuurmond

  1. 5 hours ago, rebekah_harper said:

    I will sort out the configuration files once I find them.

     

    this log file comes from a post windows reset.  I added the UM2+ first as I run one of them too. But unlike before the rest it also behaved as the UM3 and failed so now both printers fail to work with 3.3

     

     

    It looked like Cura wanted to add a UM3 with a custom material for which it could not fin the profilel. Could that be possible?

    We fixed this in the upcoming stable.

  2. 22 hours ago, rebekah_harper said:

    this should be it.

     

    I just enjoy being part of the process.  

     

    I always run the last full version and a beta. 

    cura.log

    Hi,

     

    From the log files we see there is still a UM2+ loaded, that would indicate the clean install hasn't removed the config folder. Could you try to zip the config folder and share it?

  3. 7 hours ago, rebekah_harper said:

    Well I’m officially miffed. 

    Had to reset my PC which is fine, unrelated to cura.

    so I thought with a clean slate I’d try 3.3 and still shit.  

    Am I the only one with a UM3 where this beta doesn’t work???? 

    No response to my comments or log file. 

     

    Any one have it crash when you add the UM3 printer profile???

    Can you share logfiles?

  4. 9 hours ago, papavomsee said:

    Hello,

     

    Creality CR-10 here.

    Have 3.2.1 installed without problems.

     

    Beta 3.3 crashed instant with my configuration.
    With blank config it will start, selecting CR-10 and Add Printer it will crash :(

    Next start the wizard is back, nothing configured.

     

    If I choose for example Ultimaker 2 it works.

    If i try to add the cr-10 later, it will instant crash again.

    Seems it don't like my cr-10 anymore :(

    Link to cura.log
    https://www.dropbox.com/s/caqdrq9e1eoqszr/cura.log?dl=0

     

     

    Are you using custom profiles/materials? With a clean install of 3.3 I can add a CR-10 without any problems.

  5. 1 hour ago, ahoeben said:

    Make sure to use the same terminology as elsewhere: "Configuration folder" instead of "Cura settings folder". A link to open said folder would be nice.

    I changed the text, but I can't get the link to open the folder (like the same as the 'Help' -> 'Show configuration folder'

  6. 3 hours ago, nilrog said:

    This...

     

    There is a dialog saying that Cura backed up the configuration and reset the configuration...but what and where did it back it up???

    Sure, you, as a developer, know exactly what it did, and how you can recover...but the normal user...does not know what Cura just did...*|

    Hmm, ok, so I have updated the text to include the location, any suggestions to improve it?

    <p><b>A fatal error has occurred.</p></b>
    <p>Unfortunately, Cura encountered an unrecoverable error during start up. It was possibly caused by some incorrect configuration files. We suggest to backup and reset your configuration.</p>
    <p>Your backup can be found in your Cura settings folder.</p>
    <p>Please send us this Crash Report to fix the problem.</p>
    
     
  7. 3 minutes ago, nilrog said:

     

    Well, since this happened to me...I have no clue where this backup is supposedly stored...nor how to restore it...if I had a need to do so.

    Again, much like the adaptive layers, this is a feature implemented with a developer centric mindset...with little to no end-user thought behind it...although the idea is good :+1:

    Thanks that the idea is good, of course it can be improved. But I disagree that there is no end-user though behind it.

     

    What is more user friendly?

    1. Crash during startup, Cura won't boot. User has to search on the forum where to find his/her config folder and needs to delete it manually.

    2. Crash during startup, you get a notification of this and we backup and reset your config folder for you.

     

    We want to go to a state were we will never crash during startup, but there are so many people who manually fiddle in their machine settings that it is very difficult to catch all errors. So for now we catch the crash and help the user. In a next release we might improve this so only crashes on the specific files are catched (for example) and in the mean time we fix the top 10 of the bugs that get reported so we become more robust and crash less.

  8. 2 minutes ago, SandervG said:

     

    I thought these would be preserved, I asked for our dear modified mark-2 users. Let me double check which is it. (could be very well that I'm wrong). Any idea how one could find out what to remove or where to look to find the single part that fixes this crash?

     

    Besides, what did you think of my proposal regarding the next video? 

     

    We create a zip file of the contents before we reset the configuration folder. A user can always restore it and find the file that Cura can't upgrade/parse.

  9. Just now, Julian7 said:

    As a previous commenter said, this may be associated with Retina MacBook Pros. However, no other software has ever had a problem like this on my machine. The previous version of Cura was fine.

     

    Julian

     

     

    I am also running on a MacBook Pro with a retina screen:

    5a82ede353ca7_ScreenShot2018-02-13at14_53_11.thumb.png.7e48915a2ea7c90bcc5b84c1c7ffb3b8.png

×
×
  • Create New...