Octane Properties in Data tab do not work with FlipFluids Tweet

[pegot]

Nether visibility nor OpenSubDiv settings work with FlipFluids. Whatever settings are enabled for the fluid surface automatically get set back to their defaults on the next frame.

In view port mode, only the current frame will be rendered with the correct Octane properties settings. As soon as the play head is moved, the check boxes revert back to their defaults.

And if one initiates a direct render, no frames are rendered with the desired Octane properties - all settings are immediately set back to defaults.

[pegot]

Bump.

Have devs had an opportunity to look into this yet?

[DrawFun]

Hi pegot,

Thanks for your report.
Could you please share me a simple demo to show it? Thanks.
On the other hand, in the next major build(after a stable 16.x), we are planning to have some big refactors about current mesh structures to fix some incorrect or repeating upload in mesh transferring. Hope the refactor would help in such cases.

Cheers,
DrawFun

[linograndiotoy]

I've made a video showing the issue:

https://youtu.be/lInIkCBJ6Iw

We need to understand if this is something requiring the cooperation of the FLIP Fluids developer.

Thanks for reporting it.

[pegot]

Just wanted to know if there was any update to this?

DrawFun, on October 28th you sent me PM saying you reached out to Flip Fluid developer. Any response yet?
It is really difficult to work with and get good results with Flip Fluids in Octane but such wonderful results using Cycles.

[DrawFun]

Hello pegot,

I've got something back from the dev and it is a limitation for now.

The issue is that

Nether visibility nor OpenSubDiv settings work with FlipFluids. Whatever settings are enabled for the fluid surface automatically get set back to their defaults on the next frame.

And here is the reason I got from the dev,

the mesh object data has to be deleted and re-created when loading a new frame and this is why the properties on the mesh data are reset to default values.

Therefore, It is a design conflict between the two plugins.

There is a workaround for exporting the simulation meshes to an Alembic cache. Details for how to export the fluid simulation meshes to Alembic format can be found here: https://github.com/rlguy/Blender-FLIP-F ... ted-meshes
Once the simulation is in Alembic format, you can import the cache into a scene and modify the mesh data. The mesh data settings will be persistent between frames.

Cheers,
DrawFun

[pegot]

Been away from Octane for a bit but now getting back to it and this issue seems to be fixed with the latest 2020.1 RC2 / v21.4 build, Blender 2.82a, and FlipFluids 1.0.8.

I haven’t tested too extensively but the SubDivison settings in Octane Properties were maintained throughout at least 4 frames of a FlipFluids animation without being re-set.

Thanks!