Difference between revisions of "Running Bug List"
From Bitfighter
Watusimoto (Talk | contribs) (→General Bugs) |
Watusimoto (Talk | contribs) (→General Bugs) |
||
| Line 11: | Line 11: | ||
# If game can't write to level folder (simulate by adding .standalone to install folder on windows, for example), testing a level will fail (obviously), but will not tell you why until you press escape. | # If game can't write to level folder (simulate by adding .standalone to install folder on windows, for example), testing a level will fail (obviously), but will not tell you why until you press escape. | ||
# Slashes/backslashes mixed on F7 screen for windows | # Slashes/backslashes mixed on F7 screen for windows | ||
| + | # Start Bitfighter, edit a level with forcefields (but do not test) quit, then host, you will get spurious forcefields | ||
Revision as of 00:43, 10 December 2012
Contents |
This is a running bug list.
General Bugs
- Joining a game already running won't show your badges in the scoreboard until next level. Existing clients get info on the joiner, but joiner doesn't get the full 411 on the existing players. GameType::serverAddClient::s2cAddClient isn't sending proper badge info to joiner.
- When all players on a server go /idle, something bad happens
- Black screen of death reported with /idle. Maybe we should look into preventative measures like forcing menu to be available still, etc..
- When testing a level, enter full screen unstretched, then go back to editor, then test level again. You will now be in fullscreen stretched.
- If game can't write to level folder (simulate by adding .standalone to install folder on windows, for example), testing a level will fail (obviously), but will not tell you why until you press escape.
- Slashes/backslashes mixed on F7 screen for windows
- Start Bitfighter, edit a level with forcefields (but do not test) quit, then host, you will get spurious forcefields
