Bug reports

List of BUGS which aren't BUGS

• Cannot load core textures.

SOLUTION: The reason there was a (clickheretostart).bat and a sauerbraten_unix script available, was so that people would click them instead of trying to execute the binaries in their own directories. so try one of those scripts instead.

SOLUTION2: Move the executable up one directory and try it there.

• LINUX ONLY - Missing libSDL_image-1.2.so.0

SOLUTION: Please check here -> [1]

Sandbox Beta 2.1 Bug List

• Linux Binary doesn't have the proper permission.

SOLUTION: In /Sandbox2.1/ use the command chmod -R +x bin_unix/

SOLUTION2: IN the sandbox directory there should be a sandbox_unix script, if you use chmod +x sandbox_unix on it, and execute it, it'll take care of permissions and launching.

ALTERNATIVE: You can also skip the problem. In /Sandbox2.1/ use the command ./bin_unix/native_client -t, note this executes the binary in windowed mode, and doesn't change permissions at all.

• Modelwarehouse and Particleshowcase both have the "mirror" or "void" effect.
• Sauerbraten name is not changed to Sandbox in all cases
  • This appears to only be true for some configuration files Hriato imported.
• Sandbox Freezes for absolutely no reason in multiplayer

NOTE: This is a bug with sauerbraten itself, and hasn't been fixed yet.

Sandbox Beta 2.1 Lite Bug List

• The same bugs as in "normal" version

• unix launcher - bad links to binary files (or files in bad place)

• in menu Load - links to non existing maps (remove the links or put there maps back)

Bug Reports

If you encounter a bug, we would honestly love to know about it. well, maybe not 'love' but we really would like them. All software has bugs, even the engine we use. not to mention we create many ourselves. the best way to do it is to send in a bug report. When compiling the report, we need you to be descriptive of it.

• We need to be able to recreate it
• We need to know what you did
• We need to know when you were doing it (like after pulling up some cubes, etc)
• we need to know if it was multiplayer

If you have a backtrace, the list pretty much just goes down to 'what did you do' As we're slightly incompetent programmers, we will be sending the bug report to the sauerbraten developers if we establish that it's not a problem we're to blame for it's cause.

Sending backtraces

Linux

to do this on linux, you need to compile your own client, first open your Makefile in /src, and add -ggdb3 into the CXXOPTS line. Secondly, scroll done to the "install" build option, remove any lines with the word 'strip' in it. You're ready to compile, so compile the oversized binary so we can continue (make clean && make install)

Next up, run gdb in your console (in the main directory) and type in

file bin_unix/native_client

Next up, run the executable, so just type run -r -t, you'll want it windowed. Now just reproduce the bug, once the window freezes, alt tab to the console and type 'bt' now, whatever this outputs, copy and paste it into a text file and send it in to us.