Posted by Frodo13 on Sat Feb 10th at 9:45am 2007
i am getting this problem when compiling my map, hope someone can help, thanks.
** Executing...
** Command: "c:program filesvalvesteamsteamappsthomas0705sourcesdkbinvbsp.exe"
** Parameters: -game "c:program filesvalvesteamsteamappsthomas0705counter-strike sourcecstrike" "C:Program FilesValveSteamSteamAppsthomas0705sourcesdkcs_jailed_alpha"
Valve Software - vbsp.exe (Aug 4 2006)
2 threads
materialPath: c:program filesvalvesteamsteamappsthomas0705counter-strike sourcecstrikematerials
Loading C:Program FilesValveSteamSteamAppsthomas0705sourcesdkcs_jailed_alpha.vmf
fixing up env_cubemap materials on brush sides...
ProcessBlock_Thread: 0...1...2...3...4.Brush 87502: WARNING, microbrush
..5...6...7...8...9...10 (3)
WARNING: node with unbounded volume
WARNING: node with unbounded volume
ProcessBlock_Thread: 0...1...2...3...4.Brush 87502: WARNING, microbrush
..5...6...7...8...9...10 (3)
WARNING: node with unbounded volume
WARNING: node with unbounded volume
Processing areas...done (0)
Building Faces...done (0)
Chop Details...done (0)
Find Visible Detail Sides...
Merged 200 detail faces...done (0)
Merging details...done (0)
FixTjuncs...
HashVec: point outside valid range
** Executing...
** Command: "c:program filesvalvesteamsteamappsthomas0705sourcesdkbinvvis.exe"
** Parameters: -game "c:program filesvalvesteamsteamappsthomas0705counter-strike sourcecstrike" "C:Program FilesValveSteamSteamAppsthomas0705sourcesdkcs_jailed_alpha"
Valve Software - vvis.exe (May 22 2006)
2 threads
reading c:program filesvalvesteamsteamappsthomas0705sourcesdkcs_jailed_alpha.bsp
Error opening c:program filesvalvesteamsteamappsthomas0705sourcesdkcs_jailed_alpha.bsp
** Executing...
** Command: "c:program filesvalvesteamsteamappsthomas0705sourcesdkbinvrad.exe"
** Parameters: -game "c:program filesvalvesteamsteamappsthomas0705counter-strike sourcecstrike" "C:Program FilesValveSteamSteamAppsthomas0705sourcesdkcs_jailed_alpha"
Valve Software - vrad.exe SSE (May 22 2006)
----- Radiosity Simulator ----
2 threads
[Reading texlights from 'lights.rad']
[1 texlights parsed from 'lights.rad']
Loading c:program filesvalvesteamsteamappsthomas0705sourcesdkcs_jailed_alpha.bsp
Error opening c:program filesvalvesteamsteamappsthomas0705sourcesdkcs_jailed_alpha.bsp
** Executing...
** Command: Copy File
** Parameters: "C:Program FilesValveSteamSteamAppsthomas0705sourcesdkcs_jailed_alpha.bsp" "c:program filesvalvesteamsteamappsthomas0705counter-strike sourcecstrikemapscs_jailed_alpha.bsp"
The command failed. Windows reported the error:
"The system cannot find the file specified."
Posted by fishy on Sat Feb 10th at 2:05pm 2007
i don't know how familiar you are with how the compile works, but it happens over several stages. first it takes your .vmf that you made in hammer, and it gets compiled into a raw .bsp file, with no vis data or lighting included. then the next stage of the compile takes over, adding vis data to the raw .bsp that was generated in the first stage.
that's where your 'can't find file' is appearing. your compile didn't finish the first part, so there is no raw .bsp for the 2nd stage of the compile to work with. the 3rd and 4th stages will also cry about the missing file.
so the 'can't find file' really means there was a problem with the 1st stage, not that your comp doesn't know where to look.
WARNING: node with unbounded volume
ProcessBlock_Thread: 0...1...2...3...4.Brush 87502: WARNING, microbrush
..5...6...7...8...9...10 (3)
WARNING: node with unbounded volume
WARNING: node with unbounded volume
node with unbounded volume seems to be connected with poorly positioned brushwork; vertices off grid, microbrushes, etc.
micro brushes are often caused by carving with anything other than one simple block from another. also by using the clip tool without checking that the resulting endpoints of all the newly clipped brushes are on the grid.
Posted by Stadric on Sat Feb 10th at 10:47pm 2007
HashVec: point outside valid range
This error will cause your map to fail compiling completely
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:
Finding the unfindable
Invalid solids
But you should also fix those micro brushes, and avoid all carving whatsoever.
As I Lay Dying
Snarkpit v6.1.0 created this page in 0.0098 seconds.


