Hello guys.
I’ve been having this problem since 1.6.
I’m using pflow to do some stuff and used the CoronaMultiMap to randomize some Shape Instances base color. And as you can see in the GIF they start fine but then the colors assigned get randomize every frame.
I did some of the same type of pflow animations before and did not have this problem…I’m not sure but I think I started to notice this when some of the hotfixes for 1.6 came out…but not sure at all when exactly.
I’ve attached some of the settings I have.
I’m using one shape with the multimap. But this also happens while using a group of shapes…
This happens when rendering locally, in the VFB and using backburner ..
Any help would be nice, because I can not exactly pinpoint if it is a problem just of MultiMap or something from pflow..
Hi. I forgot to say that those 2 “sets” of particles are just one, it’s part of a loop animation. So the bottom group it just the upper group but with time offset…
So the particles have no lifespan limit, they are emitted for 48 frames but no “age test” or “delete” node in pflow…
They just get emitted…all good for some time and then BAM… the ficker begins…
Works here in a quick set up (one PFlow emitter, one sphere, MultiMap applied using default colors in it rather than maps), I was able to scrub through up to frame 300 and didn’t see anything odd. Any chance you could share the scene?
So… I sat down with a friend and try to simplify this.
If the particles get deleted by a deflector…somehow the particles “reset” and the multimap in instance mode flicks … And it happens with particle age too..
So…instead of instance mode we change to “material ID” but the multimap doesn’t seems to “read” the matID. It only renders the first ID with no randomness.
But if you use the multi/subobject and separate coronamats it works well…
It seems that the Corona MultiMap doesn’t read the random ID assign by the “material static” box in pflow…and it flicks using the instance mode…
I’ve been playing with this for not so long, so maybe I’m missing something basic and probably not entirely corona related.
-same problem with both..
-all was done with 100% on both settings
-integration step the same on both on half frame
-it works, but the bad thing is that the 3dsmax file gets huuuge…and export to alembic also is huge… I’ve try this method because I had to render on cgifarm and got the flicker problem too ..
I asked a friend to do a test with other engine…works as it should
with the settings attached.. Same thing as in corona: Just a material with the multimap on the diffuse..
When viewing the pflow the Particle ID itself are not changing when particles die, so Corona must be getting confuse by something while using instance mode…and not randomizing in matID mode..
I´m encountering the exact same bug using 3ds Max 2017 and Corona 1.6.
Has this been fixed for 1.7?
I asked for the new build (1.7) but due to my company bureaucracy, will be days before I can get the patch.
edit: I tried using mesher and material by element and still got the ids changing.