SetPrimaryPartCFrame Messing up conveyors

Hey, i’m working on a Tower of hell type game and SetPrimaryPartCFrame messes up the Velocity property of a part, is there any fix to this?

I’ve tried changing the Velocity a ton and it still changes it.

2 Likes

Moving, rotating or resizing a Part using the Studio build tools causes its Velocity to be set to (0, 0, 0). Apparently that also happens when calling SetPrimaryPartCFrame?

A really simple solution would be this:

local conveyorPart = script.Parent
local conveyorSpeed = conveyorPart.ConveyorSpeed.Value

conveyorPart:GetPropertyChangedSignal("CFrame"):Connect(function()
    conveyorPart.Velocity = conveyorPart.CFrame.LookVector * conveyorSpeed
end)

Put in a script, put that script in all conveyors. Also put a NumberValue caleld “ConveyorSpeed” in all conveyors. Or change it to automatically work on everyting tagged with “Conveyor” or something.

2 Likes