Most of this response was taken from here.
This will be “as smooth as possible” but isn’t necessary for it to be smooth.
Optionally set the CFrame on RenderStepped. Both parts and guis can accomplish this (I suggest guis). If you want to make some custom handles, do it. It looks like you figured out the handles object, so that’s no longer the issue. This removes any latency or “network lag”, and has a higher update rate than the network send rate. Your title is Custom movement handles, but you don’t actually mention anything about custom handles in your post. If you want this to look as smooth as possible to clients, you’ll need to either: If you use a Weld with an anchored Root instead of a Motor6D, then the Model Parts will not move when the Root does. Key point with the latter one is that the Motor6D lets you move the anchored Root Part and have the rest of the unanchored parts move with it. When you move the Root Part, all of the other parts will move too. If you want to move this with scripts and setting CFrame on Heartbeat, then you’ll want a joint structure like this Root Part (Anchored) If you want to move this with physics, then you’ll want a joint structure like this Root Part (Unanchored) Model:SetPrimaryPartCFrame(CFrame.new(0, 10, 0)*CFrame.Angles(0, math.rad(angle), 0)) Exampleįor i = 1, 100 do - repeat 100 time to exaggerate the effect so it can be seen in a 30 sec video If you’re using SetPrimaryPartCFrame, then this can lead to the parts drifting away from each other after a lot of time. By constantly changing the cframe of the primarypart in a heartbeat loop Keep going and every time you move it 10 times you should see it increase the decimal by. If you move it another 5 times it will be at 10.001 since it is still rounding. If you put a value of 1.0001 in the Move window and drag a Part from the 0 axis 5 times (5.0005 studs) you should see the the Part’s Position round up to 5.001. 001 value since that is what is displayed. 0001 in Studio by entering that value in the Position of a Part. Same reason why 0 degrees of Rotation sometimes displays as -0. 875 (all 1/8 increments) usually fixes that issue since those values convert to base 8 values perfectly. Small changes don’t cause issues, but if you do it as you have been you’ll notice it. 
So as you move something it will continuously get further and further out of sync. Computers use a base 8 binary system of representing numbers which doesn’t work well with base 10 decimal numbers.
0 kommentar(er)
