Tremulous Forum

Media => Mapping Center => Topic started by: Odin on November 29, 2006, 08:38:34 pm

Title: Tracking down leakages.
Post by: Odin on November 29, 2006, 08:38:34 pm

How do you track down leakages WITHOUT the build menu? Currently using the build menu crashes GtkRadiant(for me). Is there a plugin that does the same thing?

Title: Tracking down leakages.
Post by: Survivor on November 29, 2006, 08:43:20 pm

Shift+Ctrl+K
Shift+Ctrl+L
?
It's in the misc menu in 1.2.13 don't know if it works, never use it myself.

Title: Tracking down leakages.
Post by: Odin on November 29, 2006, 08:46:44 pm

It's not in the latest 1.5 svn!

Title: Tracking down leakages.
Post by: Survivor on November 29, 2006, 08:50:06 pm

well, try 1.2.13 :)

Title: Tracking down leakages.
Post by: Survivor on November 29, 2006, 08:51:15 pm

Or as i remember you can force it to finish the compile even with leaks. Load up the map, activate r_clear 1 and any leaks should show up pink due to the HoM.

Title: Tracking down leakages.
Post by: Odin on November 29, 2006, 09:08:47 pm

What if I can't find anything that's coming up pink, like you said?

Title: Tracking down leakages.
Post by: Survivor on November 29, 2006, 09:11:19 pm

Without any further knowledge i really can't help. Look for the awry places where you used substract or the clipper in odd ways.
Maybe splitting the map in several parts and compiling each seperately might narrow down the location of the leak.

Title: Tracking down leakages.
Post by: KnightBear on November 30, 2006, 07:46:31 am

personally, leaks were my biggest problem starting out.  welp, i have both 1.4 and 1.5.  i typically use 1.4 for somethings, and 1.5 makes a few things less complicated.  

if leaks are a consistant problem, then id seriously suggest using 1.4.  1.5 has a feature missing.  the find next leak function under the misc menu.  its by far the superior of the line as far as funcions it was capable of.  they dumbed down 1.5 a touch to make it more stable.  i dunno how it did, because my pc likes 1.4 better anyway.  that may solve your crashing problems as well.  though some programs have issues with using the same file at the same time as another.

Title: Tracking down leakages.
Post by: Lava Croft on December 06, 2006, 01:56:11 am

Can't you just disable 'Stop compile on leak', BSP your map, and then in the File menu load the pointfile? Or am I being dumb here...

Title: Tracking down leakages.
Post by: Odin on December 06, 2006, 05:43:13 am

GtkRadiant crashes when I make a selection from the build menu.

Title: Tracking down leakages.
Post by: James on December 06, 2006, 02:22:05 pm

Binary search is the crudest but most reliable way - create a big brush over half the map, run vis, see if you get a leak - rinse and repeat, making the block smaller each time until you narrow down the location enough that you go 'aha' or spot the problem.

Title: Tracking down leakages.
Post by: Lava Croft on December 06, 2006, 03:07:23 pm

Quote from: "Odin"

GtkRadiant crashes when I make a selection from the build menu.

Stop using broken software then. Besides, if you build neatly, and with attention, you shouldn't even have any leaks at all.

Title: Tracking down leakages.
Post by: Odin on December 06, 2006, 03:33:52 pm

So you're telling me to stop using it because one feature doesn't work? I can still build from the commandline.

Title: Tracking down leakages.
Post by: Lava Croft on December 06, 2006, 10:08:43 pm

Quote from: "Odin"

So you're telling me to stop using it because one feature doesn't work? I can still build from the commandline.

Then load the pointfile it generates in Radiant.

Title: Tracking down leakages.
Post by: Revenant on December 06, 2006, 11:31:13 pm

It crashing is sometimes not just a matter of redownloading or getting a new version. Its just to do with radiant itself. Another thing, how do you know that its crashing because of a leak? There could be other problems.

Title: Tracking down leakages.
Post by: Dersaidin on December 07, 2006, 02:43:30 am

http://www.bobdev.com/q3map2build.php

Edit the .bat yourself if it doesnt have Trem specific options.