level collapsed on top of other level, why?

EDIT: deleted links..nvm

meh, the links lead to text instead of downloadable files?

You can just show us the compile log. Chances are you have some convex brushes or other odd shapes that cause vbsp to go crazy during compiles.

---

Why snark works.

right click>save target as

IE always tries to open them as text files, as that's basically what they are. dunno about other browsers.

frags, I don't know what you've done with the 2nd floor, but it's not in the vmf. some 3d editing packages can union, or weld, seperate pieces, but hammer isn't one of them.

---

i eat paint

CYA guys later.

the ramps are one brush each. the 'gap' is a transparent part of the texture, and has never been a real gap. like i said, hammer cannot weld two brushes together, either by design, or by accident.

---

i eat paint

Use a higher grid (like 32 or 64 Units) and make sure every vertex (brush corner) is on the grid. Rotating brushes usually makes the corners off so using "vertex editing" carefully might be a better idea. Look at some default VMFs that come with the SDK and you'll see how carefully the brushes are aligned to clean 16, 32, 64, 128, 256 Units sizes.

Reasons for using a strictly aligned to grid geometry:

• vbsp tries to "fill" unaligned polygon corners with additional polygons, thus creating more unnecessary geometry that causes your map to render slower (bad performance)
• Not using the grid precisely can cause compile crashes and errors, it's more difficult to avoid leaks and it can even cause geometry to collapse in a strange way causing unwanted geometry.

---

Why snark works.