Difference between revisions of "Running Bug List"
From Bitfighter
Watusimoto (Talk | contribs) (→Non-bugs stuff to do) |
Watusimoto (Talk | contribs) (→Non-bugs stuff to do) |
||
| Line 58: | Line 58: | ||
##playerStats.teleport | ##playerStats.teleport | ||
#<del>Create rudimentary in-game leader board display</del> | #<del>Create rudimentary in-game leader board display</del> | ||
| + | # Players who are idle when game starts should not be added to a team, and, if they idle through entire game, should not be added to game stats | ||
| + | # If only one player playing goes idle (or two players, one idle, one not, and non-idle player quits leaving only one idle player), game should automatically suspend; some sort of hybrid "idle & suspended" notice should be shown | ||
Revision as of 19:39, 6 March 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 -
Core heartbeat is broken somehow -
Every gametype says 'Blast as many ships as you can' in the level info screen -
Hostile objects are pink/purple? Only on old levels, probably created with really old editor -
Hostile forcefield should let flags float through -
<space> to suspend snapping in editor doesn't suspend it for snapping objects at vertices (like a goalzone to a barrier)FEATURE NOT BUG (see update to editor help for explanation) -
Phantom forcefields appear when testing a level in the editor after adding forcefields. Has this been fixed?? -
Repairing Core is broken. How would we handle this with panels? -
Fix Game Parameters menu in the editor -- should not scroll -
Make core look good again! -
Spawn shield rotation is jerky (F32 v S32?) [not jerky for me -raptor] -
Editor crash when pressing Ctrl+R to add levelgen items, then Ctrl+R again to remove them -
Bursts only ever do damage to right-most Core panel, no matter the damage impact point
OS X Related
-
Crash when exiting from main menu sometimes on Mac, ppc only. Stack trace: http://pastie.org/3474625 -
Switching to fullscreen on Mac sometimes makes the window disappear - may be related to loss of opengl context or error with opengl pixel format.Workaround coded: Use FakeFullScreen, but you have to hide the dock -
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:
Non-bugs stuff to do
Get level stats into the database- Get an achievement working
- Get the following stats into the database; they are already sent to the master
- playerStats.crashedIntoAsteroid
- playerStats.flagDrop
- playerStats.flagPickup
- playerStats.flagReturn
- playerStats.flagScore
- playerStats.switchedTeamCount
- playerStats.teleport
Create rudimentary in-game leader board display- Players who are idle when game starts should not be added to a team, and, if they idle through entire game, should not be added to game stats
- If only one player playing goes idle (or two players, one idle, one not, and non-idle player quits leaving only one idle player), game should automatically suspend; some sort of hybrid "idle & suspended" notice should be shown
