Probed range tolerance Z-tilt

Hey all--

I have had my Q2 for about 4 months just learning a bit. A few days ago I thought I'd give OrcaSlicer a try. I started noticing my prints were taking a very long time to get started.

Starting yesterday all my attempts to print have been stalled at initiation. I switched back to QidiStudio and have been able to get past the initiation and begin printing.

OrcaSlicer is just hanging at this "Retries:0/2 Probed Points range:" section of the console output. When I switched to the Qidi slicer, the process will continue and do a z-adjustment and and proceed to printing. I haven't seen this before in the console.

15:10:33 // probe at 10.000,137.002 is z=0.024531

15:10:34 // probe at 10.000,137.002 is z=0.026094

15:10:39 // probe at 260.000,137.002 is z=-0.136563

15:10:41 // probe at 260.000,137.002 is z=-0.139688

15:10:41 // Making the following Z adjustments:

// stepper_z = 0.111664

// stepper_z1 = -0.084470

15:10:41 // Retries: 0/2 Probed points range: 0.163438 tolerance: 0.050000

15:10:45 // probe at 10.000,137.002 is z=-0.080843

15:10:47 // probe at 10.000,137.002 is z=-0.078811

15:10:52 // probe at 260.000,137.002 is z=-0.082874

15:10:53 // probe at 260.000,137.002 is z=-0.079905

15:10:53 // Making the following Z adjustments:

// stepper_z = -0.009671

// stepper_z1 = -0.011537

15:10:53 // Retries: 1/2 Probed points range: 0.001563 tolerance: 0.050000

To me, this seems like my z-tilt is off, but I'm not sure why Orcaslicer gives up.

From the output-- I feel like I get what the code is doing. It has measured the z-tilt out of spec, and then can make the proper adjustment and on the retry the left and right side of the platform are within tolerance.

I assume it is correct to that this z-tilt check needs to occur each run. Any idea on why Orcaslicer just stops once it discovers the out of tolerance tilt?

This is just coincidence that I'm having this issue with Z-tilt when trying a new slicer, right? People are constantly saying to switch over, so I assume this is user error!

Thanks!