When I first started using Radiant, I used GtkRadiant to compile the maps. Any leaks would show up as a white line connecting an entity to the offending leak. But now that I'm using q3map2 to compile, this no longer works. If I try to look for a leak (do a simple BSP compilation) in GktRadiant now, I get this error message:

"The connection timed out, assuming the BSP process failed. Make sure you are using a networked version of Q3map? Otherwise you need to disable BSP Monitoring in prefs."

So I turn off monitoring in the prefs. Doing a BSP compile now gives me this:

"Writing the compile script to '/Users/clund/.radiant/1.4.0/qe3bsp.sh'
The build output will be saved in '/Users/clund/.radiant/1.4.0/junk.txt'"

But still no nice white markers showing me where the leak is.

How do I fix this? While I can find the leaks by going over every single brush intersection of the map (I've already checked the places I worked on since the last build), that white line saves me a lot of time.

Everytime you compile with q3map2 and you get a leak there should be created a mymap.lin
That's the line you wnt to have. To load it click File->Pointfile... in Radiant

Strahlemann wrote:Everytime you compile with q3map2 and you get a leak there should be created a mymap.lin
That's the line you wnt to have. To load it click File->Pointfile... in Radiant

Thanks. I'll give it a shot the next time my map leaks. B)

I'm not sure if u did this yet, but did you place spawn spots? If you don't it will show up a leak. It will not point anywhere because there is no leak anywhere map-wise.