It doesn't work for those patterns at the moment. For Gyroid it could be made to work. For Cross and Cross 3D it's a bit more difficult due to the pre-calculations and density image done for those.
Contributes to issue PP-55. Done as a 5 minute fix.
These two have garnered some feedback in that it's wholly unclear what the sentences even mean. Hopefully this correction makes it more clear for next time.
Contributes to issue CURA-8638.
Two changes have been made:
- Use more consistent terminology for the top side of the model (which could be skin or walls). This is corrected from feedback by our translators.
- Don't add disclaimers about the infill density to this already way-too-long setting description. If anything, a disclaimer should be added to the infill density description that Gradual Infill and some infill patterns might not reach the desired density everywhere. But really, I think it's more in the domain of user documentation like the Ultimaker website or the Settings Guide.
The "Combing": "Not in outer surfaces" option will be activated for all extruders in the following cases:
1. Monotonic Top/Bottom Order is enabled (in any extruder)
2. Ironing is enabled (in any extruder)
3. Top Surface Skin Layers > 0 and Monotonic Top Surface Order is enabled (in any extruder)
CURA-7976
Since the setting version 18 is used in the arachne beta build, we decided to make the the setting version to 19 in the normal releases, so that we make sure that projects made in arachne beta won't use any version upgrade scripts if a user attempts to open them in 4.12.
CURA-8510
We now have version 18, where Flsun Super Racer has customised profiles.
Nothing changes in the built-in profiles. It only needs a change in the machine instances.
Contributes to issue CURA-8510.
Fixes an issue where, when the global infill density was 0, and the settings for a mesh overlap changed the infill line distance (but not outright the density), the infill pattern would be disabled in the mesh overlap settings. (You still will need to select both the density and line width to actually change the line width though.)
Relates to github issue Cura/10349 (not explicity linking it here, as it might close that issue then, while it shouldn't as most sub-issues in there are still unresolved one way or the other.
This was not a true limitation of the mathematics. In fact, we had other flow settings (for initial layer) that already went to 0.0001%.
Discovered while working on a bug report from Reddit.
We created a new set of icons for Cura. These icons had to be reverted though because they weren't working out in the interface for the last release yet.
This unreverts them, basically adding them back hoping that we'll get them fixed in time for the next release.
Contributes to issue CURA-8342.
Revert "Revert "Fix merge conflict""
This reverts commit bb20e3307f.
Revert "Revert "Merge pull request #9716 from Ultimaker/CURA-8010_new_icons""
This reverts commit 70e4e9640e.
Revert "Revert "Fix typo in icon name""
This reverts commit 38ce22ba7c.
Revert "Revert "Add list for deprecated icons""
This reverts commit 119a957e7f.
Revert "Revert "Add Function icon""
This reverts commit 760726cf0b.
Revert "Revert "Switch out inherit icon""
This reverts commit 26afff6093.
Revert "Revert "Merge branch 'CURA-8205_Introduce_new_icons_in_Cura' of github.com:Ultimaker/Cura""
This reverts commit 6483db3d47.
Revert "Fix incorrect icons"
This reverts commit 02a4ade2a5.
The setting influences support meshes. If support was disabled but there was a support mesh, this setting would influence the slice result even if it was invisible.
Fixes#10002.
Technically, moving the feeder wheel by 1mm doesn't guarantee that the filament gets extruded by 1mm, since there might be slip.
Reported in issue #9924.
It's also used as the speed at which layer changes are made, so technically it should be kept visible since the setting does indeed affect the g-code.
In practice, it won't affect the print though. Using a reasonable Z hop speed of 10mm/s and the default acceleration of 100mm/s/s, it would take 0.1s to reach the Z hop speed. With the formula for acceleration, 1/2att+vt+c, you can see that it needs 0.5mm to get up to speed, and another 0.5mm to get back to 0. So this speed is only attained with layer heights of more than 1mm which is very unrealistic. For this reason we won't document this in the setting description or its name. The Z hop speed is only used for layer changes because it needs a sensible default for extreme cases, not because it needs to be configurable as such.
But we'll keep it visible to give a less-than-expert user a feeling of control, a placebo effect that they are actually making print quality improvements even if their firmware forbids it from making an actual difference.
FixesUltimaker/CuraEngine#1446.
Subdivided the new icons in 3 size categories. As requested by UX
Used the company naming scheme for uniformity and easy recognition.
Known issues:
- Top/Bottom category wasn't taken into account by UX at the time. Since
this is a recent addition. Both the Walls and Top/Bottom will be updated.
- Cloud/Network connection icons 12px don't render correctly. Due to the
theme-ing.
- Extruder Icons do not render correctly.
CURA-8010_new_icons
These initial layer speeds were only applied to the model (not the raft).
Number of Slower Layers indicates how many layers the initial layer speed should apply to. So if that is 0, the initial layer speed doesn't apply to anything any more, and the setting should be hidden because it has no effect on the print.
Found by Markouustalu in #4439.
- The 'main' support radius will be taken from the already existing infill line distance.
- New: Lightning Infill Support Prune Angle: Controls how fast the trees are eroded from the extremeties.
- New: Lighning Infill Support Straightening Angle: Controls how fast the junctions of the tree smooth themselves into ever straighter lines.
After changing this with fvrmr together I read back on the commit and realised that the sentence was literally saying that it affects adhesion, and then that it doesn't affect adhesion. I hope this clarifies that a bit better by giving examples.
