Replicating smooth movement for a detailed model.

[blissful sandal]

Hey, could anybody offer any advice on what the most efficient way to smoothly move a highly detailed model containing thousands of parts would be?

right now I'm thinking either:

• occasional server updates at like 2hz or so, the client would interpolate between those positions

or:

• model is only rendered on the client, while the server renders a much more simplified collision model

[oblique surge]

Don’t move the big detailed model on the server.
The server should only move a simple invisible object that handles collisions and gameplay.

Each client then has its own detailed visual copy of the model.
The server just sends occasional position updates (like 5–10 times per second), and the client smoothly interpolates the visuals between those updates.

So:

Server: small, simple, efficient, authoritative

Client: big, detailed, smooth, visual-only

This keeps movement smooth, saves bandwidth, and avoids lag—even with thousands of parts.

[marsh hull]

just render it in the client, and the server just only checks if it's moving weirdly to prevent cheats by waiting for the client to send smth with an unreliable remote event (since ur updating it fast) sends the position only of the model and then checks the previous position etc for just checking if it moves weirdly

bc if u move it in the server and in the client, not sure if itll like spike lag or something every move 2hz