Unity-Technologies / Unity-Technologies/com.unity.netcode.gameobjects

Sharing ownership between two players

Abierto
#2,558 3 comentarios 0 reacciones 1 asignado Ver en GitHub

@NoelStephensUnity ya está trabajando en esto.

Desde el 10/5/2023.

stat:Investigating Tracking type:feature
Lenguaje dominante
C#
Estrellas
2.3k
Forks
461
Merge medio
3 d 16 h
PR fusionados (30 d)
20

Descripción

This is a follow up question after #2512, where @NoelStephensUnity helped me a lot with making a solid and smooth movement of an object by a player.

But since multiplayer games are about cooperation, carrying stuff together is one of the essentials features in our game.
I'd like to make it that when one player tries to carry a large thing, it struggles, whereas two can do it easier.

The problem is, they both should be able to move the object they are carrying. And they are client-side authoritative.
So I can't just change the ownership of the object, because another player is going to have a delay.

The only idea I have is to let them simulate locally object's state, ignoring the correct one from the server. And once they drop the object, it switched back to updates from the server. I think this should work, at least, I can't tell why not.

But I think I don't understand the solution @NoelStephensUnity provided me with to 100%. I see that it disables server updates and lets client simulate rigidbody, but it also handles the jitter problem by making sure that the authority is completely switched, and I just don't understand how I can make it more generic, so I could just toggle it when I need it.

Do you think it's going to work or I am completely wrong about the approach? Maybe it can be achieved easily?
If so, could you please you elaborate on your solution? As I said, I'd like to make it generic.

Thanks a lot!

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.