Any leaks finding methods ??
As we all know ..the leaks finding is the most frequent problem while mapping..
This problem is really make me sick..
All the time when i finished the map And try to make a finnal
complie.Things happen ! these leaks wouldnt dissapear even though i removed the entities.
After several hours struggle.i Gave up..
Then i have to maka a stupid sky box to fix the probs,,But it
directly caused the low fps ....I know theres a pts option to find where the leaks are.. But i dont konw how to use it...
So is there anyone tell me how to fix the problem efficiency.../?mANY thanks,, ;)
08/02/2007 18:37You could try using this: http://www.egir.dk/index.php?page=howto_leafmarker/howto_leafmarker.htm
It havent worked for me, but maybe it will for you :P
08/02/2007 19:17As we all know ..the leaks finding is the most frequent problem while mapping..
This problem is really make me sick..
All the time when i finished the map And try to make a finnal
complie.Things happen ! these leaks wouldnt dissapear even though i removed the entities.
After several hours struggle.i Gave up..
Then i have to maka a stupid sky box to fix the probs,,But it
directly caused the low fps ....I know theres a pts option to find where the leaks are.. But i dont konw how to use it...
So is there anyone tell me how to fix the problem efficiency.../?mANY thanks,, ;)
The entities are only a hint, it shows where the lines start if u load the pointfile, just find the entity and then follow the lines to the leak.
If u remove the entity the program will only choose anotherone to start the line from.
hey delson, make more often fastvis compiles to test it next time...
and make some backups while mapping...
[ Edited Thu Feb 08 2007, 07:39PM ]
08/02/2007 21:35use "leak marker"... it creats a red block near your leak (infact on one of the coordinates y,x or z... then you follow the line knowing that the leak is somewhere on that line)...
The entity near your leak can be far away sometimes : S
The best way to avoid leaks is still to learn how to map correctly... you then never get leaks unless you turn a part of the hull func or something : P
Well the day before yesterday I also had a leak. The entity near was (in the end) far away from the leak and the point file was totally unsuable - 10 km line ending upt somewhere (in the end) not where the leak was.
I did the following that will work for sure if you have a leak. It is based on the so called binary search.
I explain it like this: If someone thinks of a number from 1 to 100 and ask you to guess while he/she is going to tell you whether the number is higher or lower, the fastest way to find the number is guessing 50. If it is higher than 75. If it is lower than 25. So always in the middle so that you always eliminate half of the possible numbers.
How can you use that for mapping? Quite easily. I did this. I know from the entity at least in which room the leak was located. So I put a huge block on the one half of the room and recompiled. If the compiler says the leak is gone, it was somewhere in the area where I put the block. If not it was in the other half. Than you make the block the half size and so on until it is clear where the leak is.
This can take a while if you have no clue about the leak. But it will lead you to the leak for sure.
Hope somebody read to the end. :D
emm.After read above replys.Ih ave a pretty clear picture of how to solve the leaks..And now all i have to do is just practice .Hope i can find my own way of leaks findin in the furture!
[blockquote]Well the day before yesterday I also had a leak. The entity near was (in the end) far away from the leak and the point file was totally unsuable - 10 km line ending upt somewhere (in the end) not where the leak was.
I did the following that will work for sure if you have a leak. It is based on the so called binary search.
I explain it like this: If someone thinks of a number from 1 to 100 and ask you to guess while he/she is going to tell you whether the number is higher or lower, the fastest way to find the number is guessing 50. If it is higher than 75. If it is lower than 25. So always in the middle so that you always eliminate half of the possible numbers.
How can you use that for mapping? Quite easily. I did this. I know from the entity at least in which room the leak was located. So I put a huge block on the one half of the room and recompiled. If the compiler says the leak is gone, it was somewhere in the area where I put the block. If not it was in the other half. Than you make the block the half size and so on until it is clear where the leak is.
This can take a while if you have no clue about the leak. But it will lead you to the leak for sure.
[/blockquote] . Thank u acidburn thats make sense..
[ Edited Fri Feb 09 2007, 03:06AM ]
10/02/2007 07:55in the future just make your map neatly and u can avoid that problem to begin with.
10/02/2007 07:55in the future just make your map neatly and u can avoid that problem to begin with. (lol sorry for the triple post the internet was slow so i just clicked a bunch of times)
[ Edited Sat Feb 10 2007, 07:56AM ]
10/02/2007 07:55in the future just make your map neatly and u can avoid that problem to begin with.
I'd just had a leak. in fact 3 of them :S.
I got those from some complex shittycrap mapping. Also called bad mapping? Anyway, i dl'ed the leak marker for a while ago, i used it when i did flr_bhopvoxx.
And i can say that it really helped.
On the map im mapping on now(a lot of on's), i used the tool too. But as acidburn says, the leak can be far away from the entity. I found it somehow and solved the problem. So if u thinks that the pointfile is too complex, just download the tool that Chrizzy posted.
It really helps.
05/03/2007 19:03If I get a LEAK I just split the map in 4 or more, depends on how big the map is. Make one skybox around one of the corner and compile. if the LEAK still annoys me then I just make another skybox in another corner until the compile-log is clear of LEAKS then you know the LEAK is inside of that skybox and then its just a matter of time before you find it :)
[ Edited Mon Mar 05 2007, 07:06PM ]
compile often ^^ this way you'll know the leak is in the stuff you changed since the last compile
05/03/2007 22:12compile often ^^ this way you'll know the leak is in the stuff you changed since the last compile
That is bad. After a couple of time you wont find it anymore.
07/03/2007 10:21Just load the pointfile and follow the red line
Good job XaSer. Nexttime maybe read what people wrote before you. ;)
08/03/2007 15:43No, to much work
Please log in to post replies.