Hello Mugz, I have been investigating the issue you reported and found the
source of the problem. As you noted it only happens when using
CODE_HEATDEFORM or CODE_AFTERBURNER materials. This is because they use
the material specific parameters on the Output block. These parameters refer
to a material instance that is used for a whole instance of the effect, not to
a material instance used for a single particle, so you cannot use particle
specific computations inside a graph and plug it in these inputs (a
GetParticleAttribute node for example). Such a setup would cause an invalid
cache entry to be created and reused for a part of the graph, instead of
dynamically computing it when it is required, therefore feeding a static value
to other parts of your effect graph. I will make sure the documentation is
updated so this specificity of material parameters is made clear. I will also
keep you updated when a fix to prevent this setup to mess with the rest of the
graph will be released. Regards, Matthieu