Common problems FAQ
Some buttons don't work!
There may be a problem with the keybindings sometimes. To reset them to the defaults, do this in the client program: In the main menu (press Escape), options...->general->Restore Defaults
Why is my ping high?
If your ping is very high (300+) then gameplay may be poor. Some things that can cause that are:
- Running P2P software like BitTorrent
- Downloading large files at high speed
So, if you are doing either of those while running Syntensity, that may be the problem.
- I get weird errors from a map - syntax errors or something else that looks like a script is broken. But the map works for everybody else...
It might be the case that the downloaded scripts got messed up somehow. This is not always detected and fixed. To force the client to re-download those scripts (with the working versions), you can simply delete them. Usually that means removing the ~/.intensityengine_client/packages/library/ folder (on Windows, replace ~ with something like C:\Users\USERNAME, etc.). (If the scripts are in another directory, then delete that directory.) Note that deleting individual script files will not work - assets are tracked by entire folders.
If you run into problems of any sort, the logged output may be useful. It appears in the console on Linux and in a file called out_client
on Windows (which will be in the directory in which you run Syntensity).
You can also raise the amount of information that is logged. By default the logging level is WARNING, which just notifies of major issues. Changing the level to DEBUG will give a lot more information, and changing it to INFO will give much more (possibly creating a very large log file). The logging level is set in settings.cfg in your Syntensity home directory, which is intensityengine
_client or .intensityengine_client
under your operating system user's home directory - Users
on Vista, or under Documents and Settings
on XP, or ~ on Linux, etc.
To check that the logging level is set correctly, look at the log output. It should contain a line line this: <<< Setting logging level to DEBUG >>>
It is recommended to try with DEBUG, then if that isn't informative enough, to try with INFO, which as mentioned above will output a lot
: In DEBUG, and especially in INFO, performance will be slow (due to many additional checks done all the time). Switch back to WARNING when you don't need anything else.NOTE 2
: In INFO, you will see some particles where the mouse points. That is to debug the mouse movement, and also to remind you that you are in INFO.
When filing bug reports
, please try to:
- Provide the output when running under DEBUG.
- Provide backtraces (that is, run the program in the debugger, and get a stack trace from the crash), preferably when compiled without optimizations (without -O1 or /O2 in src/SConstruct).
- If you are reporting a mapping bug, please provide a screenshot so we can easily understand what you mean.