OTOY Forums

coilbook wrote:

paride4331 wrote:Hi coilbook,
I don't think I understood, did you export 2 VDBs (one from PhoenixFD and one from Embergeen) and import them into 3dsMax?
Regards
Paride

Hi Paride,

The top image is phoenix simulation with octane volume modifier added. The bottom is embergen vdb. It seems that phoenix never looks smooth and always looks pixelated.

Hi coilbook,
Could you share your PhoenixFD simulation?
Regard
Paride

This version is strange. Sometimes itoo won't render for the first frame, sometimes the screen flickers only one side (maybe coherent option issues or network rendering).

In the image attached (frame 2) the concrete floor circled on the right has strange diagonal lines.
Unfortunately, I cannot share the scene. Hopefully you'll find the bug.

Opening octane viewport and then rendering again fixed it.
I wonder if slaves don't contribute correct rendered data.

PS A lot of the times we have to go to support>refresh itoo legacy forest. Otherwise it wont render. Direct forest is too slow at evaluation each frame.

coilbook wrote:This version is strange. Sometimes itoo won't render for the first frame, sometimes the screen flickers only one side (maybe coherent option issues or network rendering).

In the image attached (frame 2) the concrete floor circled on the right has strange diagonal lines.
Unfortunately, I cannot share the scene. Hopefully you'll find the bug.

Opening octane viewport and then rendering again fixed it.
I wonder if slaves don't contribute correct rendered data.

PS A lot of the times we have to go to support>refresh itoo legacy forest. Otherwise it wont render. Direct forest is too slow at evaluation each frame.

Hi coilbook,
Could you perhaps partially share the scene with the simulation containing the error by sending me a private message?
Regards
Paride

coilbook wrote:This version is strange. Sometimes itoo won't render for the first frame, sometimes the screen flickers only one side (maybe coherent option issues or network rendering).

In the image attached (frame 2) the concrete floor circled on the right has strange diagonal lines.
Unfortunately, I cannot share the scene. Hopefully you'll find the bug.

Opening octane viewport and then rendering again fixed it.
I wonder if slaves don't contribute correct rendered data.

PS A lot of the times we have to go to support>refresh itoo legacy forest. Otherwise it wont render. Direct forest is too slow at evaluation each frame.

Hi coilbook,
try checking the 'minimize net traffic' and 'static noise' options in your Kernel panel.
Regards
Paride

coilbook wrote:For some reason VISIBLE ON SCATTERING doesn't work when you use octane daylight volume. Noisy volume light still shows up.

Hi coilbook,
I'm imvestiganting about this.
I'll let you know asap.
Regards
Paride

Hi coilbook,
I am able to reproduce your issue using .vdb, but not using the daylight environment.
Could you please share your sun, your medium node assigned to it, and the light source that creates the issue?
Regards
Paride

Rik wrote:Is something up with the octane live db?

When I import a material there are no texture maps.

Seems to be ones in OTOY-Absolute textures-Brick plus a few others in Absolute textures

Hi Rik,
LiveDB has an ongoing issue in the current version of OctaneRender 2022.1.1 regarding LiveDB textures. This is an issue affecting all plugins.
The issue will be fix in the next stable release.
Regards
Paride

Hi paride. Thanks for the update.

I'll send the scene soon. When using rail clone with (gradient texture)random color colors change every frame on rail clone objects.

It flickers these colors because we had different shades of red and white.

paride4331 wrote:Hi coilbook,
I am able to reproduce your issue using .vdb, but not using the daylight environment.
Could you please share your sun, your medium node assigned to it, and the light source that creates the issue?
Regards
Paride

Hi Paride,

I will send it soon. Thank you