This is a known issue and from our tests it is not just dependent on shadow cascade count but rather on the shadow distance which adjusts the quality of the shadow detail (not just bias) regardless of the cascades. You can have 1 cascade and still have the issue pop up once you adjust the shadow distance for that shadow detail quality. And once you get to the sweet spot when you think the shadow distance/quality is just right you will have the issue visible as a consequence (note by quality I don’t mean “shadow resolution” but rather the amount of detail in the geometry that the shadow map catches). From all our discussions and posts the problem hasn’t gone away unfortunately.