The Fibonacci series is a sequence of numbers starting with 0, 1 and where each subsequent number is the sum of the previous two:
0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89, 144, ...
Thanks to Binet’s Fibonacci number formula, I didn’t have to use a Repeat node
Here’s a recent array question from the mailing list: How do you build an array that looks like this?
[0, 0, 1, 1, 0, 0, 1, 1, 0, 0, 1, 1, ...] ?
I didn’t check the other answers yet, because that would be cheating
When I look at that array, I see a repeating sequence of four integers, so that naturally suggests doing something with the Modulo node.
Using the If node is nice for clarity, but I could simply take the Boolean output of the comparison node.
Set Flags shows how to store multiple boolean flags in a single integer value. In programming, this is known as a bitmask or as bit flags, and the idea is based on the binary number system where each digit can be only 0 or 1 (on or off, true or false).
For example, in the binary number 1010, you have four bit flags: flags 0 and 3 are false, and flags 1 and 4 are true. The decimal equivalent of 1010 is 10 (21 + 23).
|Binary||Decimal||Power of 2|
Here I’m instancing a group of Arnold standin sequences, and giving each instance a different start frame. (Each standin sequence is an animated bulge on a cylinder.)
PS It works fine until you go past the last frame of the sequence, because looping or clamping the ShapeInstanceTime doesn’t seem to prevent SItoA from loading the non-existent ass file.
In the real world, indirect lighting comes from diffuse reflections: light reflecting off of nearby surfaces. In the rendered world, a camera ray hits a shading point on an object, and from that point diffuse rays are sent out to sample colors from surrounding objects.
While building an ICE tree version of this parametric equation
I discovered how to crash Softimage 2014 SP2 by doing a Show Values on the output of a Multiply node:
The key is that you have to set and then get the values later, and the array has to be the final term in the multiplication. Somehow this intuitively feels like something where things could wrong…
I tested as far back as 2013 SP1, and they all crashed.