quote: Wolfenstein manual
BSPC, prepare the map for single player AIs
If you are doing a single player map, you will need to build two .aas files, so that the AIs know were to run. For instance, if you map is foo.map, you will compile foo.bsp with q3map, and with bspc you will have to produce foo_b0.aas and foo_b1.aas. You can create a batch file to help the process (BSPC compiling is not integrated into GtkRadiant atm):
@echo off
setlocal
rem Enable this next line to compile maps without debug info (put in a rem to enable debug info)
rem set extraparms=-optimize
bspc -threads 1 -ext _b0 -cfg aascfg_sm.c -bsp2aas …\main\maps%1.bsp -output …\main\maps %extraparms%
copy bspc.log temp_b0.log
bspc -threads 1 -ext _b1 -cfg aascfg_lg.c -bsp2aas …\main\maps%1.bsp -output …\main\maps %extraparms%
copy bspc.log temp_b1.log
IMPORTANT Q3MAP2 NOTE: If you are using q3map2 to compile the map, add -forcesidesvisible to the bspc options.
Troubleshooting
If the editor doesn’t work correctly, make sure that your installation is not broken, i.e. you have installed newer version above an older one, or you are trying to use and editor binary with incompatible modules and tools (i.e. that came from other sources).
Carefully examine the console of the editor for any error and warning messages. Some important things are happening while the editor is starting, before the console is available, this is why it is possible to have Radiant log everything to a radiant.log file (which will be in C:\Program Files\GtkRadiant\radiant.log). You can turn logging on from the preferences menu.
If that fails, see the links page that comes with GtkRadiant setup to find forums and help. In the editor, the Help menu provides a number of useful shortcuts.