-
Notifications
You must be signed in to change notification settings - Fork 259
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
Annoying, Ugly Shadow Lines #237
Comments
Yeah it is the typical shadow mapping acne problem. I couldn't get around 2015-07-22 23:07 GMT+02:00 TyrannWright notifications@github.com:
|
Maybe fixable? |
@TyrannWright I've noticed that BFG seems to have an issue with gamma correction, often colorizing the textures with purple/green tints which is why things seem a bit off, the only way around it is by setting custom gamma settings in the graphics card driver control panel. @RobertBeckebans This artifact also appears in Blender's game engine when using shadows, usually improved when using the variance method and increasing the raycast length as well as sample resolution. Not sure if it is the same for the soft shadows you've written. |
Found something interesting that might help: http://www.dissidentlogic.com/old/images/NormalOffsetShadows/GDC_Poster_NormalOffset.png |
Interesting. Near the end of the article, they spoke of post process filtering. Maybe a cheap blur on the shadow pass? |
any news on this ? |
I suppose shadow bias could be increased in the meantime. This will cause shadows to "peter-pan" noticeably around their caster though. |
i wonder if the completed vulkan renderer could fix this ? |
Vulkan doesn't resolve this in itself. This can also be fixed in an OpenGL renderer by implementing shadow normal offset bias as mentioned above. |
This has been fixed in the new DX12 / Vulkan backends using temporal anti aliasing. |
After the issue of the colored shadows, I'm getting these lines in the shadows that make some characters look ugly and textures seem annoying along with a framerate drop.
The text was updated successfully, but these errors were encountered: