I am having problems and it may be because of files saving improperly (solved)

[Dapper_Denizen]

So ive been having massive problems with compiling maps as they are taking 2+ hours to get out of the vbsp stage and looking at the files that do compile versus the ones that dont reveals that the files that dont are saved in .rmf format and whats more i cant save in vmf format anymore, its not on the drop down menu when saving and coming through the options menu reveals nothing. has anyone had this problem and or am i being stupid and there is an easy solution

 

[worMatty]

Hi, Dapper.

I am going to break your post up and deal with each thing. Apologies if I say something you already know.

So ive been having massive problems with compiling maps as they are taking 2+ hours to get out of the vbsp stage

It may not actually be VBSP that's causing the compile to take a long time. VBSP shouldn't take more than a few seconds, really. VVIS can take a while since it needs to calculate the visibility between every 'portal' in your map (a side of a visleaf). if you have a map that's quite large and open, then much of it may be visible to itself so it would take a long time to calculate. It's why mappers build their maps consisting of great walled-off sections, typically using skybox brushes. If you feel this applies to you, hunt down a guide on visibility optimisation. There are a few.

If you compile in Hammer, the compile log will seem to freeze, because Windows thinks it has hung. If you use a third-party compliation application such as CompilePal, you will be able to read the log in real-time.

and looking at the files that do compile versus the ones that dont reveals that the files that dont are saved in .rmf format and whats more i cant save in vmf format anymore, its not on the drop down menu when saving and coming through the options menu reveals nothing. has anyone had this problem and or am i being stupid and there is an easy solution

I've never heard of this problem. If you manage to eliminate those dodgy compiles you will probably sort out this issue, but your original VMF shouldn't be affected like that. If you like, upload your VMF somewhere and give us a link, and we will take a look and point out problems.

 

[Dapper_Denizen]

Hey worMatty thanks for the reply,
problem with the vmf of the map is the only one i have is severely outdated (cause i didnt realise the file extension switch) and it also now throws a line 1: unexpected symbol '{' error (which from what i read online means the files scrumbuggered.) all i have are rmf files :/

and im pretty sure its hung up in the vbsp stage cause 1) the vbsp.exe is present well after an hour (unless this is supposed to happen then disregard) and i cannot find any of the other exes that should run with the compilation of the map (vvis and the such)
2) when i do forcibly stop the process it seems not to have even done the bsp work

Spoiler: log of compile here

**
Executing...
** Command: "D:\SteamLibrary\SteamApps\common\Team Fortress 2\bin\vbsp.exe"
** Parameters: -game "D:\SteamLibrary\SteamApps\common\Team Fortress 2\tf" "D:\SteamLibrary\SteamApps\common\Team Fortress 2\sourcesdk_content\tf\mapsrc\koth_shellshock2.rmf"

Valve Software - vbsp.exe (Jun 27 2016)
12 threads
materialPath: D:\SteamLibrary\SteamApps\common\Team Fortress 2\tf\materials
Loading D:\SteamLibrary\SteamApps\common\Team Fortress 2\sourcesdk_content\tf\mapsrc\koth_shellshock2.rmf

** Executing...
** Command: "D:\SteamLibrary\SteamApps\common\Team Fortress 2\bin\vvis.exe"
** Parameters: -game "D:\SteamLibrary\SteamApps\common\Team Fortress 2\tf" -fast "D:\SteamLibrary\SteamApps\common\Team Fortress 2\sourcesdk_content\tf\mapsrc\koth_shellshock2"

Valve Software - vvis.exe (Jun 27 2016)
fastvis = true
12 threads
reading d:\steamlibrary\steamapps\common\team fortress 2\sourcesdk_content\tf\mapsrc\koth_shellshock2.bsp
Error opening d:\steamlibrary\steamapps\common\team fortress 2\sourcesdk_content\tf\mapsrc\koth_shellshock2.bsp

** Executing...
** Command: "D:\SteamLibrary\SteamApps\common\Team Fortress 2\bin\vrad.exe"
** Parameters: -game "D:\SteamLibrary\SteamApps\common\Team Fortress 2\tf" -noextra "D:\SteamLibrary\SteamApps\common\Team Fortress 2\sourcesdk_content\tf\mapsrc\koth_shellshock2"

Valve Software - vrad.exe SSE (Jun 27 2016)

Valve Radiosity Simulator
12 threads
[Reading texlights from 'lights.rad']
unknown light specifier type - lights

[56 texlights parsed from 'lights.rad']

Loading d:\steamlibrary\steamapps\common\team fortress 2\sourcesdk_content\tf\mapsrc\koth_shellshock2.bsp
Error opening d:\steamlibrary\steamapps\common\team fortress 2\sourcesdk_content\tf\mapsrc\koth_shellshock2.bsp

** Executing...
** Command: Copy File
** Parameters: "D:\SteamLibrary\SteamApps\common\Team Fortress 2\sourcesdk_content\tf\mapsrc\koth_shellshock2.bsp" "D:\SteamLibrary\SteamApps\common\Team Fortress 2\tf\maps\koth_shellshock2.bsp"

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

and finally it seems even fresh maps thats just a box have the same problem...

 

[Vel0city]

Where are you loading Hammer from? tf/bin? Because that's the one you should use, not the one shipped in the Source SDK.

VBSP tries to load your mapname.rmf, sees it's an incompatible file and then proceeds not to make the necessary bsp file for VVIS and VRAD to use, and then crash and give you that error.

 

[Dapper_Denizen]

Where are you loading Hammer from? tf/bin? Because that's the one you should use, not the one shipped in the Source SDK.

im using the file located in steamApps/common/Team Fortress 2/ bin (which is what im assuming your talking about)

 

[Vel0city]

im using the file located in steamApps/common/Team Fortress 2/ bin (which is what im assuming your talking about)

Well, in that case, it could be that you're missing game files, or something is corrupt in there. You could try validating TF2's files.
To do this, close all applications using TF2 content (Hammer, CompilePal, GCFScape, etc), then go to Steam->right-click Team Fortress 2 in the game library on the left->Properties->Local Files->Verify integrity of game cache. This will replace any missing or corrupt files.

If that doesn't help, you should post a screenshot of how your Hammer configuration is set up (it's under tools/options in Hammer, the first window that pops up) so we can see what your Hammer is doing.

 

[worMatty]

In Hammer's options, on the Game Configurations page, make sure Map Type is set to Half-Life 2 and not Half-Life / TFC.

Have a look in your VMF's directory for a .vmx file. This is a backup of your VMF, made when you last saved it. Also check out C:\HammerAutosave for historic automatic backups.

 

[Dapper_Denizen]

In Hammer's options, on the Game Configurations page, make sure Map Type is set to Half-Life 2 and not Half-Life / TFC.

Have a look in your VMF's directory for a .vmx file. This is a backup of your VMF, made when you last saved it. Also check out C:\HammerAutosave for historic automatic backups.

it worked I LOVE YOU MAN