Page 1 of 1
little problem with Node-Editor
Posted: Sun Jul 12, 2015 10:13 am
by miohn
Hi Ahmet,
just playing around with the Node Editor and with Substance Designer.
(for me there is no need/advantage for SD btw. because Node-Editor in Octane
does nearly the same)
But what I encountered is, that when I make a second connection from a C4D-Noise-Node,
the effect from the 1. connection gets lost.
I think, duplicating the Noise-Node and making 2 individual connections (which works)
is not the purpose of a Node-System, because I only want the make changes to "one"
Noise-Node.
Is this a limitaion for displacement or C4D-noise-node?
Btw. would it be possible to add a "blur"-Node?
And, sorry, one more thing:
would it be possible to add a toggle or activation for nodes?
F.e. when adding a ColorCorrection that you can toggle this "on" and "off"
with a shortcut to see/switch the effect whithout
having to remove the connection and reconnecting again.
Hope you understand what I mean!
thanks
MIke
Re: little problem with Node-Editor
Posted: Sun Jul 12, 2015 3:01 pm
by aoktar
Hi Mike,
it's clear that there is a problem with same shared connection on displacement node. But i don't know what causes. I'll investigate and try to fix. Otherwise i'll leave it as it be until find a fix.
Disable/enable functionality is on my todo list. I'll try to implement it soon. Thanks for report.
Re: little problem with Node-Editor
Posted: Sun Jul 12, 2015 8:41 pm
by miohn
o.k.
thanks!
regards
Mike
Re: little problem with Node-Editor
Posted: Sun Jul 12, 2015 11:09 pm
by aoktar
At this point, i have some hardness to decide about disabling some nodes. Imagine that we use a complex node tree with some mix,multiply,etc... And you disabled a mix node. Do you thought that it will disable coming part of branch which enter to mix node? Or will it pass the incoming nodes to upper direction? First is easy but second way not. Because there can be a few input nodes which connected to this node. We can't know which one will be used.
Re: little problem with Node-Editor
Posted: Mon Jul 13, 2015 7:05 am
by Yambo
I agree.
Re: little problem with Node-Editor
Posted: Mon Jul 13, 2015 8:58 am
by miohn
hmmm I see.
I think, the second, sadly the more difficult variant, would maybe have more advantage.
Not sure.
But for me, it would be helpfull to have it first on adjustment nodes like colorcorrect, clamp etc.
Btw. what was also discussed some time ago.
Only as inspiration:
Is there any way, to visualize all nested materials inside the main mix-material in material manager?
F.e. with a small icon or frame around all the relevant materials.
Because in Material-Manager, all materials are looking the same and its very laborious to identify them.
But overall great compliment!
Node Editor works really smooth now and its great fun to work with!
regards
Mike
Re: little problem with Node-Editor
Posted: Mon Jul 13, 2015 9:29 am
by Yambo
I׳ve just almost completely left the material editor and i׳m working only with the node editor. It is very smooth and much convenient to work with. Bravo Ahmet.
I also think that visualise mix materials is a great idea.
And also - A way to organise a bit the node editor will be really helpful. Now it takes too much space in my screen and i wish i could rearrange the content inside the node editor a bit.
Re: little problem with Node-Editor
Posted: Tue Jul 14, 2015 12:02 am
by dotcommer
I can't wait to start using this new node editor. It sounds awesome. Unfortunately I'm still stuck on 2.23.2 because of the VR project i'm working on and there was a warning not to switch to the latest release mid project due to scene scale issues.
Re: little problem with Node-Editor
Posted: Tue Jul 14, 2015 12:24 am
by aoktar
dotcommer wrote:I can't wait to start using this new node editor. It sounds awesome. Unfortunately I'm still stuck on 2.23.2 because of the VR project i'm working on and there was a warning not to switch to the latest release mid project due to scene scale issues.
there should not be a problem within 2.32.2 versions. That's for upgrades from older than 2.32.2.