Advice and tutorials on how to simulate previous physics state

[pennyloafers]

Jittery RigidBody movement on client side

This script will pull the physics object on the server, collect the position rotation and velocities into an array and sync that to the client. the client will receive the array and update its local physics object in reverse, extracting from the array and placing it on to the physics server object. extends MultiplayerSynchronizer class_name PhysicsSynchronizer @export var sync_bstate_array : Array = \ [0, Vector3.ZERO, Quaternion.IDENTITY, Vector3.ZERO, Vector3.ZERO] @onready var sync_object…

I made a crude script to mess with the physics state using a multiplayer synchronizer. it could use some improvements but should get you started.

I want to adjust your perspective a little bit…

@rabidrabid

The clients render the world 100ms in the past in order to be able to interpolate and extrapolate networked entities and make it work smoothly.

This is true so remember this…

@rabidrabid

I need to validate the inputs of the players in the server, and since the player’s world is rendered 100ms in the past, when I get an input from the player sometimes I need to recreate the state of the world 100ms in the past in the server.

The player will have a ping, and lets say this is a round-trip of 100 ms. half is 50 ms. (one-way server to client)

Even though client is using state 100ms old, the server won’t see the players response until 200 ms later. (100ms state delay + ping rt)

From the perspective of the server the client is ahead of the server in time. And it will be since the client is trying to predict the server to allow a more responsive client.

I would read this and watch this.

Introduction to Networked Physics | Gaffer On Games

'Overwatch' Gameplay Architecture and Netcode