Difference between revisions of "Running Bug List"
From Bitfighter
Watusimoto (Talk | contribs) (→General Bugs) |
Watusimoto (Talk | contribs) (→General Bugs) |
||
Line 21: | Line 21: | ||
# <del>If unrecognized JS is detected, should use most recently selected joystick profile</del> | # <del>If unrecognized JS is detected, should use most recently selected joystick profile</del> | ||
# <del>Verify twoplayer.bat -- could not reproduce bug, even on same machine where it was reported</del> | # <del>Verify twoplayer.bat -- could not reproduce bug, even on same machine where it was reported</del> | ||
− | # Dissalow user names with "%" in them | + | # Dissalow user names with "%" in them -- this needs to happen at the forums level |
===OS X Related=== | ===OS X Related=== |
Revision as of 09:56, 13 February 2012
This is a running bug list.
Right now it's mostly for regressions after the release of 016
General Bugs
-
numpad keys are separate from their standard keyboard counterparts since the change to SDL. This makes loadout menus etc. not as workable - Preserving load-outs.
- Player has loadout xyz when level ends.
- Next level starts, player gets default loadout abc
- Player enters loadout zone -- should get loadout xyz again
- When level ends, current loadout should become "on-deck" loadout, at least on levels with loadout zones.
-
Mouse selection location problems when scrolling through levels -
Scrolling menus are wonky when typing letter to jump to relevant entry - Undoing insertion of vertices into walls can be quirky
-
2pt barriers with points on top of each other do not load in editor -- walls fell prey to culling mechanism that removed duplicate points from walls -
User has no way of knowing how to lay spybugs (advantage through obscurity!) -
Add info about presets to help -
If unrecognized JS is detected, should use most recently selected joystick profile -
Verify twoplayer.bat -- could not reproduce bug, even on same machine where it was reported - Dissalow user names with "%" in them -- this needs to happen at the forums level
OS X Related
- Crash when exiting from main menu sometimes on Mac (ppc only?)
- Switching to fullscreen on Mac sometimes makes the window disappear - may be related to loss of opengl context or error with opengl pixel format
-
command keys don't work on Mac -
Get Bitfighter working on Mac OS X 10.7 Lion
Windows Related
-
Exiting bitfighter with music playing will crash the game and spike the CPU. Possible solutions: