I’m still not sure how I get from the old $X2 + $Y2 + $Z2 to the python version… me.curPos[0] * me.curPos[0] + me.curPos[1] * me.curPos[1] + me.curPos[2] * me.curPos[2] - 1
I’m still at a loss as to how I can pythonize the noise ($X,$Y,$Z) expression or, more generally, translate any or the existing Touch expressions into python form.
As usual, the documentation needs a lot of love but it’s early days yet of course.
imagine that you put down an Iso surface SOP, switch its parameter mode to t-script, type in $X*$X + $Y*$Y + $Z*$Z - 1 then switch the parameter mode to Py.
and the expression automagically changes to me.curPos[0] * me.curPos[0] + me.curPos[1] * me.curPos[1] + me.curPos[2] * me.curPos[2] - 1
okay, it already does with this default expression but imagine if noise($X,$Y,$Z) changed to its python equivalent? yeah, I know, that would take some time.
we really do need a table of the python equivalent to each expression though and pretty soon - or a method for deriving one from the other.
is it possible to combine two or more functions in a single line?
or- is it possible to evaluate a multi line python script located elsewhere, like as a text DAT, within the “func” parameter? something like a glsl mat, where we could write a longer script to be evaluated.