Jump to content
Cura Connect | Survey Read more... ×
Ultimaker Community of 3D Printing Experts
billplate

why is layer height omitted from per a model settings

Recommended Posts

Cura has had per model settings for quite some time (since 2.1), but we've never supported multiple layer heights. This is an intentional "omission". Having multiple layer heights makes the slicing process orders of magnitude harder. It's doable if you only use magnitudes of a layer (eg; one object with 0.1 and the other with 0.2), but even that would require large parts of our architecture to be re-written and a load of extra features to be added.

Share this post


Link to post
Share on other sites

Thanks for the reply nallath.

I'm not familiar with the structure of gcode so i only get jist of what your saying. 

Forgive me if this is a stupid question, but could problems u mention not be bypassed by treating the per-model-layer-height setting almost like separate prints in a queue? so it would effectively be loading  a new gcode for each object? A compound-gcode as it were :)

Edited by billplate

Share this post


Link to post
Share on other sites

Well I suspect that is how it works, i.e. if you are printing 4 copies one at a time then there will be 4 copies of almost the same code, to print a copy, following each other except that the x/y axis positions will be different but the extrusion amount will be the same for each line of code. But apart from having to do work on the user interface, in the background you then have to deal with issue of different copies having different heights and avoiding collisions during printing etc.

Share this post


Link to post
Share on other sites

@ yellowshark

what u describe is, as i understand it, how the slicer works, not the gcode,  which is simpler and dost have a  concept of objects or copies.

What I'm saying is, if having multiple layer heights is an issue for the printer.  

Crate a "compound_gcode" which contains multiple objects (each with their own gcode)  which automatically load in sequence, without resetting the nozzle position. Collisions wouldn't be an issue as it would be calculated the same way as a normal one-at-a-time print. the only difference is that each object is treated like a separate gcode before being packaged as this  "compound_gcode".

 

Edited by billplate

Share this post


Link to post
Share on other sites

Theoretically it could be possible to have layer height available if you're printing multiple models in one at a time, but we also have some legacy issues, which make some things harder to build than they actually should be. As we always have more features than we have people to build them, the stuff that isn't used that much tends to not get picked up.

 

Compounding the g-code is theoretically possible, but it does create quite a few issues with avoidance paths.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Our picks

    • Architect Design Contest | People
      The goal of this contest is to design a set of people figurines that could be used in such a project to make an area, office or mall seem populated. 
      Think of different types of people in different environments, like walking people, people standing still, working people, and both men and women.
       
      • 9 replies
    • Taking Advantage of DfAM
      This is a statement that’s often made about AM/3DP. I'll focus on the way DfAM can take advantage of some of the unique capabilities that AM and 3DP have to offer. I personally think that the use of AM/3DP for light-weighting is one of it’s most exciting possibilities and one that could play a key part in the sustainability of design and manufacturing in the future.
        • Like
      • 3 replies
×

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!