[1727] PlayerObject ownership issues
tracked
SenkyDragon
It's difficult to provide a reproduction for this issue, but Kaleidosky has an issue with the open beta only which can only be explained by players in the beta thinking that they own more than one instance of a PlayerObject. I'm unsure if they are getting two instances created for themself, or if they incorrectly think that they also own a PlayerObject that belongs to someone else.
I'm unsure, but this may also be related to VRCObjectSync.Respawn not working properly in the beta, if the beta user thinks they own an object they are respawning which they actually do not.
Log In
This post was marked as
tracked
_
_tau_
Do you have any repro steps for this at all?
SenkyDragon
_tau_ Looking into this more closely today, it seems my original root cause was probably incorrect. From the symptoms and the exact u# code, I no longer think it's related to owning multiple PlayerObjects.
I'll have to add more logging for the next big event, since I can't seem to be able to reproduce it with only two clients. There is very likely /some/ new regression in the open beta, since this impacted multiple users in a giant instance, and the common connection is that all of them, and only them, were on the beta, but it must be caused by something else.
Feel free to close this for now and I'll loop back if I find something more.