![\"screen396\"](\"http:\/\/www.spellcasterstudios.com\/wp-content\/uploads\/2015\/01\/screen396.jpg\" "\\"screen396\\"")
<\/a><\/p>\nFinally figured out what was the problem with my reconstruction of the position from the FOV and depth\u2026<\/p>\n
NOTHING! ABSOLUTELY NOTHING!<\/p>\n
The problem was way before that\u2026 For some reason (and I never noticed it for years on end), I was using the field of view parameter as the VERTICAL field of view, scaled by half (for some another really unknown reason), but everything I made with shaders that required the field of view assumed I was using the fov property as the HORIZONTAL FOV\u2026 The scaling factor I had only screwed up everything\u2026 <\/p>\n
So I was looking at at a scene with a FOV property set to 80\u00ba\u2026 But since I was diving that scale by 2 (yielding 40\u00ba), and then computing the horizontal FOV from it by dividing by the aspect ratio (yielding 71\u00ba), the visual result was close enough for me never to suspect a thing\u2026 <\/p>\n
Except when I\u2019m actually using the fov in another calculation on a shader and nothing seems right\u2026<\/p>\n
What helped this revelation was the fact that I decided to change the way I was seeing the error on screen\u2026 Instead of using colors, I decided to compute the world position and compare that with the depth I had on the depth buffer\u2026<\/p>\n
The two images below show the \u201cnormal\u201d result (the one rendered correctly), and the one that the SSAO would compute half-way through the process:<\/p>\n