| Age | Commit message (Collapse) | Author |
|---|
|
CURA-9159
|
|
CURA-9096
|
|
5.0
|
|
Contributes to CURA-8640
|
|
Contributes to CURA-8640
|
|
Contributes to CURA-8640
|
|
A container is no longer needed. We can build
directly on the VM since it is the same ubuntu
version as our container.
Build script will first install conan
and then pull the repositories.
Including arcus for which I added a Conan
package to the ultimaker remote artifactory.
These dependencies will in all likelyhood be
recompiled at each run. Normally you would
upload the build conan artifacts but the
current artifactory server is still a test
server.
I also still need to fix the Conan target
naming for the GTest.
Contributes to CURA-8640
|
|
Contributes to CURA-8640
|
|
|
|
Cura 8640 PyQt6 upgrade
|
|
CURA-9088
|
|
Fix missing infill layers
|
|
CURA-9088
|
|
|
|
Add missing parameter to infill constructor
|
|
|
|
CURA-8640_PyQt6_upgrade
|
|
Ultimaker/CURA-8694_Retracted_unnecessary_travel_moves_part_II_return_of_the_comb
[CURA-8694] retracted unnecessary travel moves part ii return of the comb
|
|
Contributes to CURA-8640
|
|
Contributes to CURA-8640
|
|
Feat/Fix: transition filter limit
|
|
# Conflicts:
# CMakeLists.txt
|
|
CURA-8694
|
|
rather then the `travel_avoid_distance` offsetted boundary
CURA-8694
|
|
This commit should allow for the usage of Conan to manage our dependencies
simply do a `conan install . -if <cmake_build_folder> -pr:h default --build=missing`
and configure the CMake project using the toolchain `-DCMAKE_TOOLCHAIN_FILE=<cmake_build_folder>/conan_toolchain.cmake`
I did my best to make this change backwards compatible and allow falling back to
shipped third-party sourcecode e.q. clipper and rapidjson.
This third party sourcecode will be removed in the near future.
Contributes to CURA-8640
|
|
This allows CuraEngine to be compiled with Visual Studio
https://github.com/boostorg/polygon/issues/40
Contributes to CURA-8640
|
|
A bit of an insidious issue: The Infill constructor has so many parameters that you can't tell when one of them is missing. And some of the parameters are optional, so the compiler won't warn you about it. It even automatically casts between the bool and int type parameters so it's completely transparent except that the parameters get the wrong value when e.g. an enum has the value 0 instead of 1.
Recently we added another new parameter to this constructor: skip_line_stitching, added by c7dedb5edcddb1a734ed8c9fe867824170514daf. This parameter was set here and there where it needed to depend on whether the pattern was a monotonically printed line pattern. But other uses of this constructor were not modified. And so the parameters after that were used to determine whether it needed to skip_line_stitching. Those parameters often had completely unrelated values, in particular whether zigzags need to be connected. Because zigzags are connected in some cases, it would in those cases skip the stitching instead. And all other parameters would also shift by 1 leading to very weird results.
Fixes issue CURA-9077.
|
|
Contributes to CURA-8640
|
|
Contributes to CURA-8640
|
|
Contributes to CURA-8640
|
|
Having defaults is more bug-prone and the values for these defaults didn't always correspond to the values which were normally used
|
|
https://github.com/rijkvanmanen/CuraEngine into rijkvanmanen-PP-122_cooldown-other-nozzle-earlier
|
|
Conflicts:
src/infill.cpp -> Modifications to fix density of concentric infill, while a typedef was removed in this branch.
Contributes to issue CURA-8998.
|
|
github.com:Ultimaker/CuraEngine
|
|
inner walls
The difference in geometry diameter can be distributed over two walls, so then we should be more lenient to the filtering limit.
This doesn't take into account that the wall distribution count can be more than 1, just to simplify how it works.
If the user sets a distribution count >1 then the actual line widths will be more close to the intended line widths,
in that case the filtering could have been more aggressive.
Still it's within the filter deviation limit, so it's technically OK.
|
|
We always want to use Inwards Distributed beading strategy from now on. We'll keep the system of expansible strategies in though.
Contributes to issue CURA-8466.
|
|
github.com:Ultimaker/CuraEngine
|
|
|
|
|
|
|
|
So that we don't have to recompute it from the pos and the feature radii of the end points of the edge on which the transitionMiddle is located
|
|
Separate flow ratio from line width factor
|
|
CURA-8694
|
|
|
|
The back-pressure compensation now only compensates for changes in line width (away from the nominal width, only the width factor). This needs to be tested.
Contributes to issue CURA-8737.
|
|
We want two multipliers on the amount of extrusion here: One to reduce the flow rate out the nozzle, and another to reduce the flow rate but possibly get compensated for by changing the print speed.
So the paths need to contain an extra field. I'm calling it width_factor. It's a multiplier on the line width that gets compensated for by applyBackPressureCompensation. That function now no longer takes the flow ratio into account, just the line width.
Because of this extra field, a bunch of function calls to addExtrusionLine need to have that extra parameter too, so that applyBackPressureCompensation can separate the width from the flow still. This is a bit of a hassle!
Contributes to issue CURA-8737.
|
|
CURA-8875 Add tie-breaker to seam score calculations
|
|
CURA-8875
|
|
CURA-8875
|
|
|
