[1564] Players desync on join, and cannot be re-synced
tracked
°sky
Upon joining an instance, it is possible for players to de-sync and not be able to re-sync until one user rejoins the instance.
Upon de-sync, it appears one player just does not get networked at all, and their nameplate does not show however their selection tictac does.
Log In
TummyTime
I guess this is relevant in this one. https://feedback.vrchat.com/bug-reports/p/invisible-user
StormRel
tracked
StormRel
needs more information
Hackebein
Did you by any chance leave a station with the invisible one before? Or does the world something with stations?
I have seen this exat bug multiple times. where multiple people couldn't see me after leaving a station. It happens to me with avatar and world stations. Workaround is to hide and show the user. This is an old bug i reported a long time ago.
BobyStar
This is related but may not be the same issue as the "gaslighting" bug. Joining an instance and seeing one or some players stop existing. Rejoin or block/unblocking effected players usually fixes it.
Something odd that also fixes it is if Udon sets that particular's voice settings to some value which seems to force that remote player to refresh and fix themselves.
I discovered this on accident when I got the bug with a set of Build & Test clients. No networked values from that player are received but changing the local preceived voice gain to 0 and back up fixed that bugged remote player.
°sky
StormRel
°sky: Please provide logs! If they're too big to post here you can create a support ticket and link this post.
°sky
StormRel sorry for the delay, this was on my to do list and then i forgot 💀
attached both mine and the other persons logs
Truce
°sky and BobyStar: Have you experienced this at all on client versions other than 2025.1.1 beta?
°sky
Truce im not instance hopping enough for me to tell unfortunately. I also dont know reproduction steps to test
BobyStar
Truce I've experienced this on a variety of client versions though the last one I encountered was on 12/3/2024 (whatever latest live version was that date).
I also don't hop enough to know how to reproduce it but it seemed to happen a bit often when doing build & tests with persistence & player objects (likely a coincidence).
Was testing a fun idea with a video player (ProTV) on a pickup that was on a VRC Player Object. This caused it to happen twice in a row in build & test and never again.
Truce
BobyStar: Thanks, that at least tells me that it's not a regression caused by something in the 1.1 beta!
°sky: Thanks for the logs! There was an error message in there that gave us good idea of what we need to watch for.