2.3.57: Double Travel Between Perimeters

[CCS86]

I wanted to double check if this was expected behavior. It seems like splitting the move like this could slow it down with jerk/accel limits:

Objective Lens Cap.3mf.txt

[supermerill]

I don't understand.

[CCS86]

Instead of a single travel move, from the end of one perimeter to the start of the next, it is splitting it up into 2 travel moves.

[supermerill]

that will add a useless line in the gcode, no?

[CCS86]

I don't follow.

I'm saying the the current build, there are 2 travel moves, instead of one. To me it seems like a useless line of code, that could cause motion control to execute it slower than a single move. I wanted to check if you had a specific reason for doing this.

[gpread]

My intuition makes me wonder if this is related to #1550 ?

[supermerill]

I'm saying the the current build, there are 2 travel moves, instead of one.

weird, I saw only one.

[qwewer0]

I'm saying the the current build, there are 2 travel moves, instead of one.

weird, I saw only one.

Objective Lens Cap.3mf.txt

@supermerill Try at Z=7mm, 40298-40300.

[supermerill]

it's at 7.2
something is wrong.
what version?

[qwewer0]

it's at 7.2
something is wrong.
what version?

I tried it with 2.3.57, but here is a video of it:

bandicam.2021-09-28.06-13-55-431.mp4