Worldcraft / Hammer can load the PTS or LIN file (I recommened using the LIN file, even though it defaults to PTS) that describes the course of the leak, in Hammer you can follow the course of the leak in the 3D view.
If you can still load the map in HL, start HL with the parameter <i>-particles 50000</i> and enter the command <i>pointfile</i> in the console, the course of the leak will now appear as visible particles, use noclip to follow them.
Finally there's the Leakmarker that works on the .MAP file, adding a marker entity at the first gap of a certain size around the course of the leak. I haven't had much success with this utility. <a href='http://saida.lava.nu' target='_blank'>http://saida.lava.nu</a>
ok with loading the pointfile, i can see it in grid mode but not 3d, also i cant run pointfile cause after i move for about 2 secs in ns it crashes. And third one gives me a block where it is but from what i can see it is all blocked off and i have no idea where the d@mn leak is ?
this thing is starting to $hit me, cant find it anywhere and i followed the thing around and it lead to 'air' which was close to the middle of my map. Can i send this to somebody to have a closer look ?
Another (quite old) method is the sky-box-around-parts-of-the-map method. It's as easy as the title describes: Start with a huge hollowed skybox around the whole map and compile it. Normally bsp should now work without errors.(If thats not the case then u have some serious problems) Then scale the skybox to the half. If no errors occur , then just scale it down to the half again. If bsp discovers a leak then put a 2nd skybox around a quater of the map. Re-compile. Just continue this way 'til you've found all leaks. It's time consuming but it always works (as opposed to the pointfile thingy)
Comments
If you can still load the map in HL, start HL with the parameter <i>-particles 50000</i> and enter the command <i>pointfile</i> in the console, the course of the leak will now appear as visible particles, use noclip to follow them.
Finally there's the Leakmarker that works on the .MAP file, adding a marker entity at the first gap of a certain size around the course of the leak. I haven't had much success with this utility. <a href='http://saida.lava.nu' target='_blank'>http://saida.lava.nu</a>
It's as easy as the title describes:
Start with a huge hollowed skybox around the whole map and compile it. Normally bsp should now work without errors.(If thats not the case then u have some serious problems)
Then scale the skybox to the half. If no errors occur , then just scale it down to the half again. If bsp discovers a leak then put a 2nd skybox around a quater of the map. Re-compile. Just continue this way 'til you've found all leaks.
It's time consuming but it always works (as opposed to the pointfile thingy)
-Paladin