Help: hammer and .vmf problem

I can still load .vmf files, no problem with that. But i can't save them anymore. If I go to 'save as' i can only choose between .rmf and .map.
When i just use 'save' (or ctrl-s) instead of 'save as', it seems to save everything, and doesn't give an error. But in fact it is saved totally wrong (not the .vmf layout), so when i try to load the file it will give an error for every problem in the file (mostly a '{' or a '}' that doesn't need to be there).

I've already lost about 2 hours of work because i didn't know i was actually saving it incorrectly. Also the first backup was overwritten after 1,5 hour, so i can't use that file as well. Luckely i have a second backup file on my external hd or about 30 hours of work would've been wasted. What went wrong with hammer? How can i save .vmf files again?

 

Create a new map, make sure it's a vmf, then copy all the stuff you made into it and try to save it again.

 

When i make a new map and want to save it, i still can only choose between .rmf and .map, not .vmf.

 

So the menu option to save to VMF is gone completely? That is strange. I'd ask on interlopers or somewhere with a larger community, as this seems to be a general hammer problem.

 

my best bet is that hammer is screwed up and you'd do best if you reinstalled the SDK

 

In your hammer configuration, you probably set the map type to Half-Life/TFC. Change it to Source or whatever it's supposed to be.

 

Unfortunately map type is still HL2.

I tried saving it as emp_volcano.vmf, without selecting .map or.rmf, but it saved the file as emp_volcano.vmf.map

If i open a .vmf file (which works) and save it (ctrl s) the file looks like this:

{
"classname" "worldspawn"
"skyname" "sky_day01_01"
"maxpropscreenwidth" "-1"
"detailvbsp" "detail.vbsp"
"detailmaterial" "detail/detailsprites"
"mapversion" "360"
{
( -10240 -3072 320 ) ( -8192 -7168 320 ) ( -12288 -8192 320 ) COMMON/TOOLS/TOOLSNODRAW [ -1 0 0 0 ] [ 0 1 0 0 ] 0 0.25 0.25
( -8192 -7168 64 ) ( -10240 -3072 64 ) ( -12288 -4096 64 ) COMMON/TOOLS/TOOLSNODRAW [ -1 0 0 0 ] [ 0 1 0 0 ] 0 0.25 0.25
( -8192 -7168 64 ) ( -8192 -7168 320 ) ( -10240 -3072 320 ) COMMON/TOOLS/TOOLSNODRAW [ 0 -1 0 0 ] [ 0 0 -1 0 ] 0 0.25 0.25
( -12288 -8192 320 ) ( -12288 -8192 64 ) ( -12288 -4096 64 ) COMMON/TOOLS/TOOLSNODRAW [ 0 -1 0 0 ] [ 0 0 -1 0 ] 0 0.25 0.25
( -12288 -8192 64 ) ( -12288 -8192 320 ) ( -8192 -7168 320 ) COMMON/TOOLS/TOOLSNODRAW [ -1 0 0 0 ] [ 0 0 -1 0 ] 0 0.25 0.25
( -12288 -4096 320 ) ( -12288 -4096 64 ) ( -10240 -3072 64 ) COMMON/TOOLS/TOOLSNODRAW [ -1 0 0 0 ] [ 0 0 -1 0 ] 0 0.25 0.25
}
...

while the backup file looks like:
versioninfo
{
"editorversion" "400"
"editorbuild" "3576"
"mapversion" "487"
"formatversion" "100"
"prefab" "0"
}
visgroups
{
visgroup
{
"name" "skybox"
"visgroupid" "4"
...

Very easy to see that it doesn't oversave it as .vmf

And i've found a lot of problems with people not being able to open .vmf files, but almost never someone who can't save it. I'll keep searching though!
reinstall will have to wait, since i can't download that much (almost at my download limit) right now.

 

Jeeej, it works again.

I didn't change anything, so if anyone else has the problem i can't give you a solution. It just works again.

 

Weird, HDR started working again for Warfle today as well. I smell a sneaky update from VALVe.

 

With valve, who knows ...
I'm just glad it's fixed ;-)