Weird I never really had this much problems with welds tbh. Try putting the model on workspace and run the game to see if the welds work which they should. Obviously something is happening on the client side wheb the client decides to clone the ship. What are all the methods you have tried?
1 Like
The same thing happens when I leave it in the Workspace and it is not cloned, the server sees it well but the Client does not
Well I have tried multiple things, use Remote Events, clone it with Anchored and Unanchored in the script, create the Welds
Constraints with an Instance.new () and different things where WeldConstraints were not active so Tween did not work. And all the other methods already mentioned.
I was looking at topics about problems with the WeldContraints and I found this one that happens exactly what happens to my model.
1 Like
Good to know! Did the post help? It seems as if he’s right as the server and client have some sort of latency against each other
1 Like
In the post no solution was clarified, I was looking at other posts, I saw one from 2 years ago where exactly the same thing happened and says that roblox is fixing it.
So it seems this is more of roblox’s fault then? Cause your code seems to be fine and everything. I say maybe try to contact toblox in a way? But I don’t think it would help much
1 Like
Ok, thanks for the help
(30ch)
1 Like