Getting Incomplete Slicer Configuration detected

[old geyser]

Incomplete Slicer Configuration detected

Your slicer gcode settings are not up to date.
Learn more about the RatOS 2.1 Slicer Configuration

I copied and pasted the Cura specific slicer settings, but I still get this error message. Anyone know why. Also, shouldn't the skew profile also be in the printer settings in Cura?

[coarse locust]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[agile patio]

Also, shouldn't the skew profile also be in the printer settings in Cura?
No. https://github.com/HelgeKeck/RatOS/blob/documentation_v2.1/site/docs/configuration/macros.md#skew-profile

[gcode_macro RatOS]
variable_skew_profile: "my_skew_profile_name"

It would help if you posted a screenshot of your Cura start gcode settings. Make sure to follow this: https://github.com/HelgeKeck/RatOS/blob/documentation_v2.1/site/docs/slicers.md

[old geyser]

This is what I have in Cura

I just added the skew profile last night. But with or without it I get the same message

I should also say that it does print, and it does a Dynamic mesh.

[agile patio]

It's complaining because it's missing "Total layer count", i don't think the Cura slicer settings were ever completed for 2.1. @fair island any idea what we do here? Short of saying "don't use Cura"? 😂

[fair island]

one sec

just ignore that message in case you use cura

cura is indeed not fully functional with ratos in any case, the layer numers are used in multiple ocassions

but you can totally print with it

[old geyser]

No problem. Thank you.

[fiery bison]

I think its also cos Cura doesn't fully use the firmware retract

[agile patio]

No that doesn't matter. Firmware retraction isn't very widely used, most of us use the slicer's own retraction mechanisms. Firmware retraction just replaces the slicers own logic with G10/G11. There's nothing to "support" in that sense. Either it's used or it's not.

[fiery bison]

ah that was the point i thought of
since i also use cura

[quaint spire]

@agile patio I get Incomplete Slicer Configuration too, but I've set everything in PrusaSlicer2.8 mentioned in Helge's docs. I've been looking through my klippy.log for a hint as to what's wrong but found nothing. The only thing I see in PrusaSlicer is it shows RatRig, ver: 2.0.2 instead of 2.1.0. Maybe that doesn't matter. But where did you see the missing Total Layer Count in renatojd2010's case?

[agile patio]

Because the "Incomplete Slicer Configuration" error is only triggered if TOTAL_LAYER_COUNT isn't passed to START_PRINT. Ie, your custom start gcode in your slicer profile isn't correct. The doc has everything you need.

you need to copy that entire thing (use the icon button to the right)

[quaint spire]

Yup. Somehow my Control-C was not the same as the copy code button. Sorry to bother you, but thanks!

[agile patio]

no worries