urgentish.. help, NEXT GPU, motion blur / tyflow / frost / vrayproxy

[super gnu]

ive got a lovely particle sim done in tyflow (amazing) beta. drippy water thing, so changing topology.

i really want to render in next GPU cos its SOOOOO much faster for this scene. (like 10x faster)

vray metaballs is out for this reason..



my client has frost, so im trying that, with the idea of exporting to vrayproxy after so i can use it here.


it renders fine and fast in rt gpu... BUT.. i get no motion blur on the mesh.

if i export to animated proxy, i get no moblur on that either.

ive tried the different moblur settings available in the frost interface... none of them seem to make a difference.


strangely, if i set up that "multipass" motion blur on the max camera, and hit preview, frost will happily generate subframe samples and do a nice blur in the viewport.

however a) im not making my renders take 12-16x longer by using that, and b) it doesnt seem to work properly with gpu anyway.


i have an issue which may be related, where tyflow is recalculating the whole sim multiple times before rendering each frame., despite having it cached to ram.. im discussing this with Tyson now..




somebody please tell me how to get this mesh, rendering in rt gpu , with moblur?

[super gnu]

nobody? is it possible to get decent moblur on some kind of cached mesh with changing topology in next gpu? if so, how have people done it..

if its possible this suggests its a tyflow issue..

when i render the frost mesh in next CPU, the "subframe" moblur method works, although it kills rendertime and ram, since i need at least 10 mesh samples to get a reasonable result.

even on Next CPU the "frame velocity" moblur method does not work.

in any case im going to need to export to vrayproxy or alembic anyway, since i dont have frost.

[matanov]

Unfortunately if the mesh maker doesn't provide velocity information, we can't do anything.

[super gnu]

Unfortunately if the mesh maker doesn't provide velocity information, we can't do anything.

so you think its likely that tyflow is not baking velocity information into the frost object? if so ill pass that pointer on to Tyson.

[matanov]

Yes. We will contact him as well.

[bob dobbs]

Peter and Co, has anyone come to a method of passing velocity info from TyFlow particles to Vray instanced (or otherwise) meshes? There is a .PRT export with velocity channel, but how would this and other particle information pipe into VRay? Might there be a way using PhoenixFD to capture velocity info?

[georgi.zhekov]

Hey,

If you just add Mesh operator to your particle event and choose the "VRay Instances" option - the particles should render with motion blur.
Does this work for your case or you need something more specific?

[bob dobbs]

The goal being to apply displacement to some meshes via multi-sub object material and vray displacement mod set to 'use obj material' with motion blur being rendered in camera for an animated sequence.

The issue is compound: tyflow mesh: vray instance/triangle mesh, vrayDisplacement Modifier use texmap/obj material and vray IPR/Production render. Image attached, shows that moblur can be achieved with tyflow mesh operator set to triangle mesh or vray instance. This changes depending on whether the render is IPR or if I send it to the farm for production rendering.

Little particles not being great for Nuke vector blur due to occlusion, etc. Is there any way to receive particle velocity data through .PRT (or otherwise) in Nuke, or render these meshe's velocity data in Nuke? Sorry if I am over-complicating this or missing some part of the process.

Edit: Maybe I am over-complicating this, it seems to work after sending the particle flow to a TyMesher.. still testing though