I am trying to make projectiles that move between two points. When I create a projectile, I set its Velocity and its CFrame before I move the part into workspace. The expectation is the particle begins moving on the first frame that it is in the workspace, but it doesn’t – it pauses, and that creates issues because the time it takes to reach the target is longer than expected, so the parts are being deleted earlier before they reach the target:
I’ve attemtped keeping a pool of pre-created parts that are unanchored in workspace and setting their properties when it’s time to fire, but there is no change in behavior.
Are the parts network owner the server? This seems to be an issue with sleeping physics which could be caused by multiple variables. A (temporary) solution could be to try to handle the ball-physics display client side, as this should avoid sleeping physics associated with network ownership radius.
EDIT: Setting network ownership to the server will not solve this issue. Handling the part entirely client side seems to be the best fix for sleeping physics. I would just have a server-hitbox version and a client-visible version.
what youll maybe want to consider is having the server portion of the projectiles be invisible, and replicate that projectile with the same behaviour onto the client, that way you can have smooth things(and it shouldnt cause issues)