Projectile lags for a second when I instantiate it

Help and Feedback Scripting Support
#1

So I was scripting a game where you can throw items around… The problem that I was having was when I instantiated a projectile it would lag for a second and then it will start moving

This only started happening after I started rendering on the server-side. I already tried using something call PCache and I don’t really want to get into restarting my code for FastCast. Is there any other way to fix this?
Here is an example:

2 Likes
#2

Have you tried setting the network ownership? Learn more Here.

1 Like
#3

I tried doing that too but I got an error when I did that. Ill show you in a sec

1 Like
#4

Alright so I set the network owner to nil and there is no error outputting but the freezing is still there
image

1 Like
#5

By the way don’t use instance .new with a second arguement.

I believe you need to set the properties first then parent it into the workspace since I believe the delay is due to the delay in setting the velocity of the projectile.

3 Likes
#6

Ill try that thanks. ill message back if it does not work

#7

Alright I tried that and nothing changed

#8

Yeah I tried it and nothing changed after following that

#9

are you sure it’s being parented after the velocity is set (instead of before)?

#10

i am sureimage

#11

Maybe anchoring the part and using raycasting to detect the collisions and moving it every frame?

#12

try setting the properties in this order:

- looks (material, color, size, etc.)
- the light
- set network owner to the client who fired it, not “nil”
- physics (cancollide, location, velocity)
- parent

#13

i cant set the network owner before parenting since it has to already be a descendant of workspace

#14

my bad, make sure it isn’t nil though

#15

wdym what should i make it then?

#16

nil sets the ownership to the server

#17

the player who fired the bullet, so it appears smooth for them

if you want, you can call bullet:SetNetworkOwnershipAuto() on it after it reaches a certain distance from the player

#18

yeah but that would not really change anything the freezing will still remain

#19

You can remove the BodyVelocity part and do something like…

local Speed = 5

local Connection
	Connection = RunService.Stepped:Connect(function()
		if not Part then -- Stops moving and disconnects if it doesn't exist anymore
			Connection:Disconnect()
		end
		local ProjectileRay = Ray.new(Part.Position, Part.CFrame.LookVector * Speed)
		local Hit,Position = Workspace:FindPartOnRay(ProjectileRay, Character)
		Part.Position = Part.Position + Part.CFrame.LookVector * Speed
		if Hit then
			-- Do collision logic
			Connection:Disconnect() -- Stops moving as it's collided by now
		end
	end)

It might be useful if it’s related to what I’m seeing. You’d need to adapt it to the way that you’re working on tbh.

#20

Recommended to use the new raycast :wink: