Surface Runner

#1

This is first development of my old bugs.

  1. Basic example with one bug.
    http://www2.11moon.com/sample_files/20110801/Surface_Runner_basic.mp4
    http://www2.11moon.com/sample_files/20110801/Surface_Runner_basic.zip

  2. Example where the bug are copied to 10 by “Hierarchy” node.
    http://www2.11moon.com/sample_files/20110801/Surface_Runner_10.mp4
    http://www2.11moon.com/sample_files/20110801/Surface_Runner_10.zip

  3. Example where the bug are copied freely by MoGraph
    http://www2.11moon.com/sample_files/20110801/Surface_Runner_MoGraph.mp4
    http://www2.11moon.com/sample_files/20110801/Surface_Runner_MoGraph.zip

#2

Neato, this is pretty awesome concept you have here. Will be sure to give myself a lesson of these files.

#3

This is first update of bugs

http://www2.11moon.com/sample_files/20110801/Surface_Runner2.mp4
http://www2.11moon.com/sample_files/20110801/Surface_Runner2_basic.zip
http://www2.11moon.com/sample_files/20110801/Surface_Runner2_MoGraph.zip

Here I used 2 noise nodes to add natural behavier to the bug.
They are “stop (randomly changed their speed)” and “drunk (randomly changed their direction)”.

Notes to use noise node.

  1. “Scale” and “Frequency” values are very important to control noise effect.
  2. Prevent unnatural synchronization, “seed” value is changed by ID number of TP.
  3. Also position vector in noise field is matched to bugs position.
  4. Noise node for “nz1_in” works in “absolute”.
#4

Oh boy, awesome stuff tofuji, keep it comin’ :slight_smile:
One question though, the vector calculations in your coffee nodes,
would it be also possible to do them only with xpresso nodes?

#5

Yes, please see another example which treat simple target function.

http://www2.11moon.com/sample_files/20110801/axis.zip

XPresso nodes and COFFEE expression have both advantages and disadvantages. But, in case of matrix/vector functions, I recommend to use COFFEE. Because it is much more simple, and easy to add functions.

XPresso
Advantages: TP, easy to get/set objects (tags, materials, parameters, etc)
Disadvantages: difficlut to handle structures (“if - else”, for, switch, break), difficult to make complex things

COFFEE
Advantages: easy to make complex things, easy to handle structures
Disadvantages: difficlut to read/write “code”, no TP, difficult to get/set objects

#6

This is the file which does not use COFFEE node.

http://www2.11moon.com/sample_files/20110801/Surface_Runner2_MoGraph_XPresso.zip

#7

Thanks for the example tofuji,
I read today a little on your site about the coffee/xpresso comparison,
awesome stuff you have there. My problem is that I can’t write any code,
connecting nodes is a lot easier :slight_smile:

And thanks very much for the example purely with xpresso, learning a lot here –
you are right, coffee is much more suitable for this kind of tasks :wink:

#8

In these files, I have used “Matrix” object to bridge “Cloner” to “XPresso”, because there is no way to control Cloner from XPresso directly. The Matrix object has a good function that “act as TP”. So you can control the Matrix object from XPresso as a TP group.

However the bridge is not only one. mark render mentioned that other ways like “TP” and “Dynamics”. They are bit complex, but still possible. I have made additional example with the ways.

http://www2.11moon.com/sample_files/20110803/XPresso_TP_Cloner_SR2.zip
http://www2.11moon.com/sample_files/20110803/XPresso_Dynamics_Cloner_SR2.zip

Function is completely same, at least in this case. And Matrix is the most simple way, so I used it. However there should be different possibilities with different bridges. If you have interest in other bridges, please check it.

#9

i haven’t though of a use for this yet but it’s great. Thanks for sharing…

#10

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.