Autoleveling seems like a good idea in mattercontrol's implementation. As long as you are not printing full beds. I've found mattercontrol leaves big gaps around the edges when doing autoleveling probes, which leads to poor skirts and first layers near the edges. Until today's update I had 60mm unprobed on the +x side of the bed. Well that is 'fixed'. Now it only leaves 30mm unprobed. Bad news is now the left side probes at x25 leaving 55mm unprobed with my 30mm probe offset in x. why? disappointing in that obviously some work was done on this in the latest update but still left in a confused state.

I have tried using 'custom' under 'autoleveling solution' and have never found any combination of point specifications that have ever probed at all. homes, extends probe, lowers to z10, and stops. cancel works, machine is not hung, just can't be bothered to show an error message.

has anyone been able to make 'custom' work? why can't matter control take a bed size, a probe offset and make intelligent decisions?

@larsbrubaker Hi Lars, when you say 'should be fixed in the current build' which issues from above are you referring t?. I have quit trying to use mattercontrol from my macbook since there are constant usb connection issues. I haven't experienced SD card problems though. Moving to windows those problems have gone away.
I see you are listed on the github matterhackers repository. Are you aware that with a new and current vscode, platformio, and marlinautobuild the repo will not compile. I have brought this up repeatedly with tech support email and have received knowledgable replies only from Taylor, in that 'some libraries' probably need deprecated. Is it unreasonable to expect more details? Could someone there possibly do a new vscode install and document the steps necessary to compile the repo? I can compile repos from Marlin, Prusa, etc with no issues.
Although the pulse mechanically is a good enough printer I am starting to regret my purchase due to lack of useful and even remotely timely responses from tech support and constant mattercontrol weirdness. There are firmware settings that make the printer impossible to use standalone (extrude limits for load/unload for instance) and no documentation on what it takes to succesfully compile the repo. Taylor did get me a hex with the extrude limits properly set, but the speeds still make it mostly unusable. Simple changes if I could compile it. Thanks.

@surfmagic My pulse was spec'd to include a filament out sensor which it did not come with. However the sensor is set to on in printer settings and in mattercontrol. With those on my filament unload from mattercontrol always failed the 1st time, Doing it again always worked. Turn off the sensor in marlin and mattercontrol should solve that problem. you will need to do an m500 to save the setting in firmware. I have found that the load/unload lengths in mattercontrol do work. Load/unload on the lcd screen do not work because the matterhackers firmware has the limits set at 200. I can't currently compile it to change it though. (semi-opensource at best, with vague email responses from you know who)