Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
This post has been closed. You can still view previous posts, but you can't post any new replies.

3D dice rolls don't always match what is given in text chat.

When rolling the 3D dice, the result shown on the die doesn't consistently match the number displayed in the text chat.
1350576418
Gid
Roll20 Team
Bone, could you supply your browser specs - <a href="http://supportdetails.com/" rel="nofollow">http://supportdetails.com/</a> Also, how often does this happen? Thanks!
I and my players have seen this too, so Bone G isn't imagining it. We've turned off 3D dice for performance reasons (plus we play d100 games so it isn't that useful). My broswer specs... Operating System Windows Windows 7 Screen Resolution 1280 x 1024 Web Browser Chrome 22.0.1229.94 Browser Size 1280 x 896 Color Depth 32 Javascript Enabled Flash Version 11.4.31 Cookies Enabled User Agent Mozilla/5.0 (Windows NT 6.1; WOW64; chromeframe/22.0.1229.94) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4
1350639697
Gid
Roll20 Team
I'm not implying you're imagining it, Mr G, but I need some more specifics. How often does this occur? Is this in Roll20 proper or in Hangouts. If it's the latter, does this happen when Hangouts typically has one of its performance spikes that requires a browser refresh?
And I'm certainly not suggesting that you're implying I'm imagining it either :-) Yes, this behaviour was seen (twice, on separate occasions) in a Hangout that was running slowly, with ca. 15 second delays between typing the command and seeing the result. We've not seen it in native Roll20, but as we very rarely use Roll20 natively (once since the Hangout function was released), we wouldn't do.
1350935035
Gid
Roll20 Team
:) Ah ha! I believe this isn't so much a bug as it's one of the native issues when running a game in Google Hangouts. Synching in Roll20 gets exponentially worse in Hangouts the longer your play session goes. I've noticed this behavior myself with the dice due to this issue. If you see this occurring again, I'd recommend that you and your players refresh your browser window. That should fix the problem. As a general rule of thumb for swift gameplay in Google Hangouts: Force a refresh if you or your players ever begin to notice the chat log/video feed/dices rolls/token movement starting to lag behind. Hopefully this addresses Bone's issue as well. If the problem with the dice is more persistent than a simple refresh, let us know!
I personally have only used native roll20. My players and I are all using the most recent version of Google Chrome. Our overall system specs vary. I have experienced this error on two different computer systems in my home, still using Chrome. When this error has occured, all involved in the game can see the error.
It has occured thrice that I can recall since we've started using Roll20 a month ago.
1350960923
Pat
Pro
API Scripter
This happened in our game tonight as well. Had players in Chrome, FFox, and IE and all were seeing the mismatch.
1350991125
Gid
Roll20 Team
Alrighty, since it sounds like this is also an issue with native Roll20, I just sent off a bug report to double check there isn't something wacky going on. Thanks for the info everyone!
This is a "bug", but I'm not sure if it's something we'll be able to fix perfectly. To understand what causes it, you have to understand that we are performing a real, not-predetermined physics simulation in your browser when you roll 3D Dice. So that means we don't know the outcome ahead of time. So what's happening is, when the dice bounce around, we're constantly doing a check to see which dice face is pointing "up". This works really well 95% of the time. However, on occasion, the dice will do something crazy, like hit a wall weird, or they'll act like they've stopped rolling (based on their velocity) but then roll anyway, that sort of thing. Usually when this happens the "reader" thinks the dice has stopped rolling and then it ends up moving ever so slightly and the "top" dice face changes. We can keep tweaking the "reader" part to make it more accurate, but at the end of the day since we don't pre-generate the result, we can't 100% guarantee we're reading the dice correctly. But at the end of the day, you're still getting a random result, it's just maybe not exactly what's showing on the 3D Dice. So, we'll keep tweaking the reading part of things to make it more accurate, is I guess the short answer :-)
My players are well trained now to hit F5 at the first sign of any funny business or hint of lag. :-)
1351008536
Gauss
Forum Champion
Riley: Not that I am a coder or anything but perhaps you could kill two birds with one stone? Increase the time the dice remain on the table (as it is we can barely count the dice before they vanish) and increase the time between the dice being rolled and the dice being reported in chat? - Gauss