vrcbce
vrcbce copied to clipboard
Couple of Issues with newest release
Here's a couple of issues, I've noticed in my world with using this asset.
Using M.O.O.N's UI Pool Table Prefab.
- Pool Tables automatically reset during playing the game.
- Pool Tables UI gets stuck/locked if someone starts the game and leave, making the pool table complete useless. (I'm not sure 100% how this happens, just speculating. However this issue was happen.)
Unable to reproduce this in some simple checks: I'll need more information.
I'm not sure how to fully reproduced the issues. Just wanted to report them, cause I'm quite confused why or how it's happening as well.
Natalynn: If you want confirm it's bug, better start new scene, put only the table prefab, and play with it in test world. If you can find bugs in the UI even in the test world, means you can reproduce the bug, then FairlySadPanda can fix it.
If bug cannot reproduced, then it's most likely caused by the world itself, other script can interference, or some world parts, like colliders in floor and around, can interference the UI.
Natalynn: If you want confirm it's bug, better start new scene, put only the table prefab, and play with it in test world. If you can find bugs in the UI even in the test world, means you can reproduce the bug, then FairlySadPanda can fix it.
If bug cannot reproduced, then it's most likely caused by the world itself, other script can interference, or some world parts, like colliders in floor and around, can interference the UI.
The thing is, I've uses the pool table before this new ui update stuff and it worked fine no issues. Then I've tried m.o.o.ns and stuff broke. But i'll keep experimenting.
Oke, i noticed 2 problems you talked:
- sudden reset: happens when some1 left world. This issue chance is very low. So far i see we win game.
- stuck in game mode, no reset possible. Possible if someone left?
Thats good, I'm not the only one.
Have fixed up the player departure code in 1.1.5 to stop the InstanceOwner being needed to handle people who leave (!!).
The sudden reset bug I'm unsure on.