Functions are evaluated quite quickly, but they are evaluated for each drawn pattern. So displaying the timing for a single evaluation would not make sense.. The computation time will be directly linked to the amount of patterns you want to draw + the complexity of the function. One thing to know : the functions are…
Thanks, that helped a lot. I copied and broke apart the blend graph, figured out how to set up the drop down boxes, but I'm still having some issues. Basically I have 2 uniform colors plugged into a blend where opacity is supposed to be controller by the same opacity functions in the blend example, however, when I click…
Hey guys, I'm dipping my toes in those functions and ran into a problem. I want to create a lil chromatic aberration node by doing a directional warp on the RGB channels separately, each on a different angle, but with a single input to keep things simple. So say, user sets angle to X, R channel is warped at X, G at X+120…
You could use a function to do that. For example you have a "cracks opacity", and the "Aging" parameter. For the opacity on the blend nodes where you blend in your cracks, create a function. Inside the function, input the Cracks value, and overall Aging value into a Minimum node. That node will spit out whichever value is…
Ah, thanks Froyok that question helped me figure it out! Apparently there are multiple ways to expose parameters. I was right-clicking on the node in the graph view and using "Expose Parameters". Instead, I used "Expose" under the function drop down in the right panel. This functioned more how I expected.
Thanks Uzziel. This works nice. Next question. How to make my own function nodes and nest them in pixel processor? Something like those built-in nodes with star icon, "Degrees To Radians" for example. EDIT: Nevermind. I got it. Right click on Substance Package in Explorer > New > Function.
I have been looking a lot at Functions recently. One thing I keep finding myself wanting to see is a bit more feedback from the nodes themselves. Most of these things can be solved by doing tests and viewing the changes in the 2D/3D view but it would be nice to have (and quicker to iterate) some other feedback. - Is it…