Page 1 of 2
damper
Posted: 18 May 2018, 03:34
by zding
I really like some controls. For example damper, linear.Now I can't use them for arrays yet.
Re: damper
Posted: 18 May 2018, 07:26
by zding
Re: damper
Posted: 18 May 2018, 07:28
by zding
There are too many connections.From Arrayindexer to array.
Re: damper
Posted: 18 May 2018, 08:59
by stephen
Hey,
you are right and a ticket already exists for an Array Ease Node. I have bumped that ticket. Especially the new data visualization features of V6 ask for it.
Shortcuts
Posted: 04 Jun 2018, 07:56
by serourian
Why doesn't ventuz add the a new method of making a shortcut of a node, to be used in another layer as reference instead of wiring to the original one....? for example: you create a variable int node in a layer, then right click, create shortcut, then cut the shortcut and paste in any other layer, than whenever the original node changes, all the shortcuts change too. It is like an instance node of the original one...
This will allow us not to have too much wirings.. This will help us a lot !!!!
Re: damper
Posted: 06 Jun 2018, 15:43
by chriss0212
Hi serourian,
for this you can use scene and project data.
Greetings
Christian
Re: damper
Posted: 06 Jun 2018, 15:45
by chriss0212
Hi Stephen
"Especially the new data visualization features of V6 ask for it."
Not only... we are waiting a loooong time for that feature
Greetings
Christian
Re: damper
Posted: 11 Jun 2018, 11:45
by Naggar
Hi guys,
Included with the Damper and linear etc.. could we also have expression arrays? same as multi-switch but with expressions and inputs instead
Re: damper
Posted: 15 Jun 2018, 14:19
by chriss0212
What do you mean by expression array? Isn't it possible to use a string array?
Re: damper
Posted: 25 Jun 2018, 18:11
by Naggar
Well, it might be a petty request to be honest ^_^..
But I have projects that I have to create loads of int/float expressions to get a specific condition met.. and it ends up making the content hard to navigate through especially when you're editing an old project

. But if we had a multi expression node.. where we can have an "add" button (like the Multi Switch node) for each it adds "expression" input and "variable" inputs, and "Result" outputs, then we could reduce loads of nodes in the content window.