Hello,
The function "Support - Add/Delete " does not work in the latest version (4.11), nor in version 4.10.1. It is very annoying that such a basic function supported by all other slicers does not work here. This is a sign of a glaring and unacceptable lack on the part of snapmaker. It is time for him to correct this major flaw. If they don’t know how to write a slicer correctly, let them do like everyone else and fork Prussa Slicer or BambuStudio or OrcaSlicer…
What stops you from using a different slicer?
Cura (where Luban is based on) works flawless with the Snapmaker plugin.
The other ones you named are working as well with some modification.
Thank you. I don’t like Cura too much, but if it works perfectly, then I’ll be happy. I’ll look for this plugin. Can you tell me where to find him?
For the other slicers, I tried them, but they do not support the IDEX. I hope the Cura plugin also supports network communication, because it’s important to me.
Install Cura and select any printer you want. This is required for the initial install.
Then go to Marketplace (the button in the upper right corner) and search for “snapmaker”.
Install the plugin and restart the application.
Once it is up again, go to printer management and add printer. Now you can select the printer you have in the selection menu under “Snapmaker”
Depending on your printer (e.g. Artisan) the plugin enables Cura also to upload the GCODE via network.
1 Like
Great, thank-you. I’l try that.
have a nice day.
1 Like
Same, I cannot get this to work. I can only “generate auto support” but it places supports in areas I DO NOT want supports to be placed. When editing delete in an area it does not work either. It removes it from the initial view but selecting preview it is still there.
New Snapmaker user here. Yesterday I was very excited about my new J1S printer working pretty well out of the box, calibration went mostly well…
Then today a total face-palm moment regarding the lack of this basic function when I went to slice my first print. Bleh.
Looking at several comments in this vein I see no movement towards a resolution. Have people given up on getting this to work? Do I really have to go limping back to Cura yet again?? Why people, why?!? Say it ain’t so.
There is a fork of Orca Slicer, I think Luban is not further developed for 3d printing..
Just tried it a few times, no real experience on my side:
If you are familiar with cura or any other slicer I would go with it.
Great, thank you for the suggestion, I’ll give it a go. I’ve attempted to use regular Orca, but I’m having issues figuring out a useable workflow when using two filaments that require different toolhead temps.
My use-case was a strange one; IDEX Duplicate to copy a large print using filaments that required two different temperatures. My original goal was to quickly make two prints of the same non-critical thing and use up some old filament. My long-term goal became to see if it could even be done eventually on the Snapmaker J1s, because what else are weekends for?
I tried different approaches using the startup G-Code in the Cura Snapmaker add-in, Orca Slicer Snapmaker Orca, a greatly simplified startup G-Code and different combinations of the above and the Snapmaker J1 touchscreen options.
I finally ended up going back to Luban for the win. There are a lot of features missing from Luban and getting the supports to work well enough took some experimentation, but I did get it to work. Luban was the only slicer that allowed me to successfully make a copy (an IDEX Mirror print would be the same) using different temperatures for each toolhead.
Wow. We’re a year later, and this bug still isn’t fixed. The UI is there, and lets you choose areas where supports should be or should be excluded, and it even looks right when you see the generated supports, and then you click slice, and it goes back and does whatever the heck it feels like, completely ignoring the user inputs.
Not certain if this occurs in all situations or only when the supports are generated with the other extruder, but this occurs literally every time.
Speaking of dual extruder bugs, the most recent firmware (at least I think I’m up-to-date) is seriously awful.
- Manual z-offset setting fails about half the time, with the next button in the UI not doing anything, and backing out and trying again results in having to set the z-index from the home position unless you power-cycle the printer.
- Filament loading often results in the UI hanging when you tap the button to stop loading (though loading does stop), and if you tap it often enough, the lights go out, and the whole thing resets itself, and at that point, absolutely nothing works, so you have to power-cycle the printer.
All of these things are new after my most recent firmware update, though I update infrequently, so consider that to mean “These are regressions within the last year.”
Snapmaker really needs to get their act together before Creality eats their lunch. In addition to my A350T, I also have a brand new K2 with a pair of CFS units. I can’t get it to print PETG for crap, but for PLA models, it blows the Snapmaker away, both speed-wise and capability-wise (currently set up for auto-switching among 8 filaments, can pre-load a new roll for auto-loading when one runs out (if I’m paying enough attention), etc.
I still love my Snapmaker, because it can do CNC work, which the K2 hopelessly can’t, but I’m pretty sure I’m going to be doing all my drafts on the K2 and switching to the Snapmaker for the final PETG prints. And if Creality ever gets PETG to be usable, my Snapmaker will be relegated to PETG and the occasional “I need to do two prints at once and don’t care if one is really, really slow” situation. 
That said, the true irony is that both Snapmaker and CrealityPrint have not-quite-working support for supports. The latter won’t let you remove supports from the automatically-generated set of supports, so you have to paint everything by hand every time if you don’t want certain areas covered, and it seems to sometimes ignore the minimum area value that should allow you to prevent small areas from being automatically generated. It’s not as much of a mess as Snapmaker Luban’s support, but it is still way buggier than it should be. 
You have to set automated support to none. Then click the “add support” left hand and generate it, now you can remove and add support where you need. Thats how it worked since introduction of that Feature and I used it last week also. Cannot get that point.
I don’t even see anything called “Automated support”. There’s a “Support type”. There’s a button that says “Generate Auto Support (For All)”.
Ah. I see. If you set Support Type to “None”, then it pays attention to the manual supports. Ugh. That’s seriously bad UI design. Instead of “None”, it should at least say “Manual”.
Either way, that mode forces you to deal with standard supports instead of tree supports, which means you are likely to end up choosing between supports stuck to parts of your model or unsupported areas. So that’s still a pretty serious flaw in the functionality, in that it doesn’t work the way a reasonable person would expect.
I would still call this very broken by design. But it is good to know that the support painting functionality is at least tied to something.
Yeah, it is not perfect, but it works in a way 