![]() ![]() So unlike other projects where the push back is 'that would take too much effort to implement' when a feature is requested. ![]() This might be as easy as adding // to one line of code, hard to say. What I find interesting about this project, as compared, say to nearly any other, is that simple changes are requested, that would take a very short time to implement - in this case, I expect it might be as easy as commenting out code that forces the Z to be back on the plate. Have you ever used cura? It is very intuitive to just take a part in 3D space and rotate it in every direction and move it in every direction. Maybe this was not my best example without a drawing. This is easily achieved by enabling the raft. You will get better results if you lift it up so that support is everywhere and not only 0.5mm below that higher area. Try to print a part that has one area of its underside touching the build plate and another area of its underside 0.5mm higher in Z direction. I cannot find a reason why it should be forbidden to move a part up or down.Īny functionality, which is not needed, will stay in somebody's way. ) then cut the part at that height in the slicer.Įxport gcode, print -> Printer will continue at the layer where the failure happened. I don't understand how this is supposed to help to resume a failed print.įind out the height of the failure (caliper, log. It works but is not as intuitive as just lowering the part below the Z = 0 plane.īut to resume a failed print is really easy with lifting the part up. What is not-so-comfortable on the cut function? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |