How to use GhostPredictionSystemGroup.ShouldPredict before updating an entity if using DOTS Physics?

From the docs:

Client
The basic flow on the client is:

• NetCode applies the latest snapshot it received from the server to all predicted entities.
• While applying the snapshots, NetCode also finds the oldest snapshot it applied to any entity.
• Once NetCode applies the snapshots, the GhostPredictionSystemGroup runs from the oldest tick applied to any entity, to the tick the prediction is targeting.
• When the prediction runs, the GhostPredictionSystemGroup sets the correct time for the current prediction tick in the ECS TimeData struct. It also sets GhostPredictionSystemGroup.PredictingTick to the tick being predicted.

Because the prediction loop runs from the oldest tick applied to any entity, and some entities might already have newer data, you must check whether each entity needs to be simulated or not. To perform these checks, call the static method GhostPredictionSystemGroup.ShouldPredict before updating an entity. If it returns false the update should not run for that entity.
​

I am using DOTS Physics. The translation/rotation is updated without a system of mine.

I would like to run prediction on Asteroids (not controllable) that are using PhysicsShape and PhysicsBody near my player.

Does NetCode automatically handle doing predictions correctly for DOTS Physics?

 

Do the systems that respond to the ICommandData need to be in a special group?

 

Got it.

So my InputResponseSystem (in which I change the PhysicsVelocity of a Player object) runs in ClientAndServer.

- I would assume the client "sees" the state of the game (the rendering loop)
- then an input is ingested to create an ICommandData (from the user responding to what they see)
- the ICommandData takes a while to get to the Server but should be immediately acted upon by by the client be cause it is predicted
- I would assume that I would want to change the Velocity BEFORE the physics is run (so it is not like the input had no affect on the player for a frame)
- And then build the Physics world AFTER that velocity update

So if that is the case it would be set up as:

Code (CSharp):

1. [UpdateInWorld(TargetWorld.ClientAndServer)]
2. [UpdateInGroup(typeof(PredictedPhysicsSystemGroup))]
3. [UpdateBefore(typeof(BuildPhysicsWorld))]
4. public partial class InputResponseMovementSystem : SystemBase

Resulting in:
- InputSystem running in GhostInputSystemGroup
- InputResponseMovementSystem running just before BuildPhysicsWorld


Does that work or would this cause unexpected behavior I am not aware of?