Search the Community
Showing results for tags 'gbuffer'.
-
Hi Everyone, While implementing a custom fisheye renderer I had some interesting ideas regarding screen space effects. Our fisheye rendering works similar to the panoramic rendering of Unigine: We create several images in various directions and stitch them back together. Here is an image of the Unigine panoramic rendering to give you a feeling of how the process works (I deliberately left SS effects on to make the different images visible): Since the different images are created independently, all screen space effects need to be disabled. Leaving them enabled leads to artifacts like in the image above or as discussed here: This got me thinking: Instead of just combining the final images, would it be possible to stitch together all GBuffer Textures and then do the lighting on the combined GBuffer? I think the expensive part of fisheye rendering is creating the different images, not stitching them together so maybe this approach would even increase performance since you only need one lighting pass. However, combining all GBuffer textures might outweight the improvement. And the biggest impact would be to enable some screen space effects again. I think especially things like tonemapping and bloom could work well, maybe even SSAO. Other effects would not work due to our GBuffer not being "linear" anymore so anything like SSR or SSGI would still not work I think. This would need quite some fiddeling with the rendering pipeline so before diving into this I wanted to ask Unigine: Is this something you have thought about and decided against? If so, for what reason(s)? And if not, what are your thoughts on this? Are there more problems to be expected, that I'm not thinking about? And of course: If anyone else has any thoughts on this, feel free to share them here! Kind regards
- 2 replies
-
- fisheye
- screen space
-
(and 2 more)
Tagged with: