you checked it? even so this does not work.miko3d wrote: just make sure the mesh has the velocity "v" point attribute exported in the alembic file.
I don't understand why there is no clear answer from the developers, will this work and if so when?
you checked it? even so this does not work.miko3d wrote: just make sure the mesh has the velocity "v" point attribute exported in the alembic file.
We don't have Realflow, so we don't know which export options it has for Alembic. If it can export vertex velocities, Octane can render vertex motion blur, if it doesn't then there is nothing Octane can do since the topology (and the vertex list) changes from frame to frame, i.e. there is nothing to interpolate.mikinik wrote:you checked it? even so this does not work.miko3d wrote: just make sure the mesh has the velocity "v" point attribute exported in the alembic file.
I don't understand why there is no clear answer from the developers, will this work and if so when?
Sorry, I don't understand your question.mikinik wrote:thanks for the reply. well, maybe this attribute is not in alembic file. you can do so that could render at least one frame from .bin sequences?
That noise is noise caused by spectral sampling and which will go away after more samples/pixel. Maybe have a look at already existing scenes and investigate how physically based rendering behaves.when I put two checkboxes in movebale proxy and vertex motion blur, octane shows speed in 1 Samp/pix and picture can be seen jittering colored noise during the render. .bin sequence loaded using realflow mesh loader. or you tell me again that you don't have the owners realflow? why other renderers don't have such problems, they bought realflow?
I'll reply in the thread.abstrax, can make please some comment about this bugs or may be this features? http://render.otoy.com/forum/viewtopic.php?f=81&t=45519
How did you verify that there is velocity information?mikinik wrote:that's what I'm talking about. in RFMeshLoader have information about velocity but octane are not rendered vertex motion blur. this is a problem in octane and not more than that. it can be fixed?
here's the error about which I spoke earlier. over time nothing has changed.mikinik wrote: when I put two checkboxes in movebale proxy and vertex motion blur, octane shows speed in 1 Samp/pix and picture can be seen jittering colored noise during the render.
Ok, now I understand. The Alembic file you have sent to me contains only particle information (with velocities) and the RFMeshLoader creates a polygon/triangle mesh from it. The generated meshes do not have that vertex velocity information anymore. We can have a look and try to get it maybe directly from the plugin, but for that we would need to get in touch with NextLimit first.mikinik wrote:here I saw itabstrax wrote: How did you verify that there is velocity information?
Could you give me this scene?mikinik wrote:here's the error about which I spoke earlier. over time nothing has changed.mikinik wrote: when I put two checkboxes in movebale proxy and vertex motion blur, octane shows speed in 1 Samp/pix and picture can be seen jittering colored noise during the render.