You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
using the Simple_Distortion.efkefc in the ParticleEffectComponent shows some problems with it.
After Selecting the Moving option, when the scene containing the ParticleEffectComponent is moved, the effect shows up at the new location, but is also shown at its previous location, effectively duplicating it.
When a new effect is loaded instead of Simple_Distortion.efkefc, this effect is not overwritten, but the new particle effect shows up along with Simple_Distortion.efkefc
This seems to be a problem with effects which run continuously (don't have a finite lifetime). The laser effects provided don't show this problem as they have a finite lifetime. But Sime_Distortion runs continuously. Also, after saving and reloading this scene, Simple_Distortion effect doesn't show up and only Laser02 works (which is intended and should happen)
To trigger the bug, you'll also have to play the scene. It seems like playing the scene is duplicating the effect. If we don't play the scene, it is working as intended. But after play, a duplicate of the effect is created which persists even after play has been stopped.
using the Simple_Distortion.efkefc in the ParticleEffectComponent shows some problems with it.
After Selecting the
Moving
option, when the scene containing the ParticleEffectComponent is moved, the effect shows up at the new location, but is also shown at its previous location, effectively duplicating it.When a new effect is loaded instead of Simple_Distortion.efkefc, this effect is not overwritten, but the new particle effect shows up along with Simple_Distortion.efkefc
the effect files used : Simple_Distortion.efkefc and Laser02.efkefc (available in Effekseer162bWin\Sample\00_Basic after unzipping https://github.com/effekseer/Effekseer/releases/download/162b/Effekseer162bWin.zip)
The text was updated successfully, but these errors were encountered: