Thank you for your report. I will begin investigation into this issue as soon as possible. If I am unable to reproduce the problem, or I need more information, I or another staff member will follow up with some additional questions for you. Otherwise, I will post an ‘Answer’ once I have logged the issue in our bug database or we have a solution for it.
In the meantime, please be sure to review our suggestions for how to report a bug, and feel free to edit your post if you have additional information to provide:
Well, as you can see from the picture, the particle is shifted from its emitter’s position. Below is the setting that you need to set in Velocity/Life module. Ticking on the object’s using local space does help on the rotation issue, but the particle initial positions is still shifted from it original spawn pos.
This is making our life hell when editing particles. Basically, whenever we change speed, the particle position shifted entirely. Can you help fixed this soon?
So I copied your system as closely as I could and still could not get it to behave the same way. I did note that shortening the lifetime made the particles appear to “wobble” but only in the sense that it was doing the same X and Z calculations over a shorter timeframe which is expected with a /Life module. I want to check what version of the engine are you using? Is it GitHub compiled or from the launcher?
This is the latest 4.3 version, straight right from Epic.
I can already see some shift in your image. Notice how the first particle isn’t spawning from the object, but from some position ahead of it? Try rotating your emitter without “using local space” option, and the shift will be more visible.
If you still can’t replicate this, I’ll send you my mock up scene tomorrow.
I can see what you are talking about, but unfortunately this is the vel/life module working as intended. Essentially because you are setting that velocity at a zero time the particle is being born with a high velocity which causes the offset rendering. There are two ways to fix this and it depends on preference as to which one you would like to use, but both are going to do the same thing.
One is to add a zero time in your vel/life module and change the zero time to 0.1, in this way the particle will be rendered at the origin point and then be assigned its velocity. You can tool with going close to zero in the timeline, but it will slowly get close and closer to offsetting the particle again.
Or, you can add an initial location module to your system and use it to offset the distance back to the system’s origin. For my 2000 x 500 z system I had to offset the initial location by -50 on X and 0 on Z to get the system back to the origin location.
Hopefully this can sort out your problem for you -
On a closer investigation, seems like the bug is in Ribbon data type. As you can see, the trail isn’t following it source module, nor responding to the object’s rotation. (I usually don’t render the source emitter, so I didn’t see it. And I thought the shift came from the original emitter.)
“Inherit Rotation” does nothing, the ribbon’s position is still shifted. Hope you can test it on what I gave you.
Otherwise, just construct a simple ribbon with source particle and you can test this bug by yourselves. I’m willing to help as much as I can but please fix this really soon though. We could not add any effect to our game at all.
Ok, just to make my point clearer. Here’s the two scenarios that we are facing with ribbon data. Please see the pics below.
When we use local space, the ribbon isn’t following the source particle. However, the position of the source particle is correct (isn’t shifted.)
When we uncheck the local space, the ribbon data follow the source particle correctly. However, there’s a bug that cause the source particle’s position to shifted from the emitter. (Can you see how the particle isn’t spawning at the green arrow now?) SO the whole thing shifted by some amount.
Please notice that both pic have the same parameters, the only different in the second pic is that the “local space” potion isn’t checked.
This shift become very severe when we have small life and high velocity.
With this bug, both scenarios cannot be worked with… and we’re left with broken particles system that can’t correctly handle high velocity particles.
It does’t matter which scenarios you fix, I just want one working option with this…
Ok, I’ve been working with your assets and creating duplicates in various engine versions. I 've been able to reproduce the behavior in Scenario One above when both modules have a checked local space I am getting the offset as you show above. However I am not able to reproduce the Scenario 2 yet. The Ribbon Emitter follows the particles just fine without local space checked. I am going to go back through your assets again to double check every setting.
Thank you for the information above it helped me narrow down the scope a lot.
Hmm, I think you are a bit confused. To break it down even further, there’s 2 bugs:
Ribbon Data doesn’t follow its source particle when local space option is checked.
2, When local space option is unchecked, there’s a slight “position shift” in weird direction from emitter with high velocity. This actually has nothing to do with ribbon data. I believe the bug is in emitter’s initialization with high velocity.
Anyhow, at least, could you fix scenario one for now then? I see no use in having Ribbon Data that doesn’t follow its source particle anyhow. I would like to get scenario two fix later too, I’m sure many people will encounter this bug again and again.