Understanding Aperture Diffraction
Posted: Mon Jul 20, 2009 2:25 am
Hi guys. I have some questions about aperture diffraction as well as a possibly naive suggestion.
Whilst trying to wrestle a clean and accurate render of my rings scene I have started asking myself questions about aperture diffraction as it is implemented in indigo and how it compares to the real world.
So far whenever I use AD my renders get blurred. They always seem slightly out of focus. Now in the real world where AD is always in effect it is quite possible to have completely sharp images but also having the hot spot "flares" caused by AD so why does indigo seem incapable of achieving the same?
I was also thinking about obstacle maps, in particular the generated blades. At present you can customize the blade generation to suit yourself however I would have thought that the generated size of the opening would be directly tied to F Stop and so therefore would be automatic because the generated blade obstacle map is meant to be representative of the internals of a real camera right? Now this may be complete ignorance on my part and maybe this is already the case but was wondering if a mismatch between F Stop and the size of the opening in a generated obstacle map might have something to do with this blurriness problem...?
Whilst trying to wrestle a clean and accurate render of my rings scene I have started asking myself questions about aperture diffraction as it is implemented in indigo and how it compares to the real world.
So far whenever I use AD my renders get blurred. They always seem slightly out of focus. Now in the real world where AD is always in effect it is quite possible to have completely sharp images but also having the hot spot "flares" caused by AD so why does indigo seem incapable of achieving the same?
I was also thinking about obstacle maps, in particular the generated blades. At present you can customize the blade generation to suit yourself however I would have thought that the generated size of the opening would be directly tied to F Stop and so therefore would be automatic because the generated blade obstacle map is meant to be representative of the internals of a real camera right? Now this may be complete ignorance on my part and maybe this is already the case but was wondering if a mismatch between F Stop and the size of the opening in a generated obstacle map might have something to do with this blurriness problem...?