Leak - I really dont know where... Created 9 years ago2015-08-15 10:02:09 UTC by ZAP

Hi! I tred a lot of times fix this leak and I cannot find it :/
Someone can help me? And what do you think about map (technical) ofc. map isnt finish yet.

http://www34.zippyshare.com/v/5p19MVDv/file.html

What methods have you tried to find the leak? Big block? Loading the pointfile?

You have cycler sprites in the void.
That'll do it everytime.

I deleted it for test and still is leak :/
I tryed big blck and pontfile

Ok. I will try other method

It looks like you built this either not snapped to the grid, or with your grid set to 1.
All of these sections, as well as giving other mappers nightmares, are liable to be full of microleaks that are damn near impossible to lock down.Keep your wall widths consistent and your geometry neat. I can't imagine how tiring it must be to work with such disorganised brushwork. As a general rule, make your basic geometry at gridsize 16 or above. You can go much smaller when it comes to specific detailing, but for the majority of your brushwork, stay as tidy as possible to avoid exactly this situation.

I using max: [

Regardless,

As a general rule, make your basic geometry at gridsize 16 or above. You can go much smaller when it comes to specific detailing, but for the majority of your brushwork, stay as tidy as possible to avoid exactly this situation.

Use the square bracket keys to adjust it.

To be fair, i just saw the floating cyclers and immediately saw that as the issue - I didn't even try to compile.
That being said, your map should still generate a pointfile if the compile tools detect a leak. After compiling, in Hammer, Go to MAP > Load Pointfile. The .pts file should be located wherever your .rmf or .map is located.
You'll see a funky colored line bouncing all over the place. Follow that in the 3D view starting from the leaked entity (noted in the compile log).