I was playing with a pseudo-isometric camera style (low camera Field of View) with a larger camera distance to give it a 2.5D feeling but still maintain some perspective.
Anyhow, I’m not sure if this is a bug or if I need to change the way my lighting is being handled in the scene. When the camera distance (being driven by the SpringArm in the Blueprint) exceeds about 6500+ units all of the cast shadows seem to completely disappear or are not being rendered or registered. However, by just lowering the camera distance back down below 6000 units, they pop right back in. This can be seen in real-time while playing the game demo.
Would love to hear any suggestions on how to make this work without having to have a closer camera distance.
EDIT - RESOLVED
Some gathered notes that help me solved this problem (thanks everyone!):
When using Stationary or Movable Lights on a movable mesh (not static) the shadow visibility of that movable mesh is dependent upon the size of the mesh and its distance from the camera.
Command Line Values to Tweak:
r.Shadow.FadeResolution - controls how big the light has to be on the screen before it starts to fade out.
- Default Value: 64
- Can lower this value to keep shadows from fading out at further distances
r.Shadow.MinResolution - controls how big the light has to be on the screen before it finishes fading out, at which point it no longer has cost.
- Default Value: 32
- Lower values seem to increase shadow visibility.
r.Shadow.TexelsPerPixel - Causes a higher resolution to be assigned and then it should fade out less aggressively
- Default Value: 1.27324
- Can increase this value to improve shadow rendering visibility & quality
- Default Value: 0.03
- A lower value of 0.02 or 0.01 greatly increases shadow visibility at far camera distances (seems to have the most impact of all the console commands).