Journal #2804
Posted 18 years ago2005-12-15 09:46:04 UTC
ULTIMATE R_SPEED CATALYST!
Here's how it works:
You don't need anything else besides the batch compiler. You don't need to know about hints or any of that. First, in the BSP (or csg, one of these) tab of the compiler, there is a setting called "MAX NODE SIZE" or something like that. enable it and change the value to it's minimum, which is 64. Combine this with a FULL-VIS compile. You might not notice it, but pretty much EVERYTHING you don't see gets automatically cut away. Even the backsides of pillars and smaller objects, sometimes. I tried this with some of the more harshly-made maps of mine, and can cut over 900 wpoly's from the count very easily. The best part, no extra work with hints. It's Automatic and optimized perfectly.
If you want to hint areas to cut the poly's down by a little more, you certainly can. But be warned that this can misload sections and cost you.
The HL Engine, once again, is even more powerful than we all think.
Here's how it works:
You don't need anything else besides the batch compiler. You don't need to know about hints or any of that. First, in the BSP (or csg, one of these) tab of the compiler, there is a setting called "MAX NODE SIZE" or something like that. enable it and change the value to it's minimum, which is 64. Combine this with a FULL-VIS compile. You might not notice it, but pretty much EVERYTHING you don't see gets automatically cut away. Even the backsides of pillars and smaller objects, sometimes. I tried this with some of the more harshly-made maps of mine, and can cut over 900 wpoly's from the count very easily. The best part, no extra work with hints. It's Automatic and optimized perfectly.
If you want to hint areas to cut the poly's down by a little more, you certainly can. But be warned that this can misload sections and cost you.
The HL Engine, once again, is even more powerful than we all think.
Comments
You must log in to post a comment. You can login or register a new account.