Log Viewer Beta 1 Feedback

Apr 23, 2006 14:13
BruceCampbell wrote:
When tank A is killed by tank B, the log viewer displays it as:

"Tank A just killed player Tank B"

It's backwards.

Thanks, will change the display for the next version to make it around the right way.
Apr 23, 2006 14:17
To reiterate zzz's comment a while back, I think the event window and listbox should be resizable, as well has using a horizontal scrollbar for longer messages.

UROX
Apr 24, 2006 01:12
Elvis wrote:
I've now chenged the log file download name to be:

<timestamp> - <map name> - <WBN players>.wbv


Elvis: That's really cool. Thanks, it's been helpfull.
Apr 24, 2006 09:47
Version 1.01
------------

Pressing the fast forward button when it was at
Log Time: 09:26
Then pressing one more time resulted in:
Log Time: 1470:52

Some names leave trailing white pixels. E.g:
Inuyashax leaves white pixels in the screen.
Apr 24, 2006 10:26
(-_-)zzz wrote:
Version 1.01
------------

Pressing the fast forward button when it was at
Log Time: 09:26
Then pressing one more time resulted in:
Log Time: 1470:52

The log viewer automatically skips over empty periods in the log file. You can use the other forwards button to fast forward.

Some names leave trailing white pixels. E.g:
Inuyashax leaves white pixels in the screen.

Thanks will fix for next version. Moving the screen will the currently resolve the problem.
Apr 27, 2006 07:37
Pressing the FF button while watching at 2x speed caused the replay to stop. Pressing the RW button at that point locked up everything. CPU usage went to 100%.
Apr 27, 2006 07:49
Also, pressing FF and RW buttons repeatedly while watching at 2x speed an error dialog appeared "Error:Corrupt Log"
Apr 27, 2006 10:50
Please provide the log file refernce and log viewer version number you are using to encounter these problems.
Apr 27, 2006 20:25
Elvis wrote:
Please provide the log file refernce and log viewer version number you are using to encounter these problems.


Log viewer: 1.01
Log file: http://www.winbolo.net/gamelog.php?mode=logfile&key=c5bf321dca9748b578247055550961e8

To make it say corrupt log file (works 30% of the time):

Have it on tank centered at normal speed (1x)
Press play, let it play for 3 to 4 seconds
Then keep clicking the FF button (about 15 times)
The viewer will either seriously crash (memory violoation) or say corrupt log file. I've only seen the memory violoation 1 time.

If it says corrupt log file, then usually pressing Ok will close the file. Sometimes there are 2 error dialogs and pressing OK on one of them freezes the application. If the OK button worked then the file will close, but the Rewind button in the Controls dialog will still be enabled. Pressing it will crash the log viewer.

Around 2% of the time I see the game get stuck. It says it's playing but the game doesn't change state.
« Previous 1 2
Page 2 of 2 (34 posts total)