When a World is Updated Current Instances Become Unjoinable
closed
owlboy
When you update a world that is active with users all of the current instances stay active and any new users who join those instances are presented with terrible performance. Sometimes it is so bad you need to just kill the VRC client.
This is a terrible impression to leave on new users or ones new to VRC. It also makes updating a world in time for an event a chore.
This is not to mention just simple issues with the world not being in sync visually/structurally/functionally even if it did not run terribly.
Obviously it irons out over time. But as long as an instance is open and active that was started with an old version there is a chance all new users will end up in it and depending on the severity of differences in the versions they may end up in a world that actually basically makes their client unusable.
Log In
Tupper - VRChat Head of Community
marked this post as
closed
Closing due to age, please make a new post if it is still relevant.
euan
Is this issue still relevant? (cleaning out old posts)
danly
euan: It is. It should be marked under investigation.
owlboy
Version Number:
ALL VERSIONS
Raccoonteur
So this is why on St Paddy's day when I joined the Pug for the big celebration, the frame rate was awful for the first hour or two!
owlboy
Raccoonteur: Yeah, sorry about that ☹️
Raccoonteur
owlboy: Do you know what exactly causes this? Like, is it that the triggers which enable culling stop working, and so every part of the bar, and all avatars, are rendered at once?
owlboy
Raccoonteur: Nope, nothing about the graphics at all. Or even player count and dynamic bones or any of that.
It's literally the networked events failing over and over at a rapid pace. Be them ObjectSync events, or Trigger events, or events related to things like video playback components.
akalink
Is it possible for the devs to
make it so it just locks the currently active instances from joins if the world is updated?
Noe
Merged in a post:
Client Freezes when ObjectSync is added to an Object and players are in different versions of the world
owlboy
So there is a huge bug in how VRC handles people being in two different versions of a world. If objectSync is added to an existing object and you try to join the world when the instance was made in the old version and still has people in it (a version without ObjectSync on that Object), the client just freezes on join.
This makes updating the world a nightmare because nothing is done to make sure everyone is on the same version AND because they are not on the same version late joiners freeze. The idea that the instances will slowly die out is unacceptable.
Either everyone needs to be forced to the same version, or the client needs to handle this gracefully.
Maybe of note: In my case Sync physics, and collision transfer were both off on the ObjectSync component.
tupper
Honestly I wish there was a way that you, as a world author, could just push a big red "force rejoin" button that would knock everyone out and back into the instance they're in (for all instances open) for any given world you own.
owlboy
tupper: Sadly this does not address my issue. Even if I had that button on Halloween I would not have been able to press it because the whole client was running at sub 5FPS. (unless it was web based)
tupper
owlboy: I mean, the idea is that you could press this button from any instance, and it'd affect all current running instances of your world.
owlboy
Instances should be reset upon update of the world. Or new users should be barred from joining that instance and it should be left to expire once everyone leaves.