Please or Register to create posts and topics.

Performance Issues

PreviousPage 2 of 2
FelixGriffin wrote:
Really? I just use the defaults and it doesn't make a leaked BSP.

If you switch the compile window to advanced mode, the "default" preset does include -leaktest for vbsp, so that will stop compiling when it discovers a leak. However, (on my configuration at least) the simple / normal mode doesn't do that, and I assume that this is what most novice mappers use.

I don't know whether the OP is a novice mapper, but that is besides my main point, which is: it is possible to get a leaked map to compile and run, and therefore we can't rule it out as the source of the problem.

(However, that being said, at this point I should probably admit that I never compile from within Hammer nowadays, and my statements above are based on a few quick tests, and about my knowledge about that -leaktest option. I would love to be proven wrong about this; it would be very useful to have leaked maps not compile by default, so you know immediately when you have a leak, rather than finding out about it by all of its nasty side effects, when your map is nearly finished.)

Sendificate series: Sendificate | A Beam Too Far | Airtime | 302
Other Portal 2 maps: Medusa Glare
Portal 1 maps: Try Anything Twice | Manic Mechanic
PreviousPage 2 of 2