Three in a row: I know this one may be hard due to caching etc. but changing upstream requests opens a hole new world or possibilities. Compare Houdinis Stamp feature.
In a nutshell imagine that I had only one ImagePlane but could push the ID of the current processed vertex in a replicate or custom vertex upstream so that the ImagePlane or any other node could react to the id.
This is the future.
Actually in houdini you can stamp any attribute but the most useful is the id.
In Fusion think of this:
- Code: Select all
[Points]->[Replicate]
A | (Hidden: Change the request to the current id)
| V
[ImagePlane] (Evaluates each request with the given id)
Now I could make an expression in the ImagePlane which e.g. changes the position based on the id.
The result is that I generate multiple copies.
For a transform this doesn't make sense, since it is implemented in the Replicate, but you could use it to drive any procedural changes before hitting the replicate.
EDIT: Sorry for pushing the requests in your thread. Just had to let the brainfarts go