Hm, I wonder how we’ll look for correctness with such an unpredictable amount of animated nodes. I get 600 invariably but is that correct?
My function is not even optimized but the most interesting is, I think, after test it on different Max versions on my computer, I get so freakish and weird results:
Max 9 SP2 64: nodes:600 | time:8907 memory:4351776L Max 2009 x32: nodes:600 | time:1922 memory:1520L Max 2009 x64: nodes:600 | time:265 memory:105848L Max 2011 x32: nodes:600 | time:688 memory:2712248L Max 2011 x64: nodes:600 | time:516 memory:4877968L
So, as you see, its so easy to make wrong conclusions, and so difficult to reach meaningful conclusions.
Code optimization in Max is a (how to say…) pitfall (: