why is movement so choppy?

[molten zodiac]

I don't understand why movement is so choppy for other players.

[noble cipher]

try sending the script

[molten zodiac]

screenshots of relevant scripts:

[north niche]

you ought to use :setnetworkowner

[noble cipher]

yea on the hrp u can do that

its also maybe cause of the weld constraint

[molten zodiac]

wait who should get networkownership of what?

[ornate lynx]

** You are now Level 1! **

[north niche]

idek

plr2prob

it’s your mission to figure out

[silent sphinx]

you need to add position interpolation

[noble cipher]

ye

[molten zodiac]

what is position interpolation and how do I add it

[silent sphinx]

you know how the client runs faster than the server (potato pc´s excluded), well thats why its choppy, the server sends updates to clients at 20Hz (<citation needed) and clients ussually run at 60Hz, so you need to interpolate the 40Hz of difference

[molten zodiac]

how do I do the math on what the lerp alpha should be?

[molten zodiac]

also uhhhh how do you get lerp to work with linearvelocity?

[molten zodiac]

ok I think I did everything but its still choppy idk why

also choppy on server side :(

[plucky thistle]

userinputservice.inputbegan( while true do ... end) you should never have an infinite loop in inputbegan for starters.

and best i can tell, it looks choppy because you're setting cframe every frame, there is no physics so other clients cannot interpolate and don't know how the character is moving.

[plucky thistle]

also there is no localplayer on the server and you don't need to setnetworkowner since the player usually already has network ownership of their character

[molten zodiac]

would it be better to put the userinputservice function in the renderstepped function or do something completley different?

[ornate lynx]

** You are now Level 2! **

[plucky thistle]

"is it better" and "should i" questions are questions i refuse to answer. that's your job to figure out i'm only going to get you to working.

and to that end i suggest you add prints to a bunch of places because i suspect code is running multiple times because of that loop, so your interpolation is even worse.

[molten zodiac]

nah its just that removing the while loop changes the movement in a way that I really dont like so I have to troubleshoot that first lol

[molten zodiac]

changed up most of the movement script but its still having stutter issues :(

i'm actually gonna blow my brains schmoove off at this point

like what the hell

[molten zodiac]

ok so movement is still choppy, and I'm not sure what to do. This is the script i'm using. What am I missing?