Yeah, that’d be alright. I have plenty of time to check it out. There were a few other things I was going to suggest. I’ll suggest them so it’s easier to discuss if I find a solution while checking the scene and trying things.
-
Reduce DistanceField Trace DIstance (this setting is to ensure huge meshes have their shadows completely drawn, or for extended shadows like in low-angle sun conditions to get fully rendered). 100,000 is enormous and would be for a mountain’s shadow. Not even Godzilla’s shadow is 1 kilometer long! lol
-
I’m not sure what the project is for, but a far shadow distance of 800,000 sounds too large. I’d think the camera is rarely viewing the scene at a far distance of 8 km (800,000 cm / 100 cm = 8,000 m = 8 km…based on 1 Unreal unit = 1 cm). Perhaps 200,000 at the most. If it’s rendering the shadows at 8 km in the distance, then it is probably causing a performance hit or using up a ton of memory.
-
Adjust (on directional light) the Shadow Bias and Shadow Slope Bias. These settings, afaik, affect where a shadow starts from its shadow-casting object and somewhat how it looks. Slope Bias for shadows is meant to fix problems on vertical, curved, and angled surfaces. So grass fits that description, and might be drastically affected by the Slope Bias setting if it’s wrong or off.
Post a link to the download of the scene file / project file, and I’ll open it in 4.25. I have to download and install 4.25 (currently using 4.24.2), but I was going to do it soon. It is possible it’s a bug in 4.25, but that’s still being looked into for fixing similar issues by others in the forum.