If one channel of the "instance octane overdrive" > instance is manipulated it also changes the source.
what i would expect is:
change within the instance does not change the source, while change in the source does effect both.
steps to reproduce:(see octane_instanceshort.gif)
create 2 speheres. each with it own material tag. (Left / Right)
create 1 octane override in (Left)
Use "Instance Octane Override" and move it in Material (Right)
change color node within the instanced octane override.
>>> both spheres change color.
-------
see modo_instance as reference how it should be.
i can change the color of the instance only while still change roughness in source for both.
-------
win 11 | modo 17.0v2 | studio+ 2023.1.2.199
Instance Octane Overdrive changes source
Moderator: face_off
This looks like it is working as intended. The Octane Override Instance is a reference to the source Octane Override, so changing the source should change the material for both source and instance. Or have I misunderstood the issue?
Thanks
Paul
Thanks
Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
- sevengreen
- Posts: 14
- Joined: Mon May 30, 2022 11:37 am
Hey Paul,
source should change the instance - correct.
instance should not change the source.
If you look at the modo_reference I've attached, it's clear that I can change the color of the instance independently of the source, but still have the ability to change the roughness for both when using the source.
this is not the case with the "instance octane overdrive" because any change in the instance is propagated back to the source.
as @funk mentioned on slack. the three dots under the "instanced" nodes show that this node is already being used elsewhere. so i would say that the "instance octane overdrive" is creating the wrong kind of node while it is running.
@khellstr shows a manual workaround for this with the real instanced nodes.... thread>https://foundry-modo.slack.com/archives ... 9440414609
source should change the instance - correct.
instance should not change the source.
If you look at the modo_reference I've attached, it's clear that I can change the color of the instance independently of the source, but still have the ability to change the roughness for both when using the source.
this is not the case with the "instance octane overdrive" because any change in the instance is propagated back to the source.
as @funk mentioned on slack. the three dots under the "instanced" nodes show that this node is already being used elsewhere. so i would say that the "instance octane overdrive" is creating the wrong kind of node while it is running.
@khellstr shows a manual workaround for this with the real instanced nodes.... thread>https://foundry-modo.slack.com/archives ... 9440414609
I think the instanced Octane Override is only an instance of the Octane Override Shader Tree item. However the node inside the instance are not instanced. I have added a FR to the TODO list to instance the individual nodes.
Thanks
Paul
Thanks
Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question