burtoogle
-
Posts
1,529 -
Joined
-
Last visited
-
Days Won
19
Content Type
Forums
Events
3D Prints
Posts posted by burtoogle
-
-
Hello @eagerdas, meshtools says your model is not watertight, that's why it won't slice right.
You can install the meshtools from the Cura marketplace.
-
OK, the biggest problem was that the Max Travel Resolution setting is far too high (I think it was 15!), make that the default value. Other changes I recommend are setting the combing mode to no skin, the max comb distance without retract to something like 10, enable the wall print order optimization and set the maximum retraction count back to a large value. Hope this helps!
-
1
-
-
-
39 minutes ago, kulfuerst said:
What else sets this apart from vanilla Cura? I suppose infill resolution isn't the only thing modified in it.
The README.md does mention most of the differences between my releases and Ultimaker's.
-
Hi @terramir, could you please save a project file (File -> Save) and attach the .3mf file to this thread. Thanks.
-
The cura layer view only distinguishes between retracted (light blue) and non-retracted (dark blue) travels. It doesn't show whether z-hop is used or not. You have to use another gcode viewer to see what's going to happen.
If you have the z-hop only over printed parts setting enabled, it won't z-hop between parts, it will retract, but not z-hop.
-
Hi @V3DPrinting, the answer (not very obvious) is to turn off Z-hop only over printed parts for both extruders. Hope this helps!
-
Try setting the Minimum Infill Area, that was intended to do exactly what you are talking about. Another setting that may help is the skin expand distance.
-
Hello @Vinnycent, to understand your problem better it would help hugely if you could attach both the gcode file and also the Cura project file. To get that do File -> Save to produce a .3mf project file. Thanks.
-
17 minutes ago, orlin278 said:
As a workaround I just saved a 3mf file with just a small object and all settings visible now so I can reconstruct it. But is there a easier way?
Yes, install Aldo's excellent setting visibility saver plugin and then you can simply reload your settings after loading a project.
-
2
-
-
I implemented minimum top/bottom skin thickness for when adaptive layers are in use. You can find Linux and Windows builds with this feature at https://www.dropbox.com/sh/s43vqzmi4d2bqe2/AAADdYdSu9iwcKa0Knqgurm4a?dl=0
I don't use adaptive layers myself so please try it out and open an issue at https://github.com/smartavionics/Cura/issues if you have any feedback.
If it works OK, I shall submit a PR so it can be added to Ultimaker's Cura.
-
Turn on the wall overlap compensation and set the min wall flow to, say, 40 (not really very critical). Hope this helps.
-
2 hours ago, Safety_Lucas said:
Thank you for the link. I will take a look at those distributions Do you make them yourself? As in, do you write the code for Cura features?
Yes, I make them myself and they are based on Ultimaker's development sources + my own fixes and additions.
OK, I'll think about the speed factor. Maybe something based on the tan of the overhang angle would be good?
-
Hello @Safety_Lucas, thanks for the interesting report. Can you provide more info, please? What range of speeds would you want to use WRT the overhang angle?
BTW, my Cura builds also provide a separate fan speed setting for overhanging walls:
That feature has already been rejected by the Cura developers so it's only going to be available in my builds (Linux and Windows only, I'm afraid) which can always be found at https://www.dropbox.com/sh/s43vqzmi4d2bqe2/AAADdYdSu9iwcKa0Knqgurm4a?dl=0
-
8 minutes ago, Madau3D said:
p.s. I usually have connect infill lines enabled, regardless of infill pattern, because it reduces retractions a lot.
Me too! It also has an added benefit when you have a skin that finishes on top of infill as the skin edge can butt up against the infill connections like you see here...
-
1
-
-
2 hours ago, Madau3D said:
Are they any options in the menus to control the behavior? At fist glance it doesn't look any different than regular Cura.
There are no options to control the behaviour apart from the min area of gaps to be filled (gaps smaller than this will be left unfilled).
2 hours ago, Madau3D said:Options to specify different line widths for specific line types would still be useful- i.e. print infil and supports thinner than top and bottom surfaces, or walls, etc..
Of course, you still have the normal settings for specifying the line widths for various features:
PS - looking at your image, I should think that 10% gyroid infill with the connect lines (zig-zaggify) option enabled would work well.
-
1
-
-
9 minutes ago, Link said:
It's seems the overlap compensation code remains broken and not likely to get fixed 😔.
They have had years to fix it and not done anything and they weren't interested in using the "improvements" that I have made to that code some time back. It seems unlikely that this will get better anytime soon.
-
Thanks for the files. I believe the stuttering is caused by the model's line segment lengths getting "adjusted" by the overlap compensation and so the line segments end up with widely differing lengths, some very short.
TBH, I don't understand how a lot of the compensation code functions as it is not well documented. In the past, I have made some changes and I believe the version I have in my builds is better but it still doesn't behave very well. The current Cura master branch which will form the basis of the next release does make a better job of the cylinder when the line width is exactly 0.8 and the fill gaps between walls feature is disabled. My current build is also OK with a 0.8 line width and there is no need to disable the fill gaps feature. However, increasing the line width so that it is more than 50% of the wall width will cause the bad segmentation to occur again when the overlap compensation is enabled. Sorry, not very good, I know but that's how it is right now.
-
Thanks for the files. The gcode didn't look bad as I expected and the model is too large for me to slice for my printer. Could you please provide the gcode and model for the cylinder, please?
-
I think I know what's happening there, could you please provide the gcode that stutters and also the stl file? Thanks.
-
1 minute ago, Link said:
interestingly Cura says to use the min flow you have to print outer walls before inner will can affect overhang quality ?
If I remember right, you don't have to print outer wall first but the way it works is that the first line that gets printed is extruded at the normal width and then subsequent lines that overlap that first line get extruded at a reduced width (or omitted completely if their flow is < the min flow value). So to get the most accurate outline, you need to print the outer wall first.
What is your max resolution set to ?
Generally, I just use the default values but I note that (a) they have recently introduced a Max Deviation setting and (b) have increased the default value for max resolution.
I think (OK, I'm guessing) that the max deviation is now really controlling the accuracy of the print rather than the max resolution. i.e. use longer line segments (up to max resolution) as long as points do not deviate by more than max deviation.
Using a coarse resolution makes the slicing quicker and the gcode file smaller but does have the downside of making it even harder to achieve a nice straight z-seam on a curved object. Here's what I mean...
Here's a model sliced using the default values for max res and max deviation. I have enabled coasting simply so that it shows the z-seam position more clearly (I never normally use coasting as I think it is detrimental to print quality). Notice the ragged z-seam...
If you then change the max res to 0.05 (i.e. ten times finer), you now get a much nicer z-seam...
So the lesson there is that using a coarse resolution makes it hard to achieve a nice z-seam on curved objects.
PS - don't use the sharpest corner z-seam style, it very rarely works well. Always use a user-defined z-seam (with a small max res!)
-
2 minutes ago, Link said:
Thanks, what you advise to set the min wall flow too ?
It's not very critical, it can be quite large, i.e. 50%. If it is too large, it could introduce gaps into wall lines that would otherwise be complete.
3 minutes ago, Link said:Also do you tend to disable overlap compensation todally, what are the downsides of this ?, what is it meant to do when working properly ?
No, I nearly always use the overlap compensation and I do not get zits like you are seeing. That's with PLA and PETG using a 0.4mm nozzle and 0.5mm line widths.
-
Hello @Link, you could try using one of my builds that has had some improvements made to the wall overlap compensation feature. You can find builds for Linux and Windows at https://www.dropbox.com/sh/s43vqzmi4d2bqe2/AAADdYdSu9iwcKa0Knqgurm4a?dl=0
I don't claim perfection but it does work better than the Ultimaker version (IMHO).
If you are using the overlap compensation, make sure to set a non-zero value for min wall flow so that the thinnest wall lines are removed.
Another reason for getting zits is over-retraction. Please check that you are not retracting too much.
Finally, make sure to use the no-skin combing mode and set the max comb distance with no retract to something like 10 or 20.
Hope this helps.
-
Thanks, I tried but the walls are too thin for my 0.4mm nozzle.
Experimental Cura build for Raspberry Pi 4 now available
in UltiMaker Cura
Posted · Edited by burtoogle
Now available is a Linux AppImage that runs on an armhf system (e.g. a Pi 4). It has received minimal testing but it does appear to work (I sliced a benchy OK!).
Obviously, even the amazing Pi 4 is still quite limited compared to most laptops, etc. so don't expect stellar performance but it is surprisingly usable. I think it exceeded my expectation.
It is highly recommend that you have 4GB of memory and a CPU fan!
Known limitations are that currently the layer view only works in compatibility mode and that the UI QML is slow due to lack of JIT support.
If you try it out, please post feedback on this thread or open an issue at https://github.com/smartavionics/Cura/issues.
You can find the release at https://www.dropbox.com/sh/s43vqzmi4d2bqe2/AAADdYdSu9iwcKa0Knqgurm4a?dl=0.
Remember, all my builds are provided with no warranty whatsoever. That said, I try to fix issues where I can.