1. Try to merge filaments before grouping
2. Set max match num for machine filamnet in match mode
jira:STUDIO-10392
Signed-off-by: xun.zhang <xun.zhang@bambulab.com>
Change-Id: I2451d838e07ee02f493fda4dc702f3d13b2ad37b
and set the contact surfaces of different material types as solid,
and reduce the nozzlechange speed if it occurs at the contact surface,
and recuce the toolchange speed if it occurs at the contact surface.
jira: none
Change-Id: I884d60f4114544dfa959bd654ecc985f5fb9aac4
Use clipper2 and remove colinear points.
Later on we can try to set lightning infill as the default infill pattern of tree support.
jira: none
Change-Id: Id545b15d778071cec6e56d212ab68db1ab90ad2a
Thanks to Prusa!
jira: none
original commit message:
ceb13b1faa33ac096fe7ffd89aa222abca119e02
SPE-2405: Add Zig Zag infill that is rectilinear infill but with a consistent pattern between layers.
This Zig Zag infill is inspired by the Zig Zag infill in Cura.
Change-Id: I798affa99f4b5c3bd67f47643e67530fb7c3e0cb
(cherry picked from commit 2808d04d5deef6f99f9618648e46f11de03efc98)
In the original logic, the gcodeEditor did not parse gcode lines with
leading spaces. In recent changes, all leading spaces in gcode lines
were removed, causing all gcode to be parsed. However, some certain cmd
perform additional actions, leading to incorrect state recording. As a
result, based on the erroneous state, some gcode lines that should not
be deleted are being removed.
This logic needs to be optimized in the future.
jira:10357,10367
Signed-off-by: xun.zhang <xun.zhang@bambulab.com>
Change-Id: If34b9c3b2913768b824030685e0a36708ca3a5ca
1. fill bed crash (jira: STUDIO-10350)
2. reset arranging settings gives wrong sequential printing order (jira: STUDIO-10346)
3. do not show "arranging done" message when there is no model
Change-Id: Ic1c7eac75e3917b9f1d87ab6acc403f78e0c9f7c
1. the nozzle change gcode use double perimeter width
2. fix the error layer height for adaptive layer height
3. limit the nozzle change speed to 50 when a bridge is detected
4. fix the error extrusion flow for filament change gcode when a bridge is detected
jira: STUDIO-10269
Change-Id: I580c618555fe19d000a56e2510a42004722c1b8b
1. Add filament_is_support field. Format the filament type
2. Optimize machine filament info logic
jira:STUDIO-10326
Signed-off-by: xun.zhang <xun.zhang@bambulab.com>
Change-Id: Ia8bfc37095339e73c98209b4e3f1e0804e511e88
1. change type of transition layers below interface to erSupportTransition,
2. fix the number of transition layer above tree branches,
3. change the default setting of support_interface_pattern to smipRectilinearInterlaced,
4. change the default support_style to HybridTree when interface is soluble
5. FIX: conflict between xy_expansion && split_hole
jira: STUDIO-10239, STUDIO-10314, STUDIO-10319
Change-Id: I3eb392ccd005acedb001aa862d5bf3eb104c5293
Clipper2 has added a lot of features in the past 2 years, including "offset to polytree" which is very useful for expolygons.
jira: none
Change-Id: I6f51e243656312d8c7693e1c9f5c52cf2f0034d1
1. The line id in filament block and exturder block
is assigned during first gcode process. So we should
add offset caused by gcode processor to line id
jira:NONE
Signed-off-by: xun.zhang <xun.zhang@bambulab.com>
Change-Id: I6a24b052fdf0daa3506c5f0982b521e85107f193
and fix wipe error when enable timelapse and in single color
and set rib wall as default
jira: none
Change-Id: Ic365bb7ee0ee6715c9d4f4f00b4bca9fd472c61a
1. Filter small sparse infil after doing vertical shell detect.To make
sure the params always work, the logic should also be added after doing
internal bridge detect
jira:STUDIO-9872
Signed-off-by: xun.zhang <xun.zhang@bambulab.com>
Change-Id: I9d48303e156125dfab17ef95b73294013ab9fabd
2. use most used extruder for timelapse without wipe tower
3. apply retract_when_changing_layer for multi_extruder
jira: none
Change-Id: I4ff00573fd8a6ee9fa42877e3e7056d547e4d864
xun.zhang
zhimin.zeng
qing.zhang
jiangkai.zhao
Arthur
chunmao.guo
Lukáš Hejl
zhou.xu
xin.zhang
jiaxi.chen
guanyun