Argh, corrupt .vmf

Okay, upon experimenting with the original file a bit more, turns out its a perfectly valid .map file except for two missing '{' braces:

Change the top of the file to:

Quote

{

"classname" "worldspawn"

"skyname" "sky_day01_01"

"maxpropscreenwidth" "-1"

"detailvbsp" "detail.vbsp"

"detailmaterial" "detail/detailsprites"

"mapversion" "360"

"wad" "\documents and settings\oli\desktop\nw\nw.wad;\steam\steamapps\[email protected]\half-life\nsp\ns.wad"

{

( -288 -304 128 ) ( -288 -272 128 ) ( -240 -272 128 ) PK01/PK01_PANEL01A [ 1 0 0 0 ] [ 0 -1 0 -64 ] 0 0.25 0.25

...

Display More

... and then rename to .map. However I've still only loaded it in Hammer 3.5 and not Source (it crashes if you try loading directly into 4.0).

My internet's being screwy at the moment so I can't access the Valve wiki or anything to see how to convert brushwork from Hammer 3.5 to 4.0. But I'm sure you can give that a shot now

You can save it as a .rmf file, then load it up with hammer 4.0

Ah of course, duh. Well there you go then. vmf -> map -> rmf -> vmf again.

What an epic adventure..

hehe, should be some sort of comic made of this

The adventures of hammer screwing things up

This thread just delivered.

Moral: Always listen to Hessi

? c&p-ing into the vmf would have achieved nothing in this case.

Still be interested to know how this happened, dux did you accidently load the file into hammer 3.5?

If not it suggests hammer 4.0 uses the old .map format in some way and did very weird stuff when it crashed out?

source sux

thanks for that neccesary and helpfull comment in a currently fully alive thread