Axis_twist_compensation: compensation applied at wrong coordinates due to probe offset

[mdewayne7]

Hi RamonSaboya, and welcome. I see that the topic you linked only had Murdo responding to himself, and I would be surprised if you get much of a response as well.

Primarily because The "dirty" Flag and the Team's Position

The Klipper bros don’t have time for anything that isn’t ‘theirs’ and pretty much disregard or dismiss anybody seeking help with the dirty flag.

It’s disappointing, because obviously there are talented people with the skill and desire to implement and incorporate many of these extras so they wouldn’t be quarantined.

But there is obviously a disconnect somewhere…

Hence Kalico…

Additional reading here…

Possible Klipper "plugins" instead of macros?

The current Klipper macro system has shown impressive results. Impressive, both in a “terrific” way and in a “terrible” way. Terrific in that I’ve seen macros used to implement very impressive functionality that can directly improve user printing experience, and terrible in that some macros have grown to a level of complexity that makes them very hard to troubleshoot. One of the weaknesses of Klipper macros is that they rely on Jinja2 and G-Code - both of which are very “quirky”. They both a…

New submission process for feature enhancements

I believe that this is a commendable strategy. However, I’d like to offer some additional thoughts from my support perspective: Handling Macro Utilization My interpretation is that a primary objective in the design is to ensure that the intricacy of features and settings remain manageable. Regrettably, the current frequent usage of macros by users to circumvent absent features or enhance flexibility seems to contradict this goal. To illustrate, many of the klippy.logs we encounter (even from no…