Leaked???

[Generalfeldmarschall Lars]

While I compile my .map, it quickly says "leaked" I don't think that this is good. Is it, and if it is, why is it doing this?

Thanks,
Lars Triver

[mohaa_rox]

You didn't make a skybox. Make a box much larger than your map and press hollow. Apply the sky textures.

[General Death]

You didn't make a skybox. Make a box much larger than your map and press hollow. Apply the sky textures.

He can get the ***Leaked*** msg even if he has a skybox. Gotta make sure that all of the skybox sides dont have a gap. As far as problems I have not noticed a difference on a small map.

[Innkeeper]

I would love to get the skinny on leaks. If you use the dulplicate function to replicate a light, there is a good chance you will get a leak. I read a lot of explinations about leaks and am not sure what to believe. The original writers of the compiler know, but who are they and why don't they tell us who they are. (well, I do know why they don't tell who they are) But it would be nice to know the true explanation of the problem.

[jv_map]

A leak is a location where an entity can reach the void.

The 'leaks' caused by duplicating entities are not real leaks: they won't stop the compiler from making vis leaf nodes

You'll only get the 'leaked' error when you're map isn't enclosed by structural brushes.

The bsp compiler divides a map into a lot of vis leaf nodes, which are just small, usually rectangular volumes. Later, the vis compile uses these leaf nodes to determine the visibility on different locations. So, for a vis compile you need a leaf node layout, which cannot be made when you're map has a leak, because you would have unlimited leaf nodes.

Not sure whether that makes much sense anymore .

[mohaa_rox]

Oops! Wrong advice! Sorry.

[Generalfeldmarschall Lars]

Thanks guys for the tips and explinations. This will help in my mapping.

Lars Triver