Hybrid motion blur
[media]http://vimeo.com/54064796[/media]
I have been lucky enough to be working with Brian Burrell's Mi-27r model over the past month.
It has been incredibly useful in finding some holes regarding common game asset development patterns.
brianburrell.com/3dper_mi27r.html
This video (and still image) is a look development, effects and animation proof of concept pass for a small realtime effects demo that I'm planning to complete early in the new year.
It demonstrates a new type of hybrid motion blur using geometry shader fin extraction and image space motion blur paired together.
While there are still undesirable artifacts to fix I wanted to make it public to show a "proof of concept" of the idea that I will be writing about further in the coming months.
The motion blur is a hybrid of geometry shader fin extrusion and the recently published reconstruction filter for plausible motion blur)
http://graphics.cs.w...otionBlurI3D12/
Click here to view the iotd
Pixels are not little squares (and voxels are not little cubes).
http://alvyray.com/Memos/CG/Microsoft/6_pixel.pdf
http://www.github.com/derkreature
https://vimeo.com/mdavidsonflux
![:)](http://public.gamedev.net//public/style_emoticons/<#EMO_DIR#>/smile.png)
This is caused by bad transform interpolation through a looping animation.
To fix this I have to rethink some parts of my scene graph and animation system.
Pixels are not little squares (and voxels are not little cubes).
http://alvyray.com/Memos/CG/Microsoft/6_pixel.pdf
http://www.github.com/derkreature
https://vimeo.com/mdavidsonflux
Interesting. I'm very curious how you're combining the two techniques, and what tradeoffs you're making. I'm guessing that you're trying to increase quality via the geometric technique, while still retaining some of the performance from our image-space algorithm?
Yes. The geometry technique fills in areas that would otherwise be unshaded, while your algorithm gives me the cues for blurring.
The geometry stage uses an OIT technique similar to the linked list algorithm presented by AMD a couple of years ago.
Pixels are not little squares (and voxels are not little cubes).
http://alvyray.com/Memos/CG/Microsoft/6_pixel.pdf
http://www.github.com/derkreature
https://vimeo.com/mdavidsonflux