Running a pretty high res water and 'sand' (want to simulate matcha) mixing mpm sim. Have the default 10k max substeps on the solver but looking at the detail attribute seeing it's doing ~13k substeps. Is this normal? It's taking a bit too long per frame so curious as to why this is and if there's a way to optimize/clamp it.

Bringing it down to 5k does result in the attribute coming down to ~6k. So it's working but not a hard limit.

Other odd behaviour with the min/max substeps in MPM. Wanted to test some stuff on this same setup with a quicker sim so brought down the max substeps to 2500. The particle separation was lowered though for the test I wanted to do (0.0003).

Noticed the small particlesep with the lower max substeps eventually made the simulation unstable as it would crash at frame 3 (telling me in the error message to try messing with minsubsteps or cfl condition). But, and this what I find odd, putting the max substeps around 3333 (not sure of where exactly, 3333 works) it stabilizes the sim. When looking at the detail attribute of the resulting cache it's because it's doing around 12k substeps. The min/max setup is quite misleading or not being applied correctly...

There should be some warning that the substeps are being pushed way above the setted threshold to stabilize the sim..