Would like the ability to set 0 on elegoo tiltvat .ctb

[Cilsor]

This is merely a suggestion and not a bug or failure mode. It's in the context of owning an Elegoo Saturn 4 Ultra 16k

If it's possible, I'd like to set 0 movement on the lift height and lift speed for .ctb files for printers like the Saturn 4 Ultra 16k. Native exports from the satelite slicer result in 0 movement, and 0 speed, whereas exports from chitubox slicer and from UV tools only let the user set a minimum of 0.05. Since Chitubox will not let me correct movement in it's GUI, I figured I could use UV tools to make this correction to match manufacturer intentions -- but UV Tool also has this minimum limit.

My feeling is that the manufacturer intends movement only to occur for layer height increases, whereas having the z-axis take part in peeling will necessarily increase the violence of peel forces. It might also contribute to unnecessary wear on the z-axis as it tries to move up while under tension. The arm that the platform is suspended from is a loadcell sensor that has some intentional give to it, but this give also likely contributes to binding and why a lot of users seem to report the S4U16k is very sensitive to lacking enough lubricant. It is more prone to binding thanks to that flexibility and then Z errors from that binding are what I suspect a lot of people are mistaking for skipped layers.

Thank you for your consideration.

[sn4k3]

That value is not used, tilting vat printers do use file lifts and can't be controlled. Its all under firmware.
Setting 0 or 0.05 have same effect.

I have seen slicers using 0, others 0.05, others layerheight as value, it all ends in the same.
Value in UVtools is forced and can't be changed by anymeans other than edit the main code.

[Cilsor]

I'm just curious but if that's the case, is there an issue with having an extra layer of redundancy where such overrides can still be populated? There may come a time shortly in the future with Elegoo's newer models where the tilt vat can be controlled outside of firmware and maps to such things. It would be future proofing, and peace of mind. I understand if you disagree with being preemptive and doing work that might not be necessary however.

[sn4k3]

In the past UVtools used 0 as value, but to follow most slicers I set to 0.05mm.
I could add a global setting to control that. The code locks to machine name, if you change machine name you will be able to control that values

[Cilsor]

Thank you for your candid reply. What you're saying makes good sense.