Quote from Rand0mNumbers on June 29, 2011, 2:44 am

I find the following helpful in finding and fixing leaks:

Go to the Auto tab under Visgroups.
Uncheck everything except "World Geometry".
Look for holes.

Note: If you have any instances with world geometry that join into your level (ex: elevators), you should probably check "Point Entities" and make sure they are aligned.

Additionally, if an entity's origin is outside the map, you'll get leaks in a sealed map.

Quote from DaMaGepy on June 29, 2011, 4:41 am

Marlovious wrote:

The entity isn't causing the leak. It is only the first entity that gets compiled and see's the leak. If you follow the red line from the point file (lower-left of your screenshot) to the left you will find a hole in your map. Also, make sure you are not using func_detail since these can not be used to seal a map.

Ye, finding weird leaks easier, if you hide func_details (uncheck it at visibility options panel thingie). And you dont need to unload the pointfile before you load the new one. Also if the leak starts and ends outside the map, its good to select the whole map (or part of it) to see if an origin dot causes the leak. If jes, then just try to find to what object it belong (selecting less and less part of the map) and then choose center origins from the right click menu. Also sometimes the compiler names the entity that leaked.

Quote from Brainstatic on June 29, 2011, 11:41 am

Thank you everyone for all the tips! I should have version 1.2 of Twin Pillars uploaded sometime this week or early next week.