Particle Adapter

Consider a situation when a size-independent component, for example Image, is connected to multiple inputs, one of which is Bomber's Particle input and others aren't. In such situations, we'd have to decide which input requirements are dominant.

If we force Image to conform to Bomber's requirement (i.e. make it size-dependent), this will mess up the output that goes to the other target inputs. And vice versa, if we chose non-bomber requirements as dominant, we get particle clipping problem in the bomber.

Consider another situation, where the output of two components, one size-independent and other normal, is blended together via, say, the Blend component. It is impossible to untangle such signal and remove or impose size-independence upon any of its predecessors. The size decompensation must be done before two signals are mixed -- and having Particle Adapter as a separate component allows you to do exactly that.

One example of such situation is an image-based particle with some noise overlaid on top of it.

The previous version of Filter Forge had a Mode parameter in the Image component, that allowed you to turn size-independence for Image on or off. However, this provided no solution for size-independence of other components, e.g. Frame.

Furthermore, the introduction of new Color and Grayscale controls made the above solution even more unacceptable. In FF2.0 when you needed two Image components with different scaling methods, you can just create two copies of Image (their output is identical by design) and adjust Mode separately for each of them.

With the new Color and Grayscale controls the cloning method described above wouldn't make sense -- cloning a control component creates a redundant filter control in its interface, plus you'd have to manually load identical images into both copies of controls.

Having Particle Adapter as a separate component lets you remove size independence at any point of the filter's connection flow.

I understood the purpose to use Particle Adapter component. However, should it work for the input of image component like the upper right of this attached image?
Particle Adapter doesn't become complete substitution of particle mode of ff2 as it stands.

Quote
inujima wrote: Particle Adapter doesn't become complete substitution of particle mode of ff2 as it stands.

I can't notice any discrepancies (plz see the attached filter).

Quote
inujima wrote: problem when that is connected with components (e.g. Lookup, Scale, and Offset) other than Bomber component.

You should never have a need for that.

ParticleAdapter.ffxml

No - this is not a bug. The difference is caused by different behavior of Particle Adapter and the old Image component in Particle mode -- the latter doesn't repeat the image beyond its borders, but the former does (or rather, it doesn't force areas beyond 'particle' borders to full transparency).

(Yes, Particle Adapter is not a perfect solution, but unfortunately we can't have a proper solution until Filter Forge has infrastructure for proper handling of image bounds, so that components can be aware of them.)