Error opening mapname: Difference between revisions
Jump to navigation
Jump to search
m (Add other cause) |
No edit summary |
||
| Line 3: | Line 3: | ||
The compiler can't find the *.bsp file of your map or it's corrupted. Your .bsp file was probably not created in the first place due to an error during the [[vbsp]] stage of compiling. If not, check the pathname. With Hammer 4 and its auto-configuration settings, you generally do not need to worry about the copying procedures in the configurations. Another common source of this problem is spaces in your map name - rename your map file or do a save as with a different name with no spaces. | The compiler can't find the *.bsp file of your map or it's corrupted. Your .bsp file was probably not created in the first place due to an error during the [[vbsp]] stage of compiling. If not, check the pathname. With Hammer 4 and its auto-configuration settings, you generally do not need to worry about the copying procedures in the configurations. Another common source of this problem is spaces in your map name - rename your map file or do a save as with a different name with no spaces. | ||
[[Category:Compile | [[Category:Compile errors]] | ||
Revision as of 11:40, 11 August 2023
Error opening mapname.bsp
The compiler can't find the *.bsp file of your map or it's corrupted. Your .bsp file was probably not created in the first place due to an error during the vbsp stage of compiling. If not, check the pathname. With Hammer 4 and its auto-configuration settings, you generally do not need to worry about the copying procedures in the configurations. Another common source of this problem is spaces in your map name - rename your map file or do a save as with a different name with no spaces.