That’s awesome. Can you post a picture?
To clarify, this is something that’s working fine in every version before 4.7.2. Here’s how the right and left extruder look in 4.7.0:
It looks like you’ve found the bug though. The configs in the above picture (including the ones I sent you) are built around having ‘standard’ PLA on the main extruder (left for me) and ‘breakable’ PLA on the second extruder (right for me). So in all my tests I have standard black PLA on the left extruder and breakable white PLA on the right extruder. For the record, I have custom materials set up for each of those as well, but they’re in the same categories as the defaults:
Here’s where the bug gets complicated. In 4.7.2, if I change my right extruder to be standard PLA instead of breakable, my “GAB” configs are available:
However, when I switch my right extruder back to breakable PLA, and I duplicate one of the default support configs (that are showing up on the right extruder), that duplicate DOESN’T show up on the right extruder - it only shows up on the left extruder:
Final conclusion: For some reason, macOS Luban 4.7.2 is hiding all user-created configs for extruders that have “breakable support” materials applied to them.
//
One big silver lining to all this is that it looks like the support skirt issue was fixed when changing how parameters are read, so don’t mess that part up when you fix this bug.
“I’m wondering if you made these configurations for PLA? Or is it supposed to be a print configuration for Breakaway materials.”
According to above sentence, it seems that there is a way to make profiles for specific material. But I couldn’t find how to do it. Can you please let me know how to do it?
I don’t seem to be able to set a z-axis height for a dual colour model. It seems Luban wants to always drop all models to 0 but in this case I want the second model to be +2mm on the z-axis. Every time I move it with the mouse it jumps back to 0.
You should be able to set z manually or at least turn off auto drop to base.
The files I used are on thingverse here: Dual Color 3D Phil by MatterHackers - Thingiverse
Just mark both parts and press “align” on the top menu.
You can prevent the z grounding with slide the object to the high you want with the arrow for z axis and then just right click.
Thanks, not sure align is obvious here but fair enough that worked fine.
Looks like multiple selected and aligned objects form a group and grouped items can be moved relative to each other if one is grounded.
Still be nice to be able to type a z offset
With v4.7.2 I have encountered so many problems the slicer is unusable.
I am using the A350
-
All my custom print settings, custom material settings, all profiles, are missing after the update.
-
The custom option for creating settings is missing. Only Default is available.
-
The import profiles function is not working, so I can’t even restore my custom settings profiles from my backup disk.
-
Other issues are too numerous to list. Including many functions greyed out or missing. The slicer is not working currently.
CNC still does not account for the bit width in it’s calculations (after about 10 updates when I first reported it). If you use, say, a 6mm bit for roughing, and then go back with a 1mm ball nose for finishing, you end up with 3mm ridges in your work piece. It seems to work OK for the top, but the sides are completely stuffed.
Also - this then applies to “on the line” and “fill” as, well. There should be an option to fill inside or outside, or to be “on the line” cutting to the inside or outside.
3D printing initial line width does not seem to alter with changing the line width everywhere else (this is the only thing stopping me doing high-quality prints with a 0.2mm nozzle - everything else seems to alter).
I’m running 4.7.3, but there’s no thread for that version, so I’ll post it here.
I’m running into a bad bug with the dual extruder support — severe enough that I would describe the support as completely unusable. As soon as I switch any object in the model to use the second extruder, I end up with an extra cylinder that doesn’t exist anywhere in the model, which ends up getting printed, along with a large brim around it.
If I select the object that I added, cut, and then undo, the garbage cylinder goes away, leaving only the model. However, the model as a whole now says that it is using only the left extruder. And if I try to generate G-code in that state, when I try to export it to the workspace, it says "Generated G-code overstepped out of the cube, please modify your model and re-generate G-code.
At that point, if you try to set the entire model to a single extruder, you then lose the ability to change the parts independently, and worse, at that point, the file is utterly bricked (with the parts previously assigned to the second extruder now impossible to delete), and the only thing I can do is go back to the main menu and start over. And even if you manage to undo to get rid of the object entirely and reimport it, the file remains bricked, where you can’t change one extruder without them both changing, or if you manage to do so, that extruder’s part of the model becomes transparent.
I’m pretty sure I can break it even further if I keep trying.
This unexpected extra cylinder bug is almost 100% reproducible when importing 3mf models, and I think I also saw this behavior with one of the built-in samples. I did get it to work correctly exactly once. I have no idea what I did differently.
Steps to reproduce:
- Import this model: https://homeserver.gatwood.net/tag-SPARE.3mf
- Open the object list at the bottom.
- Change the first of the two Model objects to the right extruder.
Configuration: macOS 12.6.5 (Monterey), Apple Silicon
I also tried moving the cylinder outside of the printable area, but Luban “helpfully” prevents me from generating G-code at all in that state. Oh, and once you do that, it is impossible to move it back onto the print area again (other than with “undo”).
Somehow, through some combination of undo and redo, I managed to get it to show the object in the object list. It is called prime_tower_944. But if I hide it, I’m back to the “Generated G-code overstepped out of the cube” error again.
And after closing and redoing my import, that errant object remains hidden, but still shows up in the G-code!
After quitting and restarting, changing part of the model changed the whole model.
After closing and redoing that import again, I’m back to the cylinder. I did discover that it is possible to shrink the cylinder down to 0.2mm x 0.2mm. We’ll see what happens.
Also, whenever I connect to the machine, Luban keeps telling me that it is changing the extruder size from 0.4mm, 0.4mm to unknownmm, unknownmm to match the extruder. This one appears to be a cosmetic bug.
Partial solution. Turns out the cylinder is a feature intended to improve quality when switching extruders. The huge raft is so that it can rub up against it. Unfortunately, there’s no obvious UI when you click on it, so you have no idea what it is, and it isn’t shown in the parameters that are visible by default, so you won’t find it unless you deep dive down into the extruder settings (and only on one of the two extruders).
This is massive overkill for what I’m doing, so I’ve turned it off entirely, though it is nice to know that it exists. But it really needs to be elevated to the top level of UI. It isn’t an extruder setting. It’s a model-level setting, and one that a lot of people are likely to want to change, particularly when quality doesn’t matter that much.
And a workaround: The problem where changing one part of the model to an extruder causes all parts to change can be worked around by hiding the parts that you want to leave alone, making the change, then making those parts visible again.
Still broken in 4.7.3, still unusable until fixed.
SVGs and Gcode still arent rendering correctly with the laser. This has been going on since at least v2. Ive rendered the svgs multiple different ways and the gcode looks fine in Lightburn but is missing random cuts in Luban. They aren’t consistent either. Importing the same SVG into luban vs into Lightburn to generate gcode results in different missing lines depending on which file type is being rendered.
This seems to be the Prime Tower or Prime Tower & Ooze shield. If you go to More Settings for the Left Extruder, under Dual Extrusion Helper, there is a pull down. It seems to set it automatically. To remove the spurious Tower, set it to None.
But I am having a different problem. After figuring out the mystery Tower, I think I have it set to properly put support in using the Right extruder. But after generating g-code, it will not allow me to Export it. It is complaining: “Generated G-code overstepped out of the cube, please modify your model and re-generate G-code.” The Preview looks fine and it is way smaller than the “cube” of my A350, assuming it is referring to working volume.
Not sure what I did there. After clearing my workspace and starting fresh, it was still happening. Finally I quit Luban and started fresh. Worked fine after that…