Quote from josepezdj on June 25, 2012, 3:19 pm

You should load the pointfile and follow the red line that leads you to where the leak is. Try to name your map something WITHOUT spaces in it (use "_" instead of spaces)... maybe that is the cause that hammer cannot read the .prt file.

Quote from groet999 on June 25, 2012, 3:34 pm

It doest work.
And I see this if I jump to the leak:
http://imageshack.us/photo/my-images/856/hammer2012062521232091.png
http://imageshack.us/photo/my-images/831/hammer2012062521231409i.png/
I cant do anything there.

Quote from josepezdj on June 25, 2012, 3:42 pm

You have to get to the other point of that red line, dude. That edge you show is where that line begins

When hammer tells you that a given entity leaks, it only means that through the hole you have in your map it can reach that given entity; the problem is NOT that entity though, it is a hole that you have in your map. Check out again with that in mind.

If that red line doesn't point to any hole (bear in mind that it could be a really tiny space between 2 brushes, so try to zoom in a lot, ok?), and that line goes straight on to a brush, then maybe you tied that brush to an entity (func_brush, func_door, func_button, etc.)... You'0ll have to "move that brush to the world" again because that kind of brushes cannot seal a map.

Quote from groet999 on June 25, 2012, 3:48 pm

I have checked it, but it is the same story:
http://imageshack.us/photo/my-images/266/hammer2012062521454774.png/

Quote from josepezdj on June 25, 2012, 3:58 pm

THAT you see there is a prop or something outcoming from that instance (or whatever that is) and is causing the leak. If it's an instance check inside it clicking the "Edit instance" button at the bottom of its properties window. Could you post the vmf file of at least take much wider a picture?

Quote from Skotty on June 25, 2012, 4:38 pm

"Entity trigger_once (99999.50 -99999.50 -99999.50) leaked!"

Brush entities have their origins always where their Origin coordinate is. Maybe something happened and the value of the "Origin" of a trigger_once moved out to there. It's their center and the Red line of Pointfile can start at these (so it looks like its starting in the middle of nowhere).

Quote from Nacimota on June 25, 2012, 5:59 pm

Skotty wrote:

"Entity trigger_once (99999.50 -99999.50 -99999.50) leaked!"

Brush entities have their origins always where their Origin coordinate is. Maybe something happened and the value of the "Origin" of a trigger_once moved out to there. It's their center and the Red line of Pointfile can start at these (so it looks like its starting in the middle of nowhere).

Indeed. It appears that the origin of your trigger_once got misplaced somehow. Resetting the origin (or removing the entity) should solve the problem.

Quote from josepezdj on June 25, 2012, 7:07 pm

Yeah, that could be too. Sometimes you click a func_brush because you want to move it but you pick up its origin instead without even realising you did, and you move it so far away from the brush it belongs to; then you simply go and move the brush as nothing really happened... but the fact is that its origin is really far away. This can cause more compile errors as well not just a leak.

(wouldn't it be a good idea to change the name of this topic in order to make it be related to the issue described in it?)

Quote from Lpfreaky90 on June 25, 2012, 7:22 pm

Moderator note: pleas use a slightly more informative thread title next time "Help" isn't really informative to what kind of problem you have...