Page 1 of 1

Image Sequence as Displacement Map issue

Posted: Wed Jun 11, 2014 12:11 am
by jhinrichs
Noticed a couple issues while testing the Modo Octane Plugin. (specifically when trying to render RealFlow data)

1.) I exported a 16 bit .tif image sequence from Realflow. I had success applying the displacement to a single polygon plane when using a single image, but if I try to use a image sequence Octane doesn't appear to recognize it. When using the image sequence the animated displacements appear in Modo but Octane just shows a flat plane. I set the mesh to Cage and I unclicked the "Load All Frames into Modo and still nothing. I tried to recreate the nodal structure in the node window, but when I drag the image sequence over there is no "Output" like there is if I drag a single image over. Are image sequences supported in Octane Modo?

2.) The meshes created by emReader (a plugin for creating meshes in Modo from RealFlow data) aren't recognized by Octane.

Re: Image Sequence as Displacement Map issue

Posted: Wed Jun 11, 2014 12:30 am
by face_off
Hi

1) TICK Reload Materials Each Frame and UNTICK Load All Frames Into Octane. And don't Override the material with the displacement map. That should trigger the plugin to do an on-the-fly conversion of that displacement material each animation frame, so it should pickup the displacement sequence. I haven't actually tried this myself - so if that doesn't work, pls send me the scene and image sequence and I will take a closer look.
2.) The meshes created by emReader (a plugin for creating meshes in Modo from RealFlow data) aren't recognized by Octane.
Can you pls send me a sample scene with one of these meshes and I will investigate.

My email is paul at physicalc-software dot com.

Paul

Re: Image Sequence as Displacement Map issue

Posted: Wed Jun 11, 2014 9:27 pm
by jhinrichs
I'm not getting it to work. The 'Reload Materials Each Frame' only seems to be available (not greyed out) when 'Load All Frames into Octane' is checked.

I'll see if I can create an example with a couple of images and email it off.

Same with the emReader deal. I had a conversation with a Next Limit person. He assured me they were working with Luxology to get Realflow Alembic to work with Modo. That would be a better solution and would alleviate the emReader issue.