Difference between revisions of "Bug reports"
(→Sandbox Beta 2.1 Bug List) |
|||
| Line 3: | Line 3: | ||
* Linux Binary doesn't have the proper permission. | * Linux Binary doesn't have the proper permission. | ||
SOLUTION: In /Sandbox2.1/ use the command chmod -R +x bin_unix/ | SOLUTION: In /Sandbox2.1/ use the command chmod -R +x bin_unix/ | ||
| − | SOLUTION2: IN the sandbox directory | + | 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 | ||
* Modelwarehouse and Particleshowcase both have the "mirror" or "void" effect. | * Modelwarehouse and Particleshowcase both have the "mirror" or "void" effect. | ||
* Sauerbraten name is not changed to Sandbox in all cases | * Sauerbraten name is not changed to Sandbox in all cases | ||
Revision as of 12:52, 8 March 2008
Contents
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
- Modelwarehouse and Particleshowcase both have the "mirror" or "void" effect.
- Sauerbraten name is not changed to Sandbox in all cases
- Sandbox Freezes for absolutely no reason in multiplayer
SOUTION: This is a bug with sauerbraten itself, and hasn't been fixed yet.
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 specific to us.
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.
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.
