On 3/8/2023 at 3:27 PM, Cuq said:Most of the times you can just "Disable affected profiles" it's not a perfect solution but it's still better than "Reset" : the kill button
I’m quite sure, there was no “Disable affected profiles” option.
On 3/8/2023 at 3:27 PM, Cuq said:Most of the times you can just "Disable affected profiles" it's not a perfect solution but it's still better than "Reset" : the kill button
I’m quite sure, there was no “Disable affected profiles” option.
Yes, that can be a problematic dialog. I know that some users don't even think about it and just select OK and have the stuff deleted. I did that myself the first time but now I just close the dialog and begin to search for the problem. Often it is due to a recent change that was made (manually editing files) and by reverting the change the error goes away. A more prominent Cancel button may help for some here but the rather limited return information does not help people who are not aware of what they might have done to cause the issue. It would be nice if other information was given such as the file name where the conflict arose etc. but that may not be possible.
22 hours ago, esopalumpa said:I’m quite sure, there was no “Disable affected profiles” option.
That option is only available if you have the "Startup optimiser" plugin installed.
Thank you for this clarification. I thought this was a basic feature of Cura.
One of the drawbacks of some plugins : so essential, they should be integrate as standard in Cura.
Edited by Cuq6 hours ago, ahoeben said:That option is only available if you have the "Startup optimiser" plugin installed.
Thanky you. I have just installed the plugin. I agree with Cuq that some of these plugins should be enabled by default.
Recommended Posts
Cuq 206
Most of the times you can just "Disable affected profiles" it's not a perfect solution but it's still better than "Reset" : the kill button
Link to post
Share on other sites