MotionBlur Tweet

[face]

Only a quick test.
It´s also not perfect but shows the right way...

face

[rgigante]

Congrats Stephan! Well done!

[face]

More MB and ICE generated UV´s to read it from tools like emPoligonizer/Topolizer...

[vimeo]http://www.vimeo.com/79406559[/vimeo]
face

[PeterCGS]

Funky Great stuff!

[face]

The problem you will become with self generated UV´s is when you subdivide your mesh.
That´s because the uv´s vectors are only another selfmade value array in an ICE-Tree and will not subdivide.
You will become then a different between needed and used UV-Values...

face

[OneBigTree]

Glad to see mblur on it's way. Well done!

[bb3d]

Wait... you implemented object motionblur, although Octane does not support it yet?
And are those cubes instances? Will 1.02 support instances finally?

[face]

Wait... you implemented object motionblur, although Octane does not support it yet?
And are those cubes instances? Will 1.02 support instances finally?

It´s only a fake MB.
It combines the last and the current image together. This combined image will then used as the base for the next combine.
It isn´t so good as an average of a image sequence, but you haven´t to store all images in memory.
Which can be much heavy on a resolution of 8192px x 8192px and 32 sample images.
It´s also only WIP because i have some problems to make it working. For now it uses only 8bit.

The cube sequence uses the emTopolizer to make a single mesh.

For now i have to convert the plugin to work with the current SDK.
Also the new mapping modes must be implemented in the shaders and the code generation.

face