-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doesn't work since update cura 5.3.0 #24
Comments
As I don't have any special issue, I don"t think it's a problem with the 5.3 release. But without any other information it will be hard to analyse your problem |
I just installed this plugin for the first time so I'm unaware if it a Cura 5.3 issue (I'm using 5.3.1), but I found that if Build Plate Adhesion Type is set to None, the first layer of tabs will not generate at all, but subsequent layers will. Basically, you must at least have some form of build plate adhesion for the first layer of tabs to be present. I usually don't use a skirt because I have pre-extrusion start Gcode, but I set mine to 1 skirt line at distance 1mm which now generates the 1st layer of tabs. Just wanted to let this be known because I was scratching my head at this for half an hour. I was unaware of the skirt requirement because I didn't see it in the plugin documentation anywhere (and there are screenshots showing no skirt present). @5axes could you add this as a note in the documentation? (I apologize if it is present and I missed it). |
This is a known cura bug that doesn't just affect custom supports. The problem comes from the "Enable Support Brim" option for supports, which must not be activated if you don't use any "Build Plate Adhesion Types". You can find this bug here: Unfortunately, although the problem has existed since the first Beta versions of 5.3 and ultimaker is now starting 5.5 Alpha, they haven't seen necessar to correct the problem. |
it works in 5.6 now |
unfortunately , my favorite extension doesn't work anymore since the last update. I hope a correction coming soon!
The text was updated successfully, but these errors were encountered: