I want to collect the various small bugs that we know to exist in the various release candidates. Please: only developers should post to this thread, user bug reports should go to the release process thread or the general forum, whatever you think is best.
rc1:
- tunneling through the last wall of a cycle was possible at its end
- camera switching was broken on AMD64
rc2 and earlier:
- Rubber code was not the same for everyone, high FPS players still had an advantage
- Sensors sent out of the rim wall gave back wrong distance measurements, possibly confusing the AI and rubber
- CONSOLE_MESSAGE did not add a newline at the end
- CONSOLE_DECORATE_IP had no effect
- the rc.d start/stop scripts worked only with the --disable-etc option to configure and not with the default settings in rc.config
- german menu title reads "Armagetron Advanced Advanced"
- version.h reads "0.2.7.0" in the source tarball, it gets replaced on build with the correct version.
rc3 and earlier:
- Welcome message does not fit on screen
- Documentation says it was not updated to 0.2.7.0 ( not really a bug )
Known Bugs in 0.2.7.1
further bugs of rc3 and earler:
- Time measurements get inaccurate after a month of uptime
- Ghosting is not fixed as claimend: when you do a 180, others don't see your wall every time ( I thought it was YOU not seeing your wall )
- The stab bug, see
http://guru3.sytes.net/viewtopic.php?t=1637
- The server still may ignore user input if you give three commands at once
All were there in earlier versions, too. The stab bug can be prevented by either activating the topology police or a positive cycle_delay with sane values for rubber. Positive cycle_rubber_mindistance settings help, too.
All known bugs that snuck into the 0.2.7.1 release can be reviewed here:
http://sourceforge.net/tracker/?group_i ... tid=657948
when you set the "Status" to "any" and "Group" to "v0.2.7.1" and hit the "Browse" button. ( Does anybody know how you can make this process easier? A single link, for example? Or a wrapper page filling out the form data? ) The list will be updated when more bugs are found and will only get obsoleted on the next release.
- Time measurements get inaccurate after a month of uptime
- Ghosting is not fixed as claimend: when you do a 180, others don't see your wall every time ( I thought it was YOU not seeing your wall )
- The stab bug, see
http://guru3.sytes.net/viewtopic.php?t=1637
- The server still may ignore user input if you give three commands at once
All were there in earlier versions, too. The stab bug can be prevented by either activating the topology police or a positive cycle_delay with sane values for rubber. Positive cycle_rubber_mindistance settings help, too.
All known bugs that snuck into the 0.2.7.1 release can be reviewed here:
http://sourceforge.net/tracker/?group_i ... tid=657948
when you set the "Status" to "any" and "Group" to "v0.2.7.1" and hit the "Browse" button. ( Does anybody know how you can make this process easier? A single link, for example? Or a wrapper page filling out the form data? ) The list will be updated when more bugs are found and will only get obsoleted on the next release.