Another Map Compile Issue

Another Bad Pun

In the shadows, he saw four eyes lit by fire
aa
Jan 15, 2011
801
1,845
All the sudden my map stopped compiling correctly, or updating to the next bsp. It turned out to be a compile error. Interlopers just said that vbsp was failing, which didn't help me much, and I can't find anything in the map with 'check for problems' or in the compile log. But maybe I'm missing something! Here's the compile log.

Code:
** Executing...
** Command: "C:\Program Files (x86)\Steam\SteamApps\common\Team Fortress 2\bin\vbsp.exe"
** Parameters: -final -ldr -game -StaticPropPolys -TextureShadows -staticproplighting -game "C:\Program Files (x86)\Steam\SteamApps\common\Team Fortress 2\tf" "c:\program files (x86)\steam\steamapps\common\team fortress 2\content\tf\mapsrc\aaa_dauphin\ctf_dauphin_rc3"

Warning: falling back to auto detection of vproject directory.
Unable to find gameinfo.txt. Solutions:

1. Read http://www.valve-erc.com/srcsdk/faq.html#NoGameDir
2. Run vconfig to specify which game you're working on.
3. Add -game <path> on the command line where <path> is the directory that gameinfo.txt is in.

Unable to find gameinfo.txt. Solutions:

1. Read http://www.valve-erc.com/srcsdk/faq.html#NoGameDir
2. Run vconfig to specify which game you're working on.
3. Add -game <path> on the command line where <path> is the directory that gameinfo.txt is in.



** 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:\program files (x86)\steam\steamapps\common\team fortress 2\content\tf\mapsrc\aaa_dauphin\ctf_dauphin_rc3"

Valve Software - vvis.exe (Mar 30 2015)
8 threads
reading c:\program files (x86)\steam\steamapps\common\team fortress 2\content\tf\mapsrc\aaa_dauphin\ctf_dauphin_rc3.bsp
Error opening c:\program files (x86)\steam\steamapps\common\team fortress 2\content\tf\mapsrc\aaa_dauphin\ctf_dauphin_rc3.bsp

** Executing...
** Command: "C:\Program Files (x86)\Steam\SteamApps\common\Team Fortress 2\bin\vrad.exe"
** Parameters: -final -ldr -StaticPropPolys -TextureShadows -staticproplighting -game "C:\Program Files (x86)\Steam\SteamApps\common\Team Fortress 2\tf" "c:\program files (x86)\steam\steamapps\common\team fortress 2\content\tf\mapsrc\aaa_dauphin\ctf_dauphin_rc3"

Valve Software - vrad.exe SSE (Mar 30 2015)

      Valve Radiosity Simulator     
8 threads
[Reading texlights from 'lights.rad']
[37 texlights parsed from 'lights.rad']

Loading c:\program files (x86)\steam\steamapps\common\team fortress 2\content\tf\mapsrc\aaa_dauphin\ctf_dauphin_rc3.bsp
Error opening c:\program files (x86)\steam\steamapps\common\team fortress 2\content\tf\mapsrc\aaa_dauphin\ctf_dauphin_rc3.bsp

** Executing...
** Command: Copy File
** Parameters: "c:\program files (x86)\steam\steamapps\common\team fortress 2\content\tf\mapsrc\aaa_dauphin\ctf_dauphin_rc3.bsp" "C:\Program Files (x86)\Steam\SteamApps\common\Team Fortress 2\tf\maps\ctf_dauphin_rc3.bsp"

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

Vel0city

func_fish
aa
Dec 6, 2014
1,947
1,589
Well, it can't find gameinfo.txt in the standard library on your computer which is steamapps/tf. Once that file is missing everything goes south and VBSP stops. If VBSP doesn't make a BSP, VVIS and VRAD just don't work since they have no map file to work with, hence the "The command failed. Windows reported the error: "The system cannot find the file specified." " part of the compile log.
 

Pocket

Half a Lambert is better than one.
aa
Nov 14, 2009
4,694
2,579
I just got this same error. I had compiled a map with the normal parameters just to make sure it would work, and then I tried to recompile in final mode with -staticproplighting and -staticproppolys on, and it spat out that error when it tried to run VRAD. VBSP and VVIS both ran just fine. The heck?
 

JMaxchill

L5: Dapper Member
Jan 21, 2015
215
69
I've got basically the same problem - "Windows cannot find the map specified". From the logs, I think it's trying to copy the existing version of the map as a backup - "Windows cannot find the specified file". this basically means you can't make any new maps.
I tried copying a different bsp in (arena_badlands) and it didn't give the error, but when I tried to load the map it was still blands - Hammer didn't actually render the file. Halp?
 

Vel0city

func_fish
aa
Dec 6, 2014
1,947
1,589
Are you people writing to external drives? If you do, go stand in a corner, because you shouldn't. Drives over USB can lose connection for even a fraction of a second from time to time, but that tiny gap of information loss makes VRAD (or VBSP or VVIS, depends on timing) say nope.avi and stops working. Either compile to the main drive, or compile to the main drive.
 

JMaxchill

L5: Dapper Member
Jan 21, 2015
215
69
It doesn't tell me that. IMHO it's probably the displacements, but I'm losing the will to continue with this map...
 

Crash

func_nerd
aa
Mar 1, 2010
3,315
5,499
I've got basically the same problem - "Windows cannot find the map specified". From the logs, I think it's trying to copy the existing version of the map as a backup - "Windows cannot find the specified file". this basically means you can't make any new maps.
I tried copying a different bsp in (arena_badlands) and it didn't give the error, but when I tried to load the map it was still blands - Hammer didn't actually render the file. Halp?

This is most likely a different issue caused by something compile breaking. Check for problems.
 

A Boojum Snark

Toraipoddodezain Mazahabado
aa
Nov 2, 2007
4,775
7,669
Yall disappoint me. Compile logs are there to read to find the problem.

** Command: "C:\Program Files (x86)\Steam\SteamApps\common\Team Fortress 2\bin\vbsp.exe"
** Parameters: -final -ldr -game -StaticPropPolys -TextureShadows -staticproplighting -game "C:\Program Files (x86)\Steam\SteamApps\common\Team Fortress 2\tf" "c:\program files (x86)\steam\steamapps\common\team fortress 2\content\tf\mapsrc\aaa_dauphin\ctf_dauphin_rc3"

The game parameter is being sent twice, one of them without any input. That is what is causing the vproject error. Get rid of the first one, the second one is good because it has the directory following it.
 

JMaxchill

L5: Dapper Member
Jan 21, 2015
215
69
This is most likely a different issue caused by something compile breaking. Check for problems.
Almost certainly the displacements - it won't let me sew them either - but at this point I'm probably just gonna dump what I've got and start over.
 

killohurtz

Distinction in Applied Carving
aa
Feb 22, 2014
1,016
1,277
Almost certainly the displacements - it won't let me sew them either - but at this point I'm probably just gonna dump what I've got and start over.

You can still have non-sewing displacements that are valid, because that depends on their geometry. But it's still very possible that they're broken - use Alt+P in Hammer to check for them and run your compile log through http://www.interlopers.net/errors if you haven't already.