There’s a means of instancing some parameters in Magmaflow via exposing the inputs and adding an instanced controller. However, very few things that you can set in the nodes are able to be exposed. And the ones that can’t also can’t be animated. So there’s no way to match the lacunarity of a pair of VecNoise’s in either the same flow or two different modifiers. And if I needed to animate that parameter for an effect, I can’t do that either. For some operations, I can imagine why you might not want to have an input connection in the flow, as it prevents you from pre-computing and caching something for all particles, but for something that is user defined globally anyway, I don’t see how allowing animation/exposure would interfere with the current tools.
Somewhat related, I also noticed that an exposed InputVector in Magmaflow shows as 3 floats, not as a point3. KCM’s however do show point3’s.
- Chad