OTOY Forums

thanulee wrote:Hi "spread cutout hardness" does not do anything in analytic lights. It is supposed to feather the edges right?
R6 is great in general!

It's a factor of illumination as I can see, better answer is not on me.

aoktar wrote: Enable linked to dsiable mode of nodes

I don't know where to find, what exactly "linked" ?
To be more precise I thought about composite layer states :

SSmolak wrote:

aoktar wrote: Enable linked to dsiable mode of nodes

I don't know where to find, what exactly "linked" ?
To be more precise I thought about composite layer states :

The attachment layer_state.jpg is no longer available

I'm talking about this icon.
Also don't use the nodes as marked with "legacy", I missed to mark as legacy the "composite AOV output layer". I'll change it for R7.
These nodes are not allowed to be created in 2023.1 Octane Standalone. Only reason to keep these to don't break the backward compatibility.

aoktar wrote: Also don't use the nodes as marked with "legacy", I missed to mark as legacy the "composite AOV output layer".

Thank you for explaining but I was talking not about AOV but regular texture, material nodes I mean regular composite texture inside material nodes.
I know that there is opacity input but opacity = 0% doesn't upload unnecessary texture from VRam. It needs to be disabled by node. If we have a lot of materials with variations inside it would be great to have such enable/disable switch that can be reached as input to other nodes.
Also my post about XPresso was about Octane material too not AOV. I mean that disabling material inputs like Albedo, roughness doesn't work in realtime if it is done in XPresso.

SSmolak wrote:

aoktar wrote: Also don't use the nodes as marked with "legacy", I missed to mark as legacy the "composite AOV output layer".

Thank you for explaining but I was talking not about AOV but regular texture, material nodes I mean regular composite texture inside material nodes.
I know that there is opacity input but opacity = 0% doesn't upload unnecessary texture from VRam. It needs to be disabled by node. If we have a lot of materials with variations inside it would be great to have such enable/disable switch that can be reached as input to other nodes.

comp.jpg

Also my post about XPresso was about Octane material too not AOV. I mean that disabling material inputs like Albedo, roughness doesn't work in realtime if it is done in XPresso.

Same should be valid here what I said, sorry for confusion.
Not pratically possible to do it for opacity=%0.

There are not much for that atm, 2024 is the problem here for my assumption.

aoktar wrote: Not pratically possible to do it for opacity=%0.

There are not much for that atm, 2024 is the problem here for my assumption.

I understand so it is better to make different material versions and do material switch instead.
As for XPresso LV update you did it great for C4D 2024 and it works fine for material nodes, environment, camera tags but for material tag stil doesn't update in realtime and not only for switching channel inputs state but even diffuse color and all other parameters inside Octane material tag.

EDIT :

This enable switch for nodes is great when we have many similar materials and want to edit them globally using material multiselection in C4D - we can edit all parameters for all at once. But without possibility to enable/disable individual nodes inside materials.

If you would add this enable switch from nodes to edit controls in C4D material attribute window it would resolve this problem and add more functionality to edit globally selected materials :
Especially for image node.

SSmolak wrote:

aoktar wrote: As for XPresso LV update you did it great for C4D 2024 and it works fine for material nodes, environment, camera tags but for material tag stil doesn't update in realtime and not only for switching channel inputs state but even diffuse color and all other parameters inside Octane material tag.

Not sure what are you doing with this xpresso, posting one video doesn't help.

Adding enable for different types are not supposed to have(different IDs or lack of this function on many nodes), but I'll add functionality for toggling the enable/disable from nodes menu.

aoktar wrote: Not sure what are you doing with this xpresso, posting one video doesn't help.

Adding enable for different types are not supposed to have(different IDs or lack of this function on many nodes), but I'll add functionality for toggling the enable/disable from nodes menu.

Please see attached video and scene with xpresso issue.

You have "enabled" input visible in C4D Attribute Manager for Composite Texture Layer - why not to do the same for Image node ?

Just one little feedback: I had several C4D crashes in the last weeks, all because of the Anima plugin or problematic CAD data.
None of them was because of Octane - great work, thanks!

SSmolak wrote: - why not to do the same for Image node ?

Because it is not available in core side