This is my first post on the devforum, hopefully i got this all right…
So here’s my problem. The parts appear to glitch out and are floating behind, but when I stop, it comes back in. Also sometimes the parts will fall out because of this and then are left behind. And im not sure what to do about it…
It looks like the spheres are simulating under a different network owner, but that’s weird since they’re really close to you and there’s no one else to own them. Alternatively, it could be the way you’re moving the cart isn’t playing well with physics.
When not in ‘play’ mode, the cart and spheres are the same color, but when I enter the cart in play mode, the spheres and cart are different colors.
I am using a vehicle seat because it is meant to be a easily controllable minecart, and using user input rather than programming a path.
You should be able to solve this then by setting all of the spheres’ network owners to the driver. At first you can just manually do this to make sure the fix works, but once you verify it does you’ll have to do some math to detect if objects are in the cart or not and switch network ownership when they enter it. Alternatively, what TreeLands does is weld the spheres to the vehicle whenever it starts moving, and unwelds them whenever it stops (at least, this is what it appears to do from observation).
I would also file a bug report with a repro rbxl file demonstrating the issue. You can use the post approval process linked in the forum rules to file one.
Quick question, how would you set the sphere’s network owner to the driver?
Thiere is also SetNetworkOwnershipAuto if you want to switch back to letting the server decide who should own a part. Note that these can only be used from server scripts, and not the client.
Also relevant:
This is how the minecart and spheres currently play out.
The small gray platform is to change the network ownership to the player.
When I hit the turn, the ores appear to leave the player ownership range, and change back to server ownership. But then they won’t switch back afterwards.
Note: it took longer to reply because i didn’t know the video was too large of a file size.
Yeah, this definitely looks like a physics bug. You’ll have to file a bug report in #platform-feedback:engine-bugs with a repro rbxl file so this can be fixed. To work around this in the meantime, you’ll need to explicitly set the ownership of all ores to the server (if you let the server automatically do it, they lose ownership later) or weld them to the cart.