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 ........ 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 :-) 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 > > Isn't its main purpose in animation? Or can we insert the field evaluator > into a level which is animated (keyframe or simulated) without animating it > directly. I got the impression that it can also measure Velocity etc of the > level it is in?? This deserves better explanation and a few examples... and > apparently some debugging ;) > > BTW I got a book on Javascript, I just can't stand watching by the sideline > how these script wizards perform their magic! > > > > cheers, > > Mark H > >
