KAMP prints purge line under supports in Orca

[shirgall]

K1 Max w.1.3.3.26 firmware, factory install, w/script+enough stuff to run KAMP:

Some of my complex objects need tall support, which Orca w/auto Trees with default settings go all the way to the bed, but when those supports go "south" of the object, they can intersect with the KAMP purge line, leading to poor integrity for that support or set of supports.

I can rotate the object and not have an issue, but I figured I should document this in case others have seen it.

[shirgall]

"KAMP uses information from [exclude_object] to define mesh bounds. Complicated slicer parameter passing is finally a thing of the past. Welcome to the future!"

Perhaps this is an issue with exclude_object parameters?

[shirgall]

I discovered I did not have "Label Objects" enabled, but enabling that did not correct the problem.

[Guilouz]

Read the wiki.

[shirgall]

Yeah, I have, but I've not had to adjust the margins before. Either because I factory reset and installed everything fresh with the new firmware, but I've never needed to set the variable mesh margin before. Live and learn. Thanks for all of the scripts!

[robomopa]

I also got this problem. Is it possible to set the classic purge line default, so users that dont want the adaptive purge wont need to select from fluidd after each power-on/off cycle

[JooJooBee666]

I have the solution!

In Fluid, open the configuration menu and browse to the /Helper-Script/KAMP folder and edit the KAMP_Settings.cfg file. Look for the following line:
variable_purge_margin: 10 # Distance the purge will be in front of the print area. Default is 10.
and change it to something like:
variable_purge_margin: 50 # Distance the purge will be in front of the print area. Default is 10.
B00M! No more tree base f**kery!