Difference between revisions of "Running Bug List"

From Bitfighter
(General Bugs)
 
(334 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{TOC right}}
+
To view and report bugs, go to http://code.google.com/p/bitfighter/issues/list
  
This is a running bug list.
 
  
===General Bugs===
+
==019d==
 
+
1. Check paths in diagnostics page (press F7 twice, page 2), bad paths and missing level, scripts, bots, editor plugins on mac OS version.
# Fix twoplayer.bat
+
# Joining a game already running won't show your badges in the scoreboard until next level
+
# There are several 'idle' bugs.  Sam and I got into a few inconsistent states mostly when forcing idle by either doing '/idle' or being killed while typing; we would then have a level change or restart:
+
#* scoreboard showed we were idle but we could move around and still play
+
#* if we were in this pseudo state and forced another idle, the screen went completely black and we could not respawn
+
#* restarting a level *sometimes* brought us out of the black screen of doom, but the scoreboard would still show that we were idle
+
# Client-side prediction mismatch with energy regeneration.  I've gotten it to show in two ways:
+
## Level 'Cold Storage' (because it has slipzones).  use up all your energy and then burst-propel yourself, don't touch any keys while moving; the energy regen should kick in and you'll see the energy bar be jumpy
+
## Level 'NASCAR track', use the pulse trick to constantly move around the track at top speed (because of the constant energy regeneration).  You'll see that you'll pulse several times in a split second because client thinks you have full energy, then the server puts you back in place - this makes for very jumpy play <b><==wat can't reproduce with either level!</b>
+
# Client-side crash with teleporters when really laggy on server:  http://pastie.org/5435323  <strong><== wat can't reproduce this, even with /lag 3000 30 3000 30, /restart .... however, game is completely unplayable!</strong>
+
# <del>Objective arrows are wonky (tested in Retrieve):  they don't point correctly to flags and sometimes don't point at all.  Also if two are captured by the other team, only one shows towards the flag, but points off-center?  Soccer example:  http://sam6.25u.com/upload/3screenshot_10.png</del>
+
# When going backwards at full speed with turbo on, firing a seeker causes it to immediately reverse direction and track you.  I think it needs to leave the ship pointing away from the shooter regardless of your speed.
+

Latest revision as of 21:29, 15 November 2014

To view and report bugs, go to http://code.google.com/p/bitfighter/issues/list


019d

1. Check paths in diagnostics page (press F7 twice, page 2), bad paths and missing level, scripts, bots, editor plugins on mac OS version.