Search Issue Tracker
By Design
Votes
0
Found in [Package]
trunk
Issue ID
1413494
Regression
No
[HDRP] Realtime shadow appears and disappears when slightly moving light object
The bench seen in the videos loses its shadow when I move my lights by 2 millimeters(video). The light is not blocked by anything. I can not understand why the shadow is disappearing, apologies if its by my mistake. This project is using APV but you dont have to bake to reproduce the issue.
Repro:
1) Download Spotlight project, APV branch. https://github.com/iM0ve/Spotlight-HDRP/tree/APV
2) Open main scene (day or night not necessary)
3) Navigate to the light above the bench
4) Optionally - disable all other lights
5) Optionally - disable all emissive lamp objects
5) Select the light and change shadow to refresh every frame
6) Change Y position from 4.1 to 4.03
Result: Shadow appears
Expected: Shadow should always be visible
Also the shadow appears if I change spotlight resolution from 512 to 1k. Tried investigating with punctual light debug, but it looks like the atlas doesnt look different
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
It is simply an aliasing issue, when the shadow cone is so large the amount of texels that each object occupuies is very limited and therefore aliasing happens. In this case the position is just an unfortunate one. This makes the process miss the occluder and it is so delicate that you can see how even changing biases will lead to a different result.
Generally in this cases I'd suggest either using a custom spot angle or increase resolution.