Projectile fire behaves differently in client then in server

[beanswaggle]

@NisshokuZK;303103

I see your event to spawn a project is called “Fire Projectile Multicast”. Is it a multicast event? I don’t think it should be, spawning stuff is usually the task of the server only. Multicast would cause the server plus all connected clients to try and spawn a separate projectile. Can this be related to your problem?

Also, isn’t the client just seeing the projectile after it has already traveled a bit?

@AlexW88;300970

Did you zero out the velocity for your tests? Have you tried just spawning the projectile on the server (it definitely should replicate at the same location for all clients if spawned on the server)?

OK turns out it still works on run on server, but that doesn’t fix the problem.

I zeroed out the velocities and it looked like they were spawning in the same spot. I kept increasing the velocity, but the higher the velocity the larger the difference in the location that it looked like it spawn. I decided to print out the projectile’s location from the server and the client. and this was the result.

The Locations were exactly the same yet in the image you can tell a difference. that makes me think the projectile is rendering late on the client screen.

So i’m a bit baffled.