Touch 088 $ expression not workin

hey guys been following along with some of the workshop videos on the site and now have come into the expression parts

The problem I am experencing is that I cant apply typed variables such as $F to rotate… all i get is a error… but if I drag and drop the item to a value I get a expression. i reinstalled the 64bit version twice now and still the same problem :s

the PC is worth about €3000 so it can handle the task… maybe a fresh install of windows?

$F or any variable is a tscript thing in TouchDesigner. With 088, everything is python by default, so you get an error.

try:
me.time.frame
or
me.time.seconds

for frames and seconds.

Or you can change the operators language to tscript and these variables will work in parameters.
derivative.ca/wiki088/index. … r_Language

Any expression with $, from the older tutorials, is in the old scripting language from 077, called tscript. 088 defaults to Python.

See this thread:

viewtopic.php?f=27&t=5507

thanks for the insight, so basically I gotta learn Python to do the varible, thanks again

Or switch the node language to tscript. If you aren’t doing any scripting or expressions other than using variables, you won’t notice any difference and your variables will work. :smiley:

Jump for joy it is working for me now, yay :smiley: the first of many hurdles to overcome haha!

thanks for the support

About animating these parameters…I’m trying to make a SOP-noise “not loop” with the timeline. Changing me.time.seconds, to me.time.frames doesn’t work! “Error: (Parameter: Translate) AttributeError: ‘td.timeCOMP’ object has no attribute ‘frames’”. The syntax is right but ‘frames’ doesn’t work in all objects…? What’s going on? :smiley: I saw somewhere that you can keep adding frames to noise, so it won’t loop with the timeline…It’s driving me insane that everything reset’s after 10 seconds. Sorry about hijacking the post, but i thought this was so close to the original topic.

It’s just me.time.frame actually, I’ve edited the error in the above comment.

That works great! And the answer to my own question seems to be ‘abs’ in beginning for continuous movement. me.time.absSeconds.

Correct, and me.time.absFrame