[ANOTHER] Problem With My Map
Although the log says the Incinerator leaked, that doesn't mean that the Incinerator itels is outside of the map. It just means that somewhere in the map is a leak that "reaches" the Incinerator. if you encase the Incinerator completely with brushes, you'll most likely just get the message that now another entity leaks.
Go to "Map" and then "load pointfile", like BEARD said. When Hammer asks "Create default one", say yes. Now find a red line in the 3D view and follow it - it should run through the real leak you are looking for.
I meant to say I put a box around the map.
Anyway, I loaded the pointfile before I posted this and there was no red line anywhere, but it still said it leaked. I'm loading the map now, I'm going to delete the incinerator and try to compile to make sure thats the problem.
k, not the incinerator. Something else, but I have no clue what (the pointfile doesn't show me a red line).
Does tools/toolsblack seal the map, or is it like those vgui textures?
Found it, somehow I misplaced a modelless prop_dynamic and somehow got it way outside the map without noticing 
I've had that happen before. It's annoying.
My Work
[spoiler]Maps:
Revenge of the Angry Turrets
Capture the Cube [Co-op]
Capture the Cube 2 [Co-op]
TPWEGTH Sample Map
Aperture Aquatic Testing Center
Aperture Aquatic Testing Center 2
Aperture Time Testing Center
ML's Halloween Trick - 1000 downloads!
ML's Halloween Treat
ML's Combination - 1000 downloads!
ML's Jailbreak Labyrinth
ML's Tricky Teamwork [Co-op]
WIP:
"Capture the Cube 3"
Workshop Maps Link: http://steamcommunity.com/profiles/76561198008890579/myworkshopfiles/[/spoiler]
Toolsblack seals the map. For future reference, you might want to use cordon(s) to compile a small part(s) of the map which works. Then expand the cordon further and further out, until suddenly it doesn't compile: this tells you where the source of the problem is. Edit: as pointed out, I wasn't thinking properly and this won't work for detecting leaks. It's still worth remembering for non-leaky stuff - I'm sure you'll find a use for it.
Other than that, I seem to remember that the compile log will tell you which entity causes the leak, reporting its origin's coordinates. There's some option in hammer (view menu) to move the camera to those coordinates.
Co-operative: Lightspeed Upstairs Downstairs
It seems to me (and I honestly mean no disrespect by this) that you're getting yourself into some sloppy mapping habits. If one thing my effort to learn hammer has taught me it's taught me that if you get a problem you should work fastidiously to fix it as problems just compound themselves if you don't fix them and you'll end up with a poorly performing map.
Band aid solutions are called so for a reason. They don't fix the actual problem they just cover it up. Don't resort to using band aid solutions ion your maps unless you absolutely have to.
Other than that, I seem to remember that the compile log will tell you which entity causes the leak, reporting its origin's coordinates. There's some option in hammer (view menu) to move the camera to those coordinates.
But if the cordon surrounds the area, wouldn't it block the leak you're trying to find?
Snap
i dont no what a corodon is but i herd it not really alot but a little bit. And really, leaks are easy to find unless they're like this one, which was literally 2 units away from where the red line starts.
Reduce the size of the grid, sometimes that allows you to pinpoint the leak a bit more precisely
I have my grid on 1 90% of the time anyway.