I wanted to change the print settings in a custom settings called “#A350 Fast”. I clicked the settings icon to bring up the settings page, selected #A350 Fast, and changed the infill from 33% to 15%, and checked the “Generate Auto Support” box. When I go back out and select that profile, it still shows 33% and “No supports”. I create the GCode anyway, but it is applying 33% infill and not creating any supports. I don’t want to have create a new profile every time I change one parameter (like using supports) and end up with a massive list.
Hi Jerry,
Can you share a video of the issue that you met? So I can know which step that you are stuck in.
I shared a video here and I hope it can help you. Loom | Free Screen & Video Recording Software
Tracy,
I’ve attached a video of the issue I’m having. I select #A350-Fast Print and make changes to the Infill and Supports, then select it, but I still have the A350-fast settings being applied. When I go back in, and the changes I made to #A350 are still there, but when I select it again, I still get the A350 profile.
Jerry
Issue Applying Printing Settings.mp4 (1.15 MB)
Hi Jerry, thanks for the video. From the video, you did nothing change for #A350-Fast Print.
-
From second 1-4, you checked the #A350-Fast Print settings under the “show details”.
-
From second 5-24, you clicked on the gear icon and changed the Infill Density from 33% to 25%, and enabled the Generate auto support.
-
From second 29-30, you checked #A350-Fast Print under the “show details”.
-
From second 31-40, you clicked the gear icon and went to change the settings of A350-Fast Print
-
Finally, you generated the gcode for A350-Fast Print.
So in fact, you did not select #A350-Fast Print and make changes, but select A350-Fast Print and make changes.
Tracy,
Please watch this again. I have redone the video and only make changes to the #A350 profile, and will point only to that one at the end, instead of trying to show that the A350 was the one still being displayed. You will see, I select the #A350 Fast, show that the profile does not match what is being displayed. After I make changes to Infill and Supports, I hit Select and point to the #A350 Fast Print, but the profile still shows 33% infill and no auto support.
I hope this video makes the problem clear.
Jerry
#A350 Profile Not Saving.mp4 (1.25 MB)
Tracy,
Please watch this again. I have redone the video and only make changes to the #A350 profile, and will point only to that one at the end, instead of trying to show that the A350 was the one still being displayed. You will see, I select the #A350 Fast, show that the profile does not match what is being displayed. After I make changes to Infill and Supports, I hit select and point to the #A350 Fast Print, but the profile still shows 33% infill and no auto support.
I hope this video makes the problem clear.
Jerry
#A350 Profile Not Saving.mp4 (1.25 MB)
Thank you, Jerry, it is clear now.
I did not reproduce the issue on my computer. Can you go to settings and reset the Luban settings and try again?
I don’t have the problem anymore, but I also don’t have any material profiles except a PLA and an ABS. I didn’t realize it was going to erase everything user-created. I’d not done a reset before.
I have the same issue. I duplicate and delete the “bad” setting, but even the new duped one, can’t update any changes. I found once you have a bad setting like that, you have to start over from one of the built-in settings. Very annoying. Almost without fail, every setting will get “corrupt” eventually, an due unable to save changes.
Hi Jerry, that is good that the issue is gone.
I am sorry to tell you that if you click on the Reset all user settings, the Luban will go back to the original settings by default.
Hi @snapUser Thanks for the feedback. I have reported it to the software team.
It’s almost as if the profile is locked and can’t save further changes. But I have opened the json files and they appear fine, they just aren’t being updated/saved after parameters are changed.
Thanks, we will try to reproduce the issue first on our end.
Thank you. I thought afterwards, maybe I shouldn’t have posted my observation, as I don’t want to send your engineers down the wrong path. But too late now :). Thank you for looking into the issue.