A LagCompensator Revamp

[Amph1dian]

Current Lagcompensator:

Supports box colliders,
Supports position & scale compensation.
Supports primitive movement systems.
Uses performance intensive methods. (addcomponent, destroy, instantiate, raycast)
Easy to script.
Very easy to implement.

Revamped Lagcompensator:

Supports any 3d collider type, including ragdoll rigs.
Supports position, rotation, and animation compensation.
Supports complex movement systems.
Optimized.
Easy to script.
May need refactoring to implement.

Animation Tracking & Compensation has been added. Note that it doesn't track or compensate for Blend Tree variables, that would be very hard to automate. you would have to manually set these in the compensated animator via script. OR edit the Lagcompensator to implement & interpolate these in Capture3d.

Usage is pretty simple, create dummy player with only trigger colliders. parent said dummy and the actual player under a main player GameObject. (may need refactoring). There's probably be a way to do this without parenting, not sure. Make sure to disable this by default, as it will be enabled when necessary by the server.

then just fill in the "tracked" fields with your actual player, and "compensated" fields with dummy player. the separated position / orientation variables are there for more complex player movement systems.

Animator compensation is optional.

Now you have 2 options for implementation, The first and easier version, await UpdateColliders(). you just put this before you Raycast in your servers Fire function. This also awaits a task inside of the function, not sure if its redundant.

Second and more performant option, UpdateTargetCollider() and DisableColliders() work together. DisableColliders() goes at the end of your servers fire function. Then UpdateTargetColldier gets called if the client hits a player with their local raycast. NOT the server. i think the best way to add this is to add a NetworkConnectionToClient target to your servers fire function, then calling await UpdateTargetColldier(target) before your servers raycast, if the target is not null.

[Amph1dian]

This could work in a similar way as mischa's version, only updating if the client hit the collider on their screen. it would decrease firing overhead, as your not always hitting a player, and thus dont need to update the colliders every time you shoot. however it would require more scripting from the user, as the user would need to add a different command to the clients fire function to update the collider.

^ added as UpdateTargetCollider() and DisableColldiers().

Only thing left to do is add 2d support, I think that would warrant a different script? like LagCompensator2d?
Although maybe it doesn't matter if its in 2d or 3d, if you set it up the same.

[TUTTIK-FRUTTIK]

I suggest using [ServerCallback] for Update()

[Amph1dian]

I suggest using [ServerCallback] for Update()

Wouldn't [Server] be better? Only difference on the docs is that it doesn't throw an error if a client calls the method, but all of the methods shouldn't be called on the clients anyways? I've only ever used [Server] myself, so I'm not sure.

[MrGadget1024]

I suggest using [ServerCallback] for Update()

Wouldn't [Server] be better? Only difference on the docs is that it doesn't throw an error if a client calls the method, but all of the methods shouldn't be called on the clients anyways? I've only ever used [Server] myself, so I'm not sure.

Have to use [ServerCallback] for Unity methods because Unity will call them in all contexts and we don't need the warning flood.

[Amph1dian]

Have to use [ServerCallback] for Unity methods because Unity will call them in all contexts and we don't need the warning flood.

Ah that makes sense. For some reason I thought the original guy meant swapping [Server] to [ServerCallback] on the Update methods I added, and not unity's one.