Entity origin outside the map
The entity origin outside the map leak is probably THE biggest pain I've ever run into with leaks.
One thing that would greatly help with leaks is if the build tools and their errors were better integrated with Hammer. If allowed, Hammer ought to not run vis and rad in the event of a leak, and instead stop the build, load the point file and immediately center the map on the entity that triggered the leak. At a minimum, allowing one to go to the start of a leak trace automatically would be fantastic - far better than relying on flying around in 3d space to find it or trying to find the coordinates via the build log.
rant off :^)
Can we move this page to Leak? It would make a nice addition to Category:Glossary. The page Leak cannot be categorized as long as it's a redirect, on the other hand Leaks Explained wouldn't be a good glossary word. Jupix 05:57, 2 May 2006 (PDT)
Non leak bsp errors
Bsp produces errors other than leaks. Where should they go? The vbsp article is just usage info, so doesn't look like a good place. --22g TargetPractice 10:23, 11 Aug 2006 (PDT)
- Compile Errors or Category:Level Design FAQ are two articles that might be what you're looking for. --Giles 10:43, 11 Aug 2006 (PDT)
Leak caused by camera
I don't know if this is a know bug but my camera ended up out of my skybox and that caused the leak because as soon as it was in the skybox my leek was fixed. Not sure if it should to be added to the page anyone else have that problem before.
- That could just be an effect of radius culling. The camera is not at all involved in compiling. --Wrathofmobius 14:37, 30 July 2012 (PDT)
I noticed that if you do not place any light entities, you can still compile and run your map with leaks, but if you look into them, it just ends up like this. That is not my image, but it is the same concept. Tested with Team Fortress 2. --Nicksaysmeep 21:07, 4 April 2014 (UTC)
The highest prop on this map threw a leak error. The pointfile goes straight up and stops at the skybox. The skybox is sealed off with a nodraw box. Should I delete the nodraw box? Rardaede (talk) 16:55, 20 March 2016 (UTC)
- Fixed this error. It was somehow related to another series of errors in the compilation with portals and occluder brushes. Deleted the mentioned occluders and the leak was no longer reported. Rardaede (talk) 16:55, 20 March 2016 (UTC)
I keep getting leaks on my map. I've gone so far as to hunt down 6 zero child areas thinking they might be the problem, but after finally finding them and recompiling it didn't do anything.
I have the map cordoned done to only 119 objects with entities hidden, yet I still get: **** leaked **** wihout any other information
fixing up env_cubemap materials on brush sides...
ProcessBlock_Thread: 0...1...2...3...4...5...6...7...8...9...10 (0)
- leaked ****
Processing areas...done (0)
This causes half my map to be completely dark
--phrozen_wolf 18:23, 7 July 2016 (UTC)
- "False leaks
Although very rare, it is possible VBSP reports false leaks in your level. If you are sure that there should not be a leak reported by VBSP, copy your map and paste it into a fresh new map file. If it compiles fine, then your old file could have been corrupted." --Ninjaofsauce (talk) 13:20, 27 August 2019 (UTC)