Hyaleah

I just disable "HS mode" in MRISCOC firmware. Whatever it does, there was a note to disable it when using the CR Touch with Meshes denser than 5x5. Second I copied over the start and end Gcode from Creality Slicer over to Cura. Adding in G29 L0 and G29 A. So far two consecutive prints without issue. I was so close to giving up and just installing Crealities CR touch Firmware.

It used to be a recursive error. 1st print I would set the z-offset to -1.11, prints fine, second print I set it to -1.31, third print I set it to -1.51, fourth -1.71, and so on. Each successive print deviates +0.2 from the last. Requiring me to lower it. Lately however that went away and now it's just +0.2 somewhere after the purge but before the actual mesh starts printing. I was wondering why they use G0 instead of G1. I can always append a G0 Z or G1 Z just before the mesh. I thought about the other fixes where they don't use Cura or simply remove the start Gcode. Though I need mine to at least activate my mesh.

Possibly. I'm looking into post scripts in cura that will automatically search out and replace a certain z value. However it's not been a 100% success rate.

Using Cura 5.2.1 with Ender3v2 running Mirscoc Firmware. So I was having this same issue. I noticed I had to lower my z offset after the purge, sometimes after the skirt, usually around -0.2mm so if my Probe Z-offset was -1.00mm I would need to lower it to -1.20mm on every new print. Inside the Gcode I found the only place that altered Z by that amount was G0 F**** X**.*** Y**.*** Z0.2 So I added a post script in cura to search and replace Z0.2 with Z0 and it worked changing the values automatically, however I edited the code and implemented the changes outside of Cura to get the print to work. And the model was initially sliced without adding in supports in Cura. Using supports might alter the effectiveness of this fix as I just tried slicing my model with supports and it doesn't seem to be working. I had to actually raise my Z... so I might need some more tweaking. I disabled tilt mesh as the new meshs it spits out has a ring of values around the perimiter that aren't even close to the inner values. It's guessing is way off and rebuilding and auto mesh returns the same values I already had, so the bed hasn't gone out of alignment.