 |
I've got this fixed up by simply restarting from scratch any particle effect that has non-cycling stages when it's triggered "on". So when triggered "off" the particle does nothing, when triggered "on" it fires. But having tried it in a test map, it looks like the best behaviour would be for perpetually *cycling* particles to be triggered on and off (as they are now), but for non-cycling particles to always fire when triggered. The on/off behaviour doesn't make much sense for particles that fire once then stop. For those, every other trigger event would result in no reaction. I'll ask in the editor's guild. |
|
|
The correct fix for this is to remove the code that randomizes particles using time offset, and substitute correct code that uses the "diversity" shaderparm instead. That's how every other particle effect achieves uniqueness, and it's clearly how the Activate() method and the existing "cycleTrigger" spawnarg were meant to work. I'll also add editor documentation for "cycleTrigger" as its name isn;t self-explanatory at all. |
|
|
Rev 14255, func.def (DR documentation) Rev 6477, emitter.cpp |
- Anonymous
