Luban is bad on a fundamental level, what gives?

Snapmaker Luban
1

This behavior isn’t limited to any file in particular. When building the g-code, Luban seems to do what is wants in several ways. The randomness is reminiscent of working on PCs in the 80s and 90s.

Specifically:

ADHESION - May appear as a SKIRT in the render, despite BRIM being selected, or it may decide to render nothing as though NONE was selected. Worse yet, the actual printout on the printer MAY OR MAY NOT correspond with what is rendered.

INFILL - Similar to ADHESION, but less often, the printer will perform INFILL at whatever the previous setting was, despite having been updated and g-code regenerated.

LAYER HEIGHT - I have to close and reopen Luban, sometimes several times, in order to have an accurate number of layers in the rendering which corresponds to [project height/layer height].

SPEED: Similar to INFILL behavior.

Learning the performance limitations of the printer and various filaments in time consuming and difficult enough without having to babysit such fundamental aspects of Luban.

1 Like
2

LUBAN is essentially a bunch of open source software poorly stitched together… its just not well designed and released without proper testing. Just give up on it and use good software like cura, lightburn and estlcam

1 Like
3

I’ve tried Cura and when Luban works, it produces better prints for me.

I’m not asking for opinions on alternatives, I want the basic functions of proper data field entries. I’ve cobbled together my own code a number of times, and the BASIC requirements are not hard. Simple variable correlation being so random is just a joke, but can be easily fixed.

4

That’s a fair request. The Github issues list seems to be the best place to get issues like that addressed:

2 Likes