OctaneRender® 2022.1.1

[john_otoy]

If I render my groom (curves) and I disable shadow viibilty, my render becomes 35 times slower. (I render with path tracing kernel and alpha shadows on)

Thanks for the report

[PolderAnimation]

Looks like the ray switch 'diffuse' function does not work properly any more. If I try this old orbx file it does not look that same as milanm example.

viewtopic.php?f=30&t=67849&fbclid=IwAR0 ... gwWv7LepTE

file does not work in 2021 and 2022 but does show good results in 2020.

[frankmci]

Looks like the ray switch 'diffuse' function does not work properly any more. If I try this old orbx file it does not look that same as milanm example.

viewtopic.php?f=30&t=67849&fbclid=IwAR0 ... gwWv7LepTE

file does not work in 2021 and 2022 but does show good results in 2020.

OSL has changed a bit since Milan's script. Check out Raytype.OSL and RaySwitch.OSL now included with Octane for similar functionality.

[john_otoy]

Looks like the ray switch 'diffuse' function does not work properly any more. If I try this old orbx file it does not look that same as milanm example.

viewtopic.php?f=30&t=67849&fbclid=IwAR0 ... gwWv7LepTE

file does not work in 2021 and 2022 but does show good results in 2020.

Thanks for the scene. We'll look into it

[J.C]

Hi, I've noticed an issue when using Standard Volume Medium in animated VDBs that has temperature and density channels. When "Autoscale temperature channel" is enabled temperature channel flickers every few frames.

[john_otoy]

Hi, I've noticed an issue when using Standard Volume Medium in animated VDBs that has temperature and density channels. When "Autoscale temperature channel" is enabled temperature channel flickers every few frames.

Can you PM me and provide a scene we can look at?

[J.C]

Hi, I've noticed an issue when using Standard Volume Medium in animated VDBs that has temperature and density channels. When "Autoscale temperature channel" is enabled temperature channel flickers every few frames.

Can you PM me and provide a scene we can look at?

This looks like C4D plugin issue. I've sent PM anyways.

[SSmolak]

Fallow parameter in Field texture works fine for regular SDF primitives but it clamp values over 1 when used other objects as Mesh to SDF enabled. Please see attached video.

[john_otoy]

Fallow parameter in Field texture works fine for regular SDF primitives but it clamp values over 1 when used other objects as Mesh to SDF enabled. Please see attached video.

Can you export the scene to ORBX and PM me please?

[jobigoud]

Fallow parameter in Field texture works fine for regular SDF primitives but it clamp values over 1 when used other objects as Mesh to SDF enabled. Please see attached video.

I think I know what's going on, based on the video.
When using Mesh to SDF ("Mesh volume SDF" node) the original mesh is voxelized and the distance to the surface is put in the voxel values. However, the resulting Volume SDF object doesn't have valid values everywhere in space, but only a certain distance away from the original surface.

There is a parameter in the import/conversion settings at the top called "Border thickness (voxels)", this represents how far from the original surface the distance value will be known. When the Shape field evaluates a point that is outside this border reach, it will read a static "background value" instead of the true distance to the surface. That's why it's acting weird.

Try increasing the border thickness and see if that improves things.

(In the case of regular SDF primitives the distance is calculated with a function so it can be known at any arbitrary point in space).