Question 1.0.0-exp.8: how do I enable predicted physics?

Is predicted physics enabled by default in 1.0? It's not quite clear to me from the docs if there's something I need to do.

Or perhaps I'm doing something wrong. I'm trying to fire some projectiles that have a physics body+shape and are owner predicted. When fired on the client, the projectile seems to not move until it's fired on the server (I put some simple logging in and increased simulated RTT to determine this), at which point it snaps forward on the client to where it is on the server.

Any ideas what might be wrong here? I can provide more info if needed.

 

From the manual:

In order to to use physics simulation for predicted ghosts you must enable it by creating a singleton with the PredictedPhysicsConfig component. The singleton must exist on both the client and server with compatible values (same simulation frequency). The component lets you specify the physics tick rate as a multiple of the NetCode simulation tick rate, so you can run for example a 60Hz game simulation with 120Hz physics simulation.

Which can be found in the physics section:
https://docs.unity3d.com/Packages/com.unity.netcode@1.0/manual/physics.html

The component is now named “NetCodePhysicsConfig” (if I remember correctly).

you can verify that physics prediction is working if you have the physics systems inside the prediction on the client side.

If that is still unclear let me know.

 

This has confused me a bit because it seems to me to always move the physics now unconditionally?

Code (CSharp):

1. [WorldSystemFilter(WorldSystemFilterFlags.ClientSimulation | WorldSystemFilterFlags.ServerSimulation)]
2. [UpdateInGroup(typeof(InitializationSystemGroup))]
3. public partial class PredictedPhysicsConfigSystem : SystemBase
4. {
5.     protected override void OnUpdate()
6.     {
7.         MovePhysicsSystems();
8.         var physGrp = World.GetExistingSystemManaged<PhysicsSystemGroup>();
9.         physGrp.RateManager = new NetcodePhysicsRateManager(physGrp);
10.         World.GetExistingSystemManaged<InitializationSystemGroup>().RemoveSystemFromUpdateList(this);
11.     }

So my question is more, how do I make it not predicted physics

 

Interesting, maybe they move it now always as you also have a client only physics system with the proxy?

but I haven’t looked deeper into that part just yet.

does it cost any performance if none of the ghost entities are predicted?

 

Thanks for all the info. It looks like the physics systems are indeed running in the prediction group, so maybe I'm doing something wrong.

 

I did some debugging and it looks like the velocity is getting forced to 0 for some reason on the client.
client:


server:


log:

 

I have some additional info. I just learned how to use the Journaling window.

 

Good to know, thank you! Is there a place I should look for known issues?

 

Could this issue also affect kinematic objects which are moved byphysics (using
PhysicsVelocity.CalculateVelocityToTarget).

As we experience less smooth behavior currently compared to 0.53 on player input moved objects. Could this be related?

 

Sorry for the slow reply. I went on holidays and came back to my house being flooded by a river...

So I've been busy ^ and I haven't tested enough to say for certain this is how it works, but I believe my problem stems from the fact I only use interpolated ghosts and no prediction.

In this case I can't see why my client only physics objects need to exist in a secondary physics world instead of all existing in the same world. I don't want the overhead of running 2 physics simulations for no reason - I was already having problems with physics.

 

I'm trying to figure out if this is required if I'm using interpolated only or if it's possible to avoid and use a single physics index

 

how to collide with different world (Physics Predict World And Client Only World), In document, say use PhysicsProxyGhostDriver component, but I dont see this componet in network package。

 

What has been changed at 1.0? At 0.51 I can trigger physics but it's no longer working at 1.0. What should I change to get back the same bahavior?

 

I know the bug fix u mention but I'm saying another issue. Currently at my game project, I have pickup that using trigger physics to detect when player go and pick it. The pickup is working at 0.51 but not working anymore at 1.0. Any idea why?

 

At Physics Shape authoring there's Collision Response option, Raise Trigger Events is selected