Cura 2.3: GUI Bug?

[Gnevko 5]

Hi!

I have some strange behavior on the GUI. I have changed "Infill Overlap Percentage" from the default value (10%) to 15% and saved in my profile. After some experiments I changed the value back to 10%. Now habe have to messages:

if I press "i", the field value is still 10%, but now I have an other message

was actually is wrong, because these is no different to my profile value or to the default value.

[DaHai8 74]

Did you save your profile with 10% in it, or is it still set to 15%?

Because you said you changed it to 15%, saved your profile and then set it back to 10%.

But you manually set it back to 10, so it was not calculated - hence the 'i'.

If you saved your profile at this point, you save it as a manually entered 10 and not a calculated 10.

When you clicked the 'i' it calculated the field to 10, but that doesn't match your profile, because its still set to 15 (or a manually set 10).

So now you get an 'undo' arrow because 10 does not match your saved profile data.

Save your profile now with 10 as the calculated field and all should be good.

Manually set fields, even if they are currently the same as a calculated value, will not change when other fields that can affect it change. So even if manually set 10 is the same as calculated 10, you will always get a warning because Cura can't adjust it automatically.

Edited September 5, 2016 by Guest

[Gnevko 5]

DaHai8, thank you for the explanation!

Other strange Cura's 2.3 behavior on MAC OS X: sometimes Cura starts with "New Machine Assistant" and without my already added Printer. It really a little bit confusing because I need to change the Start/End GCode part each time it happens.

Maybe you know how to solve this problem?

[nallath 1,124]

If it starts with new machine assistant, it probably failed to load your old active printer, notices that you don't have an active printer so it tries to add one.

Could you give me your .log files saved by Cura. There should be some errors there that show what is going wrong.

For the rest, DaHai8 is right on all accounts

[Gnevko 5]

Hi,

how can I send you the log file (I found it )?

And now I can reproduce this bag: just create or update a profile, close Cura Application, open Cura again - that's it - "Add new printer" window.

2016-09-05 20:47:19,182 - WARNING - UM/Settings/ContainerRegistry.pyc (load [188]): Could not determine container type for file /Users/Alex/.cura/machine_instances/Ultimaker+Original.cfg, ignoring

2016-09-05 20:47:19,183 - WARNING - UM/Settings/ContainerRegistry.pyc (load [188]): Could not determine container type for file /Users/Alex/.cura/machine_instances/Ultimaker+Original%2B+%232.cfg, ignoring

2016-09-05 20:47:19,578 - DEBUG - .../cura/plugins/MachineSettingsAction/MachineSettingsAction.py (_onContainerAdded [40]): Not attaching MachineSettingsAction to ultimaker_original_dual; Multi-extrusion printers are not supported

2016-09-05 20:47:19,974 - DEBUG - .../cura/plugins/MachineSettingsAction/MachineSettingsAction.py (_onContainerAdded [40]): Not attaching MachineSettingsAction to ultimaker2_extended_plus; Machines that use variants are not supported

2016-09-05 20:47:20,107 - DEBUG - .../cura/plugins/MachineSettingsAction/MachineSettingsAction.py (_onContainerAdded [40]): Not attaching MachineSettingsAction to ultimaker2_plus; Machines that use variants are not supported

2016-09-05 20:47:25,465 - ERROR - UM/Logger.pyc (logException [53]): Exception: Could not deserialize container Ultimaker Original+

2016-09-05 20:47:25,465 - ERROR - UM/Logger.pyc (logException [53]): Traceback (most recent call last):

2016-09-05 20:47:25,465 - ERROR - UM/Logger.pyc (logException [53]): File "UM/Settings/ContainerRegistry.pyc", line 238, in load

2016-09-05 20:47:25,465 - ERROR - UM/Logger.pyc (logException [53]): File "UM/Settings/ContainerStack.pyc", line 252, in deserialize

2016-09-05 20:47:25,466 - ERROR - UM/Logger.pyc (logException [53]): Exception: When trying to deserialize, we received an unknown ID (ultimaker original+_normal quality 0) for container

Edited September 5, 2016 by Guest

[Gnevko 5]

And of course something like this (just right now)

Edited September 5, 2016 by Guest

[nallath 1,124]

It tries to load a profile that it can't find. By the look of it you also had 2.1 installed. We've found some issues with the 2.1 conversion scripts, so clearing your local files will already help quite a bit.

[Gnevko 5]

Yes, at first I installed Cura 2.1.3, then I deinstall it and installed Cura 2.3 ... and as a typical user I assume it should just work without something need to be clearing or some other magic staff.

Edited September 6, 2016 by Guest

[nallath 1,124]

as a typical user I assume it should just work without something need to be clearing or some other magic staff.

 

You're right, but this is a beta. If you want stable software, don't get the beta

[Gnevko 5]

I undersend this and I hope the release version come soon and without such bugs. Because of that I use betta version and post some bugs I found.

[Gnevko 5]

Let's continue

1) I selected "White" color, but the name was not changed - is still Generic.

2) Diameter in "mm3" - strange ...

[Gnevko 5]

It tries to load a profile that it can't find. By the look of it you also had 2.1 installed. We've found some issues with the 2.1 conversion scripts, so clearing your local files will already help quite a bit.

 

I deleted all related folder which a could find and reinstall Cura 2.30 ... the problem is still exists (as soon I add and select new profile and close Cura) :(

[nallath 1,124]

1) I selected "White" color, but the name was not changed - is still Generic.

2) Diameter in "mm3" - strange ...

 

Materials is still quite messed up. It's a know issue.