As an exercise I tried creating my own motion caching function (which was way slow because in Piccolo) and I”d have the same problem. I figured it was probably floating point values being rounded off to some number of decimals in the caching. Does it make sense or am I off track?

Thanks for the info and I”ll try it right away!

Yup, that’’s a legal Behavior move.

Just a slight correction on the multiple passes, though. You can actually run one simulation and dump out MI files for each pass. When you do the “render setup” step in XSI, do one for each pass and put the resulting render setup data in a seperate folder. In the sim, create a mental ray object for each pass and initialize them in the standard way (same way as when dealing with one). Make sure each mental ray object spews out its resulting MI files in a different folder. Run the simulation once, and you should see MI files for each pass. Make sense?

yotto