Z" can be negative with Remove Empty Layers

[fabry2012]

Application Version

5.3.1

Operating System

Windows 11

Printer

Anycubic Kobra MAx

Reproduction steps

1. Rectangle raised 3mm or more on the z-axis
2. Use of adaptive layers activated
3. Slice

On the first layer there will be the following gcode with negative Z axis height which will make the nozzle hit the print bed violently, destroying the head and the bed. A real example

;LAYER:0
M107
M204 S20000
M205 X10 Y10
G1 F1200Z-24.29
;MESH:crown.stl
G0 F2700 X204.921 Y203.733 Z-24.29 <============

Actual results

physical destruction of the nozzle and print bed

Expected results

Z axis of the first layer close to zero or with a positive value

Checklist of files to include

• Log file
• Project file

Additional information & file uploads

Configuration

bugged gcode

[GregValiant]

Thanks for the report.
Please load the model and set Cura up to slice. Then use the "File | Save Project" command to create a 3mf file. Right click on the 3mf file in Explorer and select "Send To / Compressed (Zipped) Folder". Post the Zip folder here.
I can duplicate this behavior. Part of this might be a known bug involving raised models and "Remove Empty First Layers".

@MariMakes here is a project file. The "Z" is negative when the model is raised up off the build platform, "Generate Supports" is disabled, and "Remove Empty First Layers" is enabled. "G0 F9000 X98.5 Y103.121 Z-2.36"

If "Remove Empty First Layers" is disabled then the first layer is "G0 F9000 X126.5 Y126.5 Z10.64"

Adaptive Layers doesn't appear to have anything to do with this.
GV 15975.zip

[github-actions]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

[MariMakes]

Quick update from our side 👋

I stumbled upon your issue and recall bringing it up to the team but cannot find the follow-up we've done on it.
So I'll bring it up to the team again to see what they can do to improve it.

Apologies for the slow response.

[MariMakes]

Apologies for the delayed response.

We've added a ticket to the backlog with the intent to improve this.
For internal reference CURA-11537

Thanks for the report! 👍

[HellAholic]

Issue has been resolved, validating with the project file @GregValiant provided (Thanks), the gcode shows:
G0 F9000 X98.5 Y103.121 Z0.2
after applying the fix.

Fix will be part of the next release.

Cheers!