-
-
Notifications
You must be signed in to change notification settings - Fork 21.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shadows disappear at certain viewing angles with distant camera far plane #91753
Comments
I let git bisect do it's thing and it found this commit: With that commit shadows start to disappear. |
Here's the workaround I'm using now,. It's terrible, don't commit.
|
cc @lawnjelly |
Likely duplicate of #89560 , so may be fixed already. |
Tested versions
Reproducible in: v4.3.dev.custom_build [7ebc866]
Not reproducible in: v4.3.dev.custom_build [51991e2]
Regression introduced in: v4.3.dev.custom_build [4577dfd]
System information
Ubuntu 24.04 LTS - Vulkan (Forward+) - reproducible with both Intel IGP and NVIDIA dedicated
Issue description
If the Camera3D far plane is set to something high like 1e5..1e6, shadows disappear at certain viewing angles either completely or partially. The affected angles are narrow, but once found and the camera stays put, shadows can stay off indefinitely.
Shadows may disappear partially. In my project, trees (MultimeshInstance) are often unaffected, but not always, while all vehicles and terrain lose their shadows regularly. Where shadows disappear they all disappear at the same time, no matter the object type or distance.
Shadow settings seem to have no influence on this. The only setting that I found to have an impact is the camera far plane:
far = 4000 (default) -> cannot reproduce
far = 1e5 -> can reproduce at few angles
far = 1e6 -> can reproduce at many angles
I happen to need at least 1e5, better 1e6, else the clouds don't render right.
Steps to reproduce
look for whole walls flashing bright white
Minimal reproduction project (MRP)
disappearing_shadows_example.zip
The text was updated successfully, but these errors were encountered: