Hi Mark,
I can explain a little bit how it "should" work.
It's like the "animation based on other animation, and not on time"
Maybe you know the "bend based on acceleration" scene,
or the "muscle bulge based on skeletons angle".
You "simply" set up a choreography for an object and the teach
the object how to react on the field evaluators output.
Now the buggy things coming in:
Since v4.5 some output values have changed from let's say 10 to 10000.
If you animate field evaluator directly, it's crashing or stopping RS.
Sometimes the field evaluator evalutes only on manually moving
the frameslider, not in playback
........
Hi Matthias,
Thanks for replying within half an hour; I think I won't try to tame this
monster for the time being... ;)
Because of the above, my try was via constraint+script, which solves
most strange behaviour in RS (like the ik-objects etc...).
And: Yes, you can put the field evaluator in a level (or better: you
should ;-)
and then animate the level and watch the outputs.
In my opinion, you should transfer the data mostly via JS, and not as
"based on".
and save often, when working with the field evaluator :-)
I forgot to ask: would RPL behave differently from javascript in this
context?
Maybe RPL would be easier for me to pick up than JS ;)
to Vesa: Is it possible, to get a fully working field evaluator in V6 :-?
I'll put some "field evaluator+poor mans scripts" online, if there's time
on the table.
Matthias
A final V5 service pack to fix a few errors that crept into SP4 would be
welcome! (some JS system files missing, bugs) Unless V6 is really around
the corner...
thanks,
Mark H
