Compiling Issues Created 18 years ago2005-12-07 02:19:02 UTC by n00b #2

Well i was working on a map and finally got it to where i thought it coudl be "testable" but as soon as i compile it all hell breaks loose. So here is the compiling process for anyone who can help me out because i really have no friggin' clue

** Executing...
** Command: Change Directory
** Parameters: "C:Program FilesValveSteamSteamAppsddunkj1counter-strike"

** Executing...
** Command: C:PROGRA~1VALVEH~1toolsqcsg.exe
** Parameters: "c:program filesvalve hammer editormapscs_canyon"

qcsg.exe v2.8 (Jan 31 2000)
-- qcsg --
entering c:program filesvalve hammer editormapscs_canyon.map

********** ERROR **********
Token too large on line 5

** Executing...
** Command: C:PROGRA~1VALVEH~1toolsqbsp2.exe
** Parameters: "c:program filesvalve hammer editormapscs_canyon"

qbsp2.exe v2.2 (Dec 28 1998)
-- qbsp2 --

********** ERROR **********
Can't open c:program filesvalve hammer editormapscs_canyon.p0

** Executing...
** Command: C:PROGRA~1VALVEH~1toolsvis.exe
** Parameters: "c:program filesvalve hammer editormapscs_canyon"

vis.exe v1.3 (Dec 30 1998)
-- vis --
1 thread(s)

********** ERROR **********
Error opening c:program filesvalve hammer editormapscs_canyon.bsp: No such file or directory

** Executing...
** Command: C:PROGRA~1VALVEH~1toolsqrad.exe
** Parameters: "c:program filesvalve hammer editormapscs_canyon"

qrad.exe v 1.5 (Apr 6 2000)
--- Radiosity --
1 threads
[Reading texlights from 'C:PROGRA~1VALVEH~1toolslights.rad']
[1 texlights parsed from 'C:PROGRA~1VALVEH~1toolslights.rad']

********** ERROR **********
Error opening c:program filesvalve hammer editormapscs_canyon.bsp: No such file or directory

** Executing...
** Command: Copy File
** Parameters: "c:program filesvalve hammer editormapscs_canyon.bsp" "C:Program FilesValveSteamSteamAppsddunkj1counter-strikecstrikemapscs_canyon.bsp"

The command failed. Windows reported the error:
"The system cannot find the file specified."

"Token too large".
This can refer to several different errors:

1. The "too many wads" as mentioned above. 8 wads in WC/Hammer is a good limit, more may cause this error among others. If you are using more than 8 wads you can use Wally to combine the extra wads into one custom wad.
2. Too long a path/name for the map or compiling tools. Only a limited amount of memory is set aside for the path/names. Solution is to move the compiling tools or map into a shallow folder.
3. Having a space in a path/name. Examples: frequently Program Files is part of the path name. Compiling tools do not like the space between "program" and "files". Solutions are to either use the MSDOS pathname, or to move the offending files from under the spaced folder, or put quotes " " around the whole path name in WC/Hammer so that windows uses it right. If your map has the space in its name (eg. Bob map), remove the space and change it to (Bobmap).

For future reference.

You should get Zoner's tools for compiling, anyway. The Quake tools provided with Hammer are a joke. See the Links page.