4.5: No reslice option after changing settings

[mechamecha 64]

Just started using Cura 4.5 after sticking with 4.1 for quite a while because of an issue with supports missing on bottom layers. (@burtoogle was kind enough to figure out a workaround in this thread.) However, I've discovered a couple of other strange issues:

 

1) After slicing, then changing certain settings (e.g. roof support settings), the "preview" and "save to file" options continue to remain visible with no option to reslice. In order to reslice, I have to change an unrelated setting, then reset it back to its original value.

 

2) When switching between printers (UM3 and UM2 in my case), sometimes settings will mysteriously vanish. To get them to reappear, I'll have to restart Cura. Or I can go into settings and individually deselect, then reselect them. (These aren't printer specific settings that are supposed to disappear; they're settings that should be there, like support settings, for example.)

 

3) With UM2, start gcode does the expected nozzle purge, but then drops the nozzle straight down into the purged filament before moving over to start printing, causing it to drag the whole mess into the print. I don't think this is a firmware issue with the UM2, because Cura 4.1 didn't cause this to happen.

Edited March 23, 2020 by mechamecha
Added issue #3

[nallath 1,124]

14 hours ago, mechamecha said:

1) After slicing, then changing certain settings (e.g. roof support settings), the "preview" and "save to file" options continue to remain visible with no option to reslice. In order to reslice, I have to change an unrelated setting, then reset it back to its original value.

 

2) When switching between printers (UM3 and UM2 in my case), sometimes settings will mysteriously vanish. To get them to reappear, I'll have to restart Cura. Or I can go into settings and individually deselect, then reselect them. (These aren't printer specific settings that are supposed to disappear; they're settings that should be there, like support settings, for example.)

These two are related I think. They should be fixed for 4.6

Also, for the next time, could you report issues (and each of them in their own report) on github? That makes it a lot easier for us to keep track of things.

[mechamecha 64]

Thank you, nallath. OK, I'll do github in the future.