Troubleshooting

Troubleshooting

The game doesn't start

• Update your graphics drivers. Q3Rally needs hardware OpenGL.
• Linux: make sure SDL2 and an OpenAL implementation are installed. On Debian/Ubuntu: sudo apt install libsdl2-2.0-0 libopenal1.
• Start with default settings: rename q3config.cfg in your data directory (see Installation → Where your files are stored).

Crash with Z_Malloc or Hunk_Alloc errors

The game ran out of its reserved memory. Raise the limits and restart:

\seta com_hunkMegs 256
\seta com_zoneMegs 64

You can also pass them on the command line:

q3rally.x86_64.exe +set com_hunkMegs 256 +set com_zoneMegs 64

I can't connect to a server / "pure server" errors

The server and your client need the same game data. Make sure you're on the same version as the server, then remove any extra .pk3 files you added to baseq3r and try again.

My old server config starts the wrong game mode

The g_gametype numbers changed in v0.7c. Old configs for team modes have to be updated. See Dedicated Server → Gametype numbers.

Weather looks thin or doesn't show up

• Check cg_atmosphericLevel. 0 turns weather particles off.
• 🧪 In the development build, weather can be dynamic: it comes and goes during a match if the server has g_dynamicWeather 1.

My ghost isn't saved

• Only laps that are good enough (a personal best, or one of the five fastest) are saved.
• Ghosts are stored per track variant. A reversed or shorter version of the same map has its own ghosts.
• Check that baseq3r/ghosts/ in your data directory is writable.

Autoball: no ball, or the match doesn't start 🧪

• The console shows AUTOBALL: this map has … red / … blue autoball_goal: the map is missing the ball or a goal. See Game Mode Entities → Autoball.
• The ball feels wrong or a warning about the Bullet backend appears: set g_scriptedObjectBullet 1.
• No bots join: the map needs an .aas file.

Still stuck?

Ask on Discord or open an issue on GitHub. Include your operating system, the game version, and the last lines of the console output.