Scripting HelpersARCHIVE
A little piece of Roblox history. Preserved for everyone, one question at a time.Read about the archive →
COMMUNITY QUESTION

The rotation of the model is choppy?

So I'm trying to make a place that just lets you stare at a spiral. It all works fine until I start it up on a server, where the animation looks choppy. I'm not sure why its doing this or if this is a limit from roblox's servers.

The game is here if you want to observe it yourself: https://www.roblox.com/games/615076271/A-Spiral

here is the code of the spiral itself:

parent = script.parent

--rs = game:GetService("RunService") 
-- Attempted to run this client side.. but I don't exactly know how to do that

primaryPosition = parent.SpiralCenter.Position

workspace.FakeSpiral:Remove() -- This was just for the game's screenshot

for num = 1,3 do -- This creates the spiral
	local r = 0
	for i = 1,360*1.5 do
		if r <= 40 then
			r = r + 0.1
		end
		
		part = parent.SpiralCenter:Clone()
		part.Name = "SpiralPart"
		part.CanCollide = false
		
		part.Size = Vector3.new(0.5,2 + r/15,2 + r/15)
		part.Position = Vector3.new(
			(math.cos(math.rad(i + 360/3*num))*r),
			parent.SpiralCenter.Position.Y,
			(math.sin(math.rad(i + 360/3*num))*r)
		)
		
		part.Transparency = 0
		part.Parent = parent
		part.CanCollide = true
	end
end

local rotate = 0

while wait() do -- The animation of the spiral
	
	if rotate <= 354 then
		rotate = rotate + 3
	else
		rotate = 0
	end
	
	parent:SetPrimaryPartCFrame(
	CFrame.new(Vector3.new(0,40,0)) * CFrame.Angles(math.rad(rotate),0,0)
	)
end

4 comments

0

Moving an entire model in studio can look choppy. The best way to do this with a lot of parts, is unions, or welding.

0

Actually in studio, it looks perfectly fine. It's just online on a server it looks choppy. Unions would be ok... if there weren't a total of 1621 parts in the spiral itself ^_^"

0

yeah it's just from the number of parts.

0

Figured so. Trying to do it with gui's instead now. Can still make a video of the spiral's animation at least

1 answer

Try rotating the model by LocalScript. Since all the rotation is client-sided, none of the replication choppiness is there (though, if FilteringEnabled is activated, that's a different story).

This discussion is preserved as it was. New answers, comments, and votes are closed.