Common Support Issues

From BZFlagWiki
Revision as of 13:18, 7 July 2009 by Mr Burns (Talk | contribs) (Kicked for not using UDP)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This is a list of common problems in the game and their resolutions.

Global Login Not Identifying[edit]

If you get the following error upon entering or finding servers...

ERROR: Did not get token:
NOTOK: Invalid callsign or password

It may be caused either by the global login system being down (which you can check by going to the BZBB) or your ISP putting a caching proxy on port 80. This means that when your client goes to get a token from global login, your ISP returns an old cached token which will not work. If there is a proxy, then the following steps will allow you to bypass it.

#set list http://my.bzflag.org/db
  • Change the line to read:
set list http://my.bzflag.org:81/db
  • Save the file and restart BZFlag

If you continue to get the error above then either global login is down or there is a more serious problem (in which case you should get support).

Kicked for not using UDP[edit]

BZFlag uses UDP to communicate between the client (you playing the game) and the server (the machine hosting the map). If you are getting kicked from servers for not using UDP, it could be caused by your anti-virus, firewall, router, modem, or ISP.

The easiest thing to try is to disable your firewall and/or antivirus for a few minutes and see if you can play. If you still have issues and you use a router, try connecting your computer directly to your modem. If this works then the problem is probably caused by your router. Check to see if there is a newer firmware for your router. Also check to see whether some setting in your router's configuration might need to be changed.

There was recently an issue found with the Windows anti-virus program Nod32. It identifies BZFlag as a browser, causing it to block UDP communication. To fix this, right click on Nod32 in the system tray, go to Advanced Setup. From there, go to Web access protection > HTTP, HTTPS > Web browsers, and uncheck BZFlag.

Slow Performance[edit]

The performance of the BZFlag client is very dependent on the performance of the system's video card. Slow performance is often a problem when the host OS does not have the proper video card drivers to provide the needed acceleration for the 3D drawing the game does.

It is always a good idea to get the latest video drivers from the chipset manufacturer for your card. This is almost always either nVidia or ATI.

I can't kill anyone![edit]

If your shots seem to go right through other tanks without exploding them, you are probably experiencing lag. Tip: shoot slightly ahead of where other tanks appear to be.

Starting A Server[edit]

Refer to Creating A Server for help on starting your own server.

Router Setup[edit]

If you are setting up a server, you may need to unblock/forward ports on your router. This is done through the router's settings. You pick a range of ports to forward to a local IP Address (IE: Forward ports 5154-5200 to local address 192.168.1.101).

An excellent resource to assist you in doing this is available here: http://portforward.com/


Here is an example of port forwarding on one router

Port Forwarding

Crashes[edit]

If your client crashes on startup or some key mappings don't work you might try removing your configuration file and restarting BZFlag. You will have to set things like video mode and username/password again after removing it.

If you are running Linux and get segmentation fault errors when trying to connect to a server, update libcurl3 to 7.15.5 or greater.