Enhance FOV with Panini projection mode

[bananakid]

It came to my knewledge that the proper FOV handling implementation is Panini projection mode, which is different from what is in Quake/vkQuake:

This YouTube video explains Panini projection very well.

Blinky proof-of-concept has implemented Panini projection mode (among others) for TyrQuake, so it looks like it can be ported to vkQuake with reasonable resources. I tried the proof-of-concept and and the imprevement over generic FOV is there indeed. FTE QW features Panini projection mode as well.

[PanucciMetalhead]

I also like this feature. FTEQW has it too, but the engine has more issues than I can count that I stopped playing around with it altogether. I don't think adding this feature deviates from vkQuake's keep-it-clean principle.

[vsonnier]

I looks interesting, but not at all fitted for the vkQuake renderer (performance-wise or other). So, no.

[Novum]

I would at least consider it. I don't think we are actual fillrate bound on any halfway decent hardware so overscan for Panini isn't that expensive? Otherwise it's similar to what the water warp shader already does.

[PanucciMetalhead]

I would at least consider it. I don't think we are actual fillrate bound on any halfway decent hardware so overscan for Panini isn't that expensive? Otherwise it's similar to what the water warp shader already does.

Thank you, @Novum !

[PanucciMetalhead]

If anyone is interested, I've implemented this feature on my fork (https://github.com/PanucciMetalhead/vkQuakePlus/tree/dev). I think I've got the warping correct, but the rendered image becomes more and more "blocky" as FOV increases past 130. I'm looking into supersampling as a solution, but I don't know if this is the best way to go about it. I'm open to feedback and suggestions.

FOV 130, Panini disabled. FOV 130, Panini enabled. FOV 170, Panini enabled.

[bananakid]

This is huge! Hopefully someone helps to complete the effort!