Theoretical "Pixel Occlusion" Filtering Method

[Jakeofalltrades]

The idea is that odd or even numbered pixels can be occluded from a rendered frame, and the second frame would compensate by inverting the occlusion. This should, in theory, double your rendering speed by rendering only half of the pixels for each frame, while maintaining full image quality.

 

Here's an example of how a completed frame would appear.

 

 

Does this seem viable to anyone? Discuss.

 

EDIT: Make sure you view the image at it's full size, as it doesn't present an accurate depiction when scaled down.

Edited April 22, 2010 by Jakeofalltrades

[Bruce]

Looks terrible (grainy)

[Jakeofalltrades]

Looks terrible (grainy)

 

Naturally, it's only using half the pixels. The idea is to have a seperate frame for the additional rendering, and in motion, the grain should disappear.

[Bruce]

Should but it didn't did it?

[Jakeofalltrades]

Should but it didn't did it?

 

Wiseguy!

Edited April 24, 2010 by Y kawika

[brandon]

It's impossible to see how it works in a still shot. Though, I don't see it as a very good idea. You'd have to run at double the framerate to get the same amount of pixels, and I could imagine it wouldn't work too well if the FPS drops below 60. And there is also the issue of running multiple GPUs, which could lead to synchronisation issues.

 

Read up on Tile based deferred rendering, Jake. It has a lot more promise, considering it's actually currently used, albeit in the iPhone.

Edited April 26, 2010 by brandon

[Bear]

First thing that came to me is eye strain

 

Bear