Code: ** Executing... ** Command: "f:\program files\steam\steamapps\bbbf\sourcesdk\bin\ep1\bin\vbsp.exe" ** Parameters: -game "f:\program files\steam\SteamApps\SourceMods\Empires" "F:\Program Files\Steam\steamapps\SourceMods\Empires\mapsrc\emp_bridge2bridge" Valve Software - vbsp.exe (Dec 11 2006) 1 threads materialPath: f:\program files\steam\SteamApps\SourceMods\Empires\materials Loading F:\Program Files\Steam\steamapps\SourceMods\Empires\mapsrc\emp_bridge2bridge.vmf fixing up env_cubemap materials on brush sides... ProcessBlock_Thread: 0...1...2...3...4...5...6...7...8...9...10 (1) ProcessBlock_Thread: 0...1...2...3...4...5...6...7...8...9...10 (1) Processing areas...done (0) Building Faces...done (2) FixTjuncs... PruneNodes... WriteBSP... HashVec: point outside valid range ** Executing... ** Command: Copy File ** Parameters: "F:\Program Files\Steam\steamapps\SourceMods\Empires\mapsrc\emp_bridge2bridge.bsp" "f:\program files\steam\SteamApps\SourceMods\Empires\maps\emp_bridge2bridge.bsp" The command failed. Windows reported the error: "The system cannot find the file specified." Compiling with VVIS off and VRAD off for fullbright basic overview testing. The map has a shitload of displacements but not much else. What have I done wrong.
http://www.interlopers.net/errors/ (scroll down, select the errors and the explanations will be shown at the bottom of the page) The command failed. Windows reported the error: The system cannot find the file specified. Description: At the end of the compiling process the BSP file is copied from the directory your vmf file is in to the game/maps directory so it can be played. This error means it couldn't find the BSP to copy it.(the message Windows returns may vary on it's language) The cause is usually some fatal error in vbsp.exe (the program that generates the bare bsp-file) so check for other errors in your log. The other cause is some invalid setup of directories, or bad mapnames, too long pathnames etc. In which case you should also see the effects further upwards in the log (something like the other programs not being able to load your map). For mapnames, remember to avoid any strange characters, like brackets, dots, commas and spaces. try to build your mapname out of characters ( a-z ), numbers ( 0-9 ) and the underscore ( _ ) only. The exact cause is usally findable in the logfile. Remember this error is not a cause of your map to not compile, it is merely a sign that your map didn't compile. Solution: Check your logfile for errors, check your directory setup or rename your map. ====================================================== HashVec: point outside valid range Description: Your map is too big (you have brush(es) too near to the edge of the grid) or you have invalid brushes. Solution: If the problem-checker in Hammer (alt+p) doesn't find any offending brush(es), and you can't see brushes near the edge of the grid, you should use the cordon tools or visgroups to find them. See also: Reference: Finding the unfindable Reference: Invalid solids This error will cause your map to fail compiling completely
If you can't spot the offending brush, your best bet is to select everything that is on-grid and copy it over to a fresh vmf.
