BuzzerBeater Forums

Bugs, bugs, bugs > Match Viewer Bugs

Match Viewer Bugs (thread closed)

Set priority
Show messages by
This Post:
00
1821.57 in reply to 1821.56
Date: 11/2/2007 2:36:16 PM
Overall Posts Rated:
00
It's my first week in BB and I was looking after training results. I trained Stamina.
Is it possible that I had no advance in Stamina nor any change in any player DMI ?

From: Vikman

This Post:
00
1821.58 in reply to 1821.57
Date: 11/2/2007 3:18:36 PM
Overall Posts Rated:
11
No, this is a training bug...check this topic out(5454.1)

This Post:
00
1821.59 in reply to 1821.1
Date: 11/4/2007 1:23:15 AM
Overall Posts Rated:
44
the fast forward works for times in the first four quarters, but for OT it treats them as if they lasted 12 minutes (so a 1st OT is treated as lasting from 48-60 minutes, and you need to FF to 55 minutes to get to the actual start of play in the OT. For a second OT, you need to FF to between 67 and 72 minutes.

This Post:
00
1821.60 in reply to 1821.59
Date: 11/4/2007 1:59:48 AM
Guma Terror
I.1
Overall Posts Rated:
3131


im not sure if this belongs here or if it is just a translation problem



but in the commentary says: player XXX receives the ball from player YYY. player YYY shoots the ball.

it should be the other way around.



also in today´s game a player of mine shoot the ball , and the commentary said UNDEFINED as the result of the shoot ¿?



From: dhoff

This Post:
00
1821.61 in reply to 1821.1
Date: 11/4/2007 2:52:31 AM
Overall Posts Rated:
1919
I like the "Half time. Play will resume at ..." message. I meant to suggest something like that a while ago. :)

One problem, though. When I reload the matchviewer during halftime, the "play will resume at ..." message displays a different time. It looks like it just adds 10 minutes to the time (my computer's time, not the time of daythat BB displays in the browser) at which I reload the viewer. (Makes sense if I watch the whole game without reloading between halves, of course.)

This Post:
00
1821.62 in reply to 1821.59
Date: 11/4/2007 7:10:47 AM
Overall Posts Rated:
77
the fast forward works for times in the first four quarters, but for OT it treats them as if they lasted 12 minutes (so a 1st OT is treated as lasting from 48-60 minutes, and you need to FF to 55 minutes to get to the actual start of play in the OT. For a second OT, you need to FF to between 67 and 72 minutes.


Yeah, I noticed that too. I spent yesterday fixing the list of bugs in regular time. I think they're all done now except for the players doing things in a funny order when everything happens in the same minute - which is due to a direct feed from the GE.

I've got overtime left to go through today, there are a few clock issues there.

From: BB-Oxidus

This Post:
00
1821.63 in reply to 1821.61
Date: 11/4/2007 7:23:17 AM
Overall Posts Rated:
77
I like the "Half time. Play will resume at ..." message. I meant to suggest something like that a while ago.

One problem, though. When I reload the matchviewer during halftime, the "play will resume at ..." message displays a different time. It looks like it just adds 10 minutes to the time (my computer's time, not the time of daythat BB displays in the browser) at which I reload the viewer. (Makes sense if I watch the whole game without reloading between halves, of course.)


That text has actually existed for a loooong time as far as I can tell. It was just hidden. So well hidden in fact, that the viewer couldn't find it :-)

I'll have a look at that bug.

From: dhoff

This Post:
00
1821.64 in reply to 1821.63
Date: 11/7/2007 3:06:41 AM
Overall Posts Rated:
1919
That text has actually existed for a loooong time as far as I can tell. It was just hidden. So well hidden in fact, that the viewer couldn't find it :-)

I'll have a look at that bug.

Not sure if you've looked at it, but here's something else. I left the matchviewer running through halftime. It said that my game would start up again at 8:58 (the half ended at 8:48). The game didn't start up again until 9:06.

From: BB-Oxidus

This Post:
00
1821.65 in reply to 1821.64
Date: 11/7/2007 3:20:57 AM
Overall Posts Rated:
77
I'm going to sort this out soon. I've just put in a new handling model for the XML interface to the viewer and fixed up some memory stuff so things shouldn't bloat so much. Boring, boring things :-) I tested it through the games today and it appears to work, so I'll get that published after the next slew of games on Thursday. Nothing exciting though.

It's all fits and starts at the moment, fixing things up on the site that need more immediate solutions, but I'm starting to see light at the end of that thar tunnel. Well, not really, but I can always hope :-)

From: dhoff

This Post:
00
1821.66 in reply to 1821.65
Date: 11/7/2007 3:33:35 AM
Overall Posts Rated:
1919
And since I've got you here, another thing with the matchviewer. I left the viewer open from some time in the first quarter through the end of the third quarter. When the quarter ended, I reloaded the page and the viewer showed me a point in the game with 8 mins left in the fourth quarter. I assume this is some sort of memory/bloat thing?

It's all fits and starts at the moment, fixing things up on the site that need more immediate solutions, but I'm starting to see light at the end of that thar tunnel. Well, not really, but I can always hope :-)


Oh, and watch out for that oncoming train. :)

From: BB-Oxidus

This Post:
00
1821.67 in reply to 1821.66
Date: 11/7/2007 4:14:37 AM
Overall Posts Rated:
77
And since I've got you here, another thing with the matchviewer. I left the viewer open from some time in the first quarter through the end of the third quarter. When the quarter ended, I reloaded the page and the viewer showed me a point in the game with 8 mins left in the fourth quarter. I assume this is some sort of memory/bloat thing?


That's to do with how flash handles the internal clock. It runs a routine once per second, but flash doesn't really have a good grasp of what one second actually means. So, slowly but surely it runs out of sync. The problem is obviously exacerbated by the fact that a small margin of error per second adds up to a lot over an hour. I'm working on a solution to re-sync the clock during the breaks ( and maybe timeouts ) so that this doesn't happen - or at least discrepancies to the magnitude of 4 minutes can be avoided.

Oh, and watch out for that oncoming train.


I'm made of rough cut diamonds and the clippings from Chuck Norris' beard. You should see the last train that hit me :-)

Advertisement