Consider a Niagara System with an Emitter in "Global Space" that has "Interpolated Spawning" active and a "Spawn Burst Instantaneous" module with a "Spawn Time" of 0.0 (for example, the built-in ConfettiBurst Emitter).
Now consider that the corresponding Niagara Component in the level is moved and then reset and (re)activated in the same Blueprint Event, in the same frame.
In such a scenario, if the Niagara System / Emitter was previously inactive, the burst spawn will correctly happen at the newly set location of the component.
However, if the Niagara System / Emitter was active at the time of the move+reset (for example, while still having live particles from a previous activation), the burst spawn will unexpectedly happen at the old location of the component, where it was in the previous frame before being moved.
This unexpected behavior probably happens because the "Spawn Burst Instantaneous" module with "Interpolated Spawning" ends up using a Spawn Interpolation of 0.0, which results in the previous frame's location being used for the burst.
How does TextureRenderTarget2D get TArray<uint8> type data?
How to delete some elements correctly when deleting an array loop?
How do I set a material as a post-processing material?
Why does the REMOVE method of map container remove elements have memory leaks?
What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?
What is the difference between Camera and CineCamera?
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-209013 in the post.
0 |
Component | UE - Niagara |
---|---|
Affects Versions | 5.2.1, 5.3.2 |
Created | Mar 6, 2024 |
---|---|
Updated | Sep 18, 2024 |