Very strange bug

[ARC8DE]

Whenever I compile my map, the BSP does not update. I was able to fix this by deleting the BSP and compiling again. However, Hammer now throws me this error. Hammer seems to be trying to run the BSP without compiling anything. The total time from clicking compile to the compile process ending is around 6 seconds, very short. Any fixes?

Compile log:


** Executing...
** Command: "C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\bin\vbsp.exe"
** Parameters: -game "C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\tf" "c:\hammerautosave\mvm_daybreak_v1
"

Valve Software - vbsp.exe (May 21 2020)
12 threads
MSG_FILEWRITE - Filesystem was asked to write to 'c:\hammerautosave\mvm_daybreak_v1

.log', but we don't own that location. Allowing.
materialPath: C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\tf\materials
Brush 0: File c:\hammerautosave\mvm_daybreak_v1

.vmm, line 1: Invalid argument
Side 0
Texture:


** Executing...
** Command: "C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\bin\vvis.exe"
** Parameters: -game "C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\tf" "c:\hammerautosave\mvm_daybreak_v1"

Valve Software - vvis.exe (May 21 2020)
MSG_FILEWRITE - Filesystem was asked to write to 'c:\hammerautosave\mvm_daybreak_v1.log', but we don't own that location. Allowing.
12 threads
reading c:\hammerautosave\mvm_daybreak_v1.bsp
Error opening c:\hammerautosave\mvm_daybreak_v1.bsp

** Executing...
** Command: "C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\bin\vrad.exe"
** Parameters: -both -final -StaticPropLighting -StaticPropPolys -textureshadows -game "C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\tf" "c:\hammerautosave\mvm_daybreak_v1"

Valve Software - vrad.exe SSE (May 21 2020)

Valve Radiosity Simulator
12 threads
MSG_FILEWRITE - Filesystem was asked to write to 'c:\hammerautosave\mvm_daybreak_v1.log', but we don't own that location. Allowing.
[Reading texlights from 'lights.rad']
unknown light specifier type - lights

[56 texlights parsed from 'lights.rad']

Loading c:\hammerautosave\mvm_daybreak_v1.bsp
Error opening c:\hammerautosave\mvm_daybreak_v1.bsp

** Executing...
** Command: Copy File
** Parameters: "c:\hammerautosave\mvm_daybreak_v1.bsp" "C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\tf\maps\mvm_daybreak_v1.bsp"

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

 

[Da Spud Lord]

At the end of VBSP, which is the part of your compile process that creates the BSP:

Brush 0: File c:\hammerautosave\mvm_daybreak_v1

.vmm, line 1: Invalid argument
Side 0
Texture:

You have converted your map into a manifest (.vmm). Manifests are an unfinished feature, and VBSP does not know how to compile them. If you intentionally converted your map into a vmm, see this guide for how to compile it.

 

[ARC8DE]

At the end of VBSP, which is the part of your compile process that creates the BSP:

You have converted your map into a manifest (.vmm). Manifests are an unfinished feature, and VBSP does not know how to compile them. If you intentionally converted your map into a vmm, see this guide for how to compile it.

I've had people tell me this before and I've never understood what it meant. To clarify, I'm trying to compile the VMF, not the VMM. Should I just delete the VMM file and then compile?

 

[Da Spud Lord]

You say you're trying to compile the vmf, but obviously VBSP thinks you're trying to compile the vmm.

I wouldn't delete the vmm outright in case you come to regret this decision, but moving it to a different folder where VBSP can't find it might fix your issue.

 

[ARC8DE]

You say you're trying to compile the vmf, but obviously VBSP thinks you're trying to compile the vmm.

I wouldn't delete the vmm outright in case you come to regret this decision, but moving it to a different folder where VBSP can't find it might fix your issue.

I ended up just deleting the VMM and that fixed the issue. Thanks.