-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The marker becomes impossible to grab if a person exits the instance whilst holding it #17
Comments
Thanks I'll look into it |
I wasnt able to repro, did this happen just once when the game crashed? If so thats a very rare case because just rejoining while drawing seems fine. Its also very unlikely the actual pickup stopped working since thats just a vrc component and I can't control how it works |
I know for sure that it happens every time that either a game crash or the in-game "VRChat has stopped responding" popup occurs whilst holding the marker. You may want to try ending the task with Task Manager instead of rejoining. |
Unfortunately, neither disconnecting my internet, nor force-killing the VRChat process can reproduce the bug. However, it still exists. I know it seems oddly specific and rare, but when public group instances run for 24+ hours, there's usually at least one massive flood of ink all over the map from some random bored user who eventually crashed in the middle of drawing, leaving the marker stuck in limbo. This leaves a big mess that is completely impossible to clean up, since the erase button can no longer be interacted with. I haven't actually tested the force-killing of the application in a lobby with more than 2 people, so maybe the player count plays a role. If that's not the case, I may just have to find a way to force the game to crash. |
This issue usually occurs due to an unexpected game crash in the middle of drawing. The marker is no longer able to be grabbed or have its drawings cleared for the remainder of the lifetime of the instance.
The text was updated successfully, but these errors were encountered: