Owner information is not correctly synced to new players when there are many UdonBehaviour objects.
in progress
TORISOUP
[Steps to reproduce]
- Lay out many (about 50 or more) MonoBehaviour and VRC_Pickup objects in the scene.
- Enter the world with 3 or more people.
- All player pick up and move some objects.
- Join a new player.
- The coordinates of some objects are not synced correctly to the new player.
[Cause]
Maybe, ownership information is not correctly transmitted to new player.
In the new player, owner of some objects will appear to be the master.
But the owner is actually a different player.
So the coordinates by the true owner send to be ignored, the new player will see the object appear to be stationary from its initial position.
Also, if an object is picked up by the true owner of that one, SetOwner is not called.
So new players will continue to recognize that the master is the owner.
[Interim measures]
Always the master keep to hold all ownership of objects.
Log In
Phasedragon
in progress
Marking this as in progress but really it's been in progress for a while now! We're working on an update to networking that overhauls some backend things that won't actually add any new features, but will fix many long standing and painful bugs related to ownership such as this one. Of course we have to be very careful with anything related to networking and so these changes need to be tested and iterated on thoroughly to prevent new bugs from slipping in. Sorry that it's taking so long!
Reimajo
Phasedragon: Will it also fix the issue that the gravity flag/kinematic flag doesn't properly sync when being changed from an external U# script (we talked about this lately) (see https://feedback.vrchat.com/udon/p/vrcobjectsync-doesnt-sync-gravitykinematic-flags-reliably)?
TORISOUP
It's a test world.
If the number of participants is small, it's not a problem, but if there are more than 4 or 5, it becomes unstable.
wrld_da4a743b-fca0-4993-9c3f-c3d494fe4f23
AirGamer
TORISOUP: Are you still seeing this issue? I used to have this issue in my world, but I'm not seeing it in 1069.