Extend Render option
I have observed that with Eevee only the geometry of the part of the model that is in the viewer is generated. This causes image errors to appear on the edges of the image in the form of lights that should not appear. A halo also appears around the edges of the image (white in this case)
In the 3D viewer we have this problem solved by being able to extend the field of vision beyond the limits of the camera.
Is it possible to implement an option to extend the geometry load even if only the vision of the camera is rendered?
A slider that indicates the amount of viewing angle that is added to the render calculation (not the output image) could be a good implementation.
I attach an image indicating the problem that I observed.
6 Comments
I was going to make this exact proposal a while back, but I was having trouble making images to demonstrate the phenomenon.
The issue has nothing to do with geometry; it's caused by how post-processing effects are handled in screen space. There is no pixel data beyond the edges of the rendered image and, as a direct result, visible artifacts occur when post effects need information from off-screen, like reflecting a surface that's out of view.
Looking at your image, I'm not sure if the issue is being caused by contact shadows (a post effect) or the directional light shadow map (which would be a frustum positioning issue). If it's the latter, this should be a bug report, as this is something that should never happen with robust frustum culling, period.
If the problem is indeed related to screen-space effects, the best solution would be to provide an option to render with an expanded border beyond the edges of the render area which will be automatically cropped off when rendering is complete. This way, the edge artifacts will occur outside of the render area.
@quargzon: that technique is called overscan. there is an extension, I hope the port to 2.8
wiki.blender.org/index.php/Extensions:2.6/Py/Scripts/Render/Camera_Overscan
@Antonio Navarro Blaya: I agree. This is something that I see as a must-have feature for Eevee. The blatant edge artifacts are a major shortcoming of an otherwise well-made renderer with massive potential.
Not sure if it's pertinent to make suggestions about an "in development" feature, not even in pre-alpha. Yes ?
@loic.dautry: As long as they're feature requests and not bug reports, it should be fine. After all, this is probably the best time to make these requests -- while the technology is still brand new and "malleable", as opposed to going back and painstakingly changing it later.
The devs are all working together and focusing on this particular area right now, so things can get done quicker and more thoroughly, and important workflow issues and user suggestions can be addressed before its initial release.
Besides, it's not like developers have to implement EVERYTHING they see on here. If they don't add it, they don't add it, and life goes on.
@quargzon: exactly, it's only a proposal.