Welcome to Ultimaker Cura 3.2 | Stable

[SandervG 1,521]

11 minutes ago, ahoeben said:

including all carefully made profiles a user may have

 

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? 

[Msuurmond 28]

6 minutes ago, hi5 said:

hi 

 

I tested the cura.exe (3.2.1) on the virustotal and indicated it. why is it unsafe?

You should ask 'Cylance'. Unfortunately some virusscanners give a false positive on Cura. 

[Msuurmond 28]

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.

[ahoeben 1,948]

47 minutes ago, Msuurmond said:

 

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.

 

There are no instructions on how to do this though, or where even to find this zip. And because the folder is zipped, the user can't even import the profile files one by one without unzipping the archive first.

 

I don't think it is bad that there is now an option to at least get a working Cura again, and I certainly don't have a magic solution that gets Cura in a working condition with the configuration intact. But realise that the current solution comes at a steep price: having to start over. It would be good if there were some sort of a "configuration doctor" wizard that would detect problems with specific files instead of a single "one button fits all" solution, but creating and testing that would take a lot of resources.

[ahoeben 1,948]

4 hours ago, SandervG said:

@ahoeben, I believe this video was made before you informed us that we overlooked your (indeed) valuable contribution of mesh types.

 

I first mentioned the missing features in the overview on January 23rd, and this video was not posted until yesterday. But I did notice that the video was made with the beta, not the release version. Oh, and I do like the fact that this video was made in the first place, and appreciate the effort that went into making it. It could have been more though...

 

Sure, I'll be happy to give my feedback on a script for a future release video, or even a document that goes from Cura dev to marketing to point out missing or unclear changes and additions to Cura.

[Brulti 177]

Maybe have Cura save the configuration in a 'Cura.old' file, like Windows does? Then you can just import your custom configurations fils one by one, until you find out which one is bugged?

 

I would also be very interested in seeing videos listing all the new features, and maybe major bug fixes. As was mentioned above, what is not shown or told about in those videos often go overlooked.

[ultiarjan 1,223]

21 hours ago, SandervG said:

For the snappy quick overview of new features, doesn't the blog, forum post and release notes suffice? The purpose of the video would be to explain more in depth (and also show) what features can do and how they work with some more background knowledge and context. 

 

Sure, ok there's no real need for the quick short video apart form marketing...

 

But the in depth teaching video's on features would be better imo if they would only contain one feature, shorter, and easy to refer to in case you want to explain something.

[ultiarjan 1,223]

4 hours ago, SandervG said:

I thought these would be preserved, I asked for our dear modified mark-2 users.

 

Nope... I've lost count on how many times I reinstalled Mark2 files...have not bothered yet on Cura3.2

 

[nilrog 103]

8 hours ago, SandervG said:

At one point a screenshot was shared with 'Backup and reset configuration', this should have prompted Cura to remove all third party machine profiles and reload them according to the latest profiles. Supposedly, this should have fixed it. So, if someone runs into a similar issue, please give this a try  

5 hours ago, ahoeben said:

 

This likely would have fixed the problem, though it is a lot like "throwing out the baby with the bathwater". It is a (drastic) workaround, not a solution.

 

This prompt was shown in my face when I had downloaded Cura 3.2 and launched it the second time...because it crashed at first startup.

At this point I had no custom profiles etc...but if I had...it sure is a drastic way to adress issues with the app...

[nilrog 103]

5 hours ago, Msuurmond said:

 

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.

 

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 

[Msuurmond 28]

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 

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.

[SandervG 1,521]

1 hour ago, ultiarjan said:

But the in depth teaching video's on features would be better imo if they would only contain one feature, shorter, and easy to refer to in case you want to explain something.

The video could also be cut up in smaller sections, few minutes per feature. This requires more time to edit it all, but I'll suggest it. Perhaps like an agenda which features are being covered before you watch it could also help. 

 

1 hour ago, ultiarjan said:

Nope... I've lost count on how many times I reinstalled Mark2 files...have not bothered yet on Cura3.2

 

one the user end I hear this more often than I would want, on the Ultimaker side I usually hear it shouldn't happen anymore. @Msuurmond, any idea why the experiences are so far apart?

 

[Msuurmond 28]

2 minutes ago, SandervG said:

one the user end I hear this more often than I would want, on the Ultimaker side I usually hear it shouldn't happen anymore. @Msuurmond, any idea why the experiences are so far apart?

 

@ultiarjan can you send me the config files reinstall each time?

[RoboDLC 1]

On 2/13/2018 at 3:30 AM, Msuurmond said:

**Update: Could you try this version: https://stack.mybacklog.info/s/LDltcUP2BXur7AZ

I can't reach anything at this link.  I don't have a login there.

 

Thanks,

DLC

[nilrog 103]

This...

11 hours ago, Msuurmond said:

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

 

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

[Msuurmond 28]

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>

[ahoeben 1,948]

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.

[Brulti 177]

I second the link.

[Msuurmond 28]

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'

[ahoeben 1,948]

Need me to do a PR?

[Msuurmond 28]

Yes please!

[ahoeben 1,948]

I am looking in to it.

[ahoeben 1,948]

See https://github.com/Ultimaker/Cura/pull/3325

[Msuurmond 28]

50 minutes ago, ahoeben said:

See https://github.com/Ultimaker/Cura/pull/3325

Nice, will test and merge tomorrow morning.

[nilrog 103]

17 hours ago, Msuurmond said:

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>

 

Yes, a better text with a working link to the configuration folder is a lot better.

 

But, if Cura already crashed/failed to use the old configuration...what will happen when the user starts putting back that same "bad" configuration?