Now that in 5.4 with Virtual Shadow Maps, we have the option to override the behavior for shadow invalidations per primitive, while using separate static caching we still need to consider the mobility of the actors or with this new feature we just can rely on setting the Shadow Cache Invalidation Behaviour?
I believe separate static caching is now the default behavior.
The cache invalidation behavior is meant to solve different problems. It will help reduce cache invalidations when used correctly, or force invalidation when needed.
But the separate cache is meant to prevent objects that generally must be dynamic, such as characters or animating foliage, from invalidating a bunch of static geometry shadows. This case is not helped by the new behavior setting, since these types of objects cannot use non-invalidating behavior without causing visual artifacts.
That makes a lot of sense, thank you for answering my question @BananableOffense !! Really helpful
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.