4
include(navbar.html.m4)
9
I've migrated this list to the SourceForge bug list. You can browse it
10
dnl ELINK(sourceforge.net/Feature Requests/?group_id=6185,here) and make additions to it.
11
dnl ELINK(sourceforge.net/bugs/?group_id=6185,here)
12
ELINK([sourceforge.net/tracker/?atid=657948&group_id=110997&func=browse],here) and make additions to it.
13
This page is kept for historical reasons.
16
SUBSECTION(Bugs with insufficient information to fix; I'm glad about all hints)
18
<li>Braking and turning at the same time speeds up ( could not reproduce ) </li>
19
<li>sound does not work sometimes (with winamp in background??)</li>
22
SUBSECTION(Probably unfixable bugs)
25
If an invalid (i.e. too big) screen resolution is selected,
26
strange things may happen; anything from crashes to running at a lower
27
resolution and only showing part of the image. Technically, those are bugs
28
in the display driver or OS; PROGTITLE can't do more than ask if a screen
32
Alt-tabbing out of PROGTITLE in fullscreen mode may produce strange behaviour;
33
if you hit it accidentally, better alt-tab back quickly... Window mode seems
34
to work flawlessly, however.
36
<li>The game system ( starting a match, deciding when someone won, starting new rounds ) is
37
fundamentally flawed; all changes to it have a high probability of introducing nasty new bugs.
38
All following bugs are caused by this mess. I'll give it a complete workover for 0.3.0, if I ever
40
<li>( Mixed human/AI teams do not work very well )</li>
44
SUBSECTION(Probably fixed bugs)
46
<li>Network game with holes in walls: holes disappear when they get blown into a cycle's current
47
wall as soon as it takes its next turn ( client only effect )</li>
48
<li>two human teams with only AI players on will keep playing on a dedicated server</li>
49
<li>crash when opening the score-view after the following actions:
51
client with one player connects<br>
52
client with two players connects, one of them joins the team from the other client<br>
54
<li>Inactive players get accounted as team members</li>
55
<li>the dedicated server won't go daemon(it should notice by itself that
56
it's standard io is not the console)</li>
57
<li>Strange camera behaviour; I only observed it myself when the frame rate is
58
very high (200 and up)</li>
59
<li>Invisible bikes on the Voodoo 2 under Windows (Jacob Aaron Barandes),
60
caused by broken implementation of display lists. Other Voodoo 2 systems
61
show different kind of trouble...</li>
62
<li>RADEON: no valid screen mode found. Implement desktop colour depth and ignore errors. (Nathan Parslow <bruce@linuxgamers.net>)</li>
63
<li>Seemingly random disconnections (network object IDs get assigned
64
incorrectly every once in a while)</li>
65
<li>server browser does not get the complete list from master</li>
66
<li>Server browser crashes when an unreachable server under the cursor is
68
<li>Disconnected state is set when connecting to a server, disconnecting and
69
starting an own server</li>
70
<li>Disconnected state is set when the last guest quits on an own server</li>
71
<li>Chat state does not work in server mode</li>
72
<li>network mode without dedicated server: rounds are reseted when someone connects</li>
73
<li>network mode: use special multiplayer-settings rather than special single-player settings</li>
74
<li>network mode: player changes are not transmitted immediately</li>
75
<li>explosion sounds are often not played</li>
81
SUBSECTION(Fixed bugs)
84
<li>PROGTITLE exits with a message like "Point (569.977, 269.095) does not have a face in direction (0, 2.05167) Please Send A Bug Report!"; That means the
85
internal data structures are corrupt and don't allow another wall to be drawn. Maybe I should just rebuild the structures when that happens? Hmm...</li>
86
<li>Problems when logging in on a server with a game already running (Managed to reproduce it finally)</li>
87
<li>AI players drove out through the rim wall and came back alive</li>
88
<li> with fast video cards or "Express Finish": Champion of a
89
match was declared in an additional round </li>
90
<li>when changing the screen mode in mid-game, the cycles became invisible</li>
91
<li>The textured floor did not work on all known ATI chips (from Rage to Radeon) and probably all S3 chips; (OK, I know now
92
what would have to be done. But I'm too lazy currently)</li>
93
<li>Seemingly random connection terminations; caused by packet loss.</li>
94
<li> Matches on a dedicated server started in round 2</li>
95
<li> sometimes: crashes with "... left grid"-message </li>
96
<li> the mouse cursor stays visible on some Linux systems (VooDoo 3000
98
<li>the control over the own bike is poor in network mode (about 99% perfect now)</li>
99
<li>When you play the highscore hunt on a dedicated server and someone
100
enters, you got accounted one won round on your score, and the
101
multiplayer settings were not restored.</li>
103
<li>camera hickups</li>
105
<li> ALT-Tabbing out of PROGTITLE for Windows causes BAAAD lockups.</li>
107
<li>The network mode is still not tested very well, but there were no
108
BAD crashes the last couple of hours. One problem that is hard to get
109
away: Making many fast turns confuses the client for a while;
110
driving straight again makes it catch on after a short while. Fixing
111
this would require a change in the network protocol, and I promised
112
not to do that until after version 0.1. (I mainly got it fixed now.)</li>
114
<li>player Coors are wrong in network play sometimes</li>
116
<li>does not exit cleanly on some configurations</li>
118
<li>the server exits every now and then, even with players on it (some
119
crashes, but most of the time the cpu time limit is hit)</li>
121
<li>It seems to be impossible for a second user to join a network game
122
if there are >8 AI players; yet, I couldn't reproduce this bug.</li>
124
<li>Texture files MUST be in RGBA - 32bit/pixel mode. (corrected. They
125
may now be in RGBA or RGB format.)</li>
127
<li>logging in to the server often fails with timeouts</li>
129
<li>sometimes, there are "ghost bikes".</li>
131
<li>Some generic hangups (an esp. nasty one affected even the server).</li>
133
<li>in "Fast Finish" mode, there are hangups when you lose.</li>
135
<li>Chatting during the game break killed you immediately in the next game.</li>
137
<li>It was possible do drive through walls:
139
<li>drive straight to then</li>
140
<li>turn EXACTLY on the wall</li>
141
<li>turn the other direction</li>
143
I accidently made it through the outer wall that way.
144
Haven't seen such things happen lately, so I consider it fixed.</li>
146
<li>The network mode had various problems: random crashes, players
147
getting killed just because they took a turn, walls being temporarily
150
<li>The Linux version crashes on exit. (It's a boomerang bug: I think it
151
will come back again. Caused by C++ destructors of static objects
152
called in the wrong order.) </li>
154
<li> The sky is supposed to have a foggy look (alpha effect).
155
with Win9x VooDoo or TNT hardware rendering however, there seem to exist
156
only the alpha values 0 (=fully transparent) or 1 (=opaque).
157
Linux version and Win9x software rendering are not affected.
158
What am I doing wrong? Please send me a small OpenGL program
159
that uses correct alpha blending so I can correct this.
160
(Stupid me. I explicitly ordered OpenGL to store the textures with
161
one bit alpha; Mesa ignored that.)</li>
163
<li>The timer does funny things sometimes (causing you to crash into
164
yourself by just taking an turn)</li>
166
<li>The far edges of the grid are not displayed at match start.</li>
169
SUBSECTION(Those are NOT bugs:)
172
<li>in "Freestyle" game mode, there game does not stop until you are dead.</li>
174
<li>"Z-Trick" and "Infinity" don't work on your PC</li>
176
<li>In a network game, it sometimes <strong>seems</strong> like bikes can pass through walls</li>
181
include(navbar.html.m4)
added
removed
src/doc/bugs.html.m4
