We have already identified the issue, and I gave them a straight forward answer on the most efficient way to solve their issue. I’m just waiting on a reply or for them to test it. Feedback and advice is welcome
Could you use a remote event to keep it firing at the torso/root part
1 Like
Yes, that is what I recommended to them already
Btw task.wait I think can only run task.wait(0.03)
task.wait() is the lowest amount of time it can wait.
Task.wait() will yield to a single frame, which would represent roughly 0.015 of a second if playing on 60 FPS.
Hey there, sorry for the late reply(again) I will test this with a friend (until they answer me lol), If it works, ill mark this reply as solution, thanks for your help!
No problem! If you have any questions, let me know.
1 Like
I think task.wait only goes to 0.03 max i meant
That’s “wait()”, not task.wait()
huh maybe I always thought it was task.wait
SetPrimaryPartCFrame is Deprecated. He should use PivotTo()
1 Like
I used CFrame.lookAt, does that make any difference?
Sorry, but it’s different. If you do this, you’ll end up using a high amount of bandwidth as you’re sending data to the server 60 times a second, which isn’t the best, especially when you want your game to be as optimized as possible. I suggest OP (@GreatSword707) to reduce the amount of times data is sent to the server every second, maybe fire the remote event 10 times a second and use linear interpolation on the server. The players might notice it, but it’s for the best.
1 Like