V-core 3 still probes full bed after enabling adaptive meshing

I’ve enabled adaptive meshing in printer.cfg and added the start print macro in the slicer (and confirmed that it makes it into the gcode with proper bounding box values), but the printer always probes the entire bed. Did I miss a setting somewhere?

blacksmithforlife•12/20/23, 1:39 AM

upload your printer.cfg

ordinary-sapphireOP•12/20/23, 2:10 AM

printer.cfg15.92KB

blacksmithforlife•12/20/23, 2:54 AM

is set to false

ordinary-sapphireOP•12/20/23, 2:59 AM

yeah because it takes too long. When it’s set to true it does the whole thing regardless of the model

blacksmithforlife•12/20/23, 4:48 AM

What slicer are you using?

ordinary-sapphireOP•12/20/23, 4:49 AM

superslicer

blacksmithforlife•12/20/23, 1:21 PM

what do you have as your start print gcode?

blacksmithforlife•12/20/23, 1:21 PM

ordinary-sapphireOP•12/20/23, 9:53 PM

yes, I have exactly that, and it produces reasonable-looking numbers in the resulting gcode

ordinary-sapphireOP•12/20/23, 9:53 PM

blacksmithforlife•12/20/23, 9:56 PM

can you upload the gcode file?

ordinary-sapphireOP•12/29/23, 8:09 PM

update on this - it turns out I had left the ADXL tuning block uncommented but without the accelerometer attached, and for some reason that was interfering with adaptive mesh. Now that I commented the accelerometer blocks put it’s working.