Reducing wpollys Created 14 years ago2009-10-06 09:54:05 UTC by Skals

hello there twhlers!
Right now im making a hl1dm map, but im kinda having problems with wpolys.

What im after is trying to find out ways to lower them to get better r_speeds.

I already know a few methods:
1. i have func_walled all my little objects, pillars stair cases etc.
2. i've nulled every face you can't see in game.
3. i have added some hints (not too sure how to properly use them tho).

are there any other methods to lower my w_pollys? any suggestions? ty for reading.

Increase the texture scale on large surfaces.
If you also have very small detail objects in your map, like small pipes, func_illusionary those. Don't overdo it though.

Note that incorrect useage of HINT brushes actually increase wpolies and thus r_speeds.

What's your current wpolys?

What kind of areas/objects are causing your trouble? Screenie us.

lower the bsp node size to 128 (default 1024) and compile with full vis. You're compile time will be upped, but your map's organization will be tighter.

that's how I keep them down.

Kinda like this.the blue tinted areas are the nodes being drawn. This does not slice up your polies into tiles either. infact, they automatically dice up every 240 units unless the texture applied is scaled differently.

This greatly helps in those spots where there's a door or something that allows a small view into a new area. This is all noticeable if you use r_speeds and wireframe to check your map.

ZOMG that is awesome rim! (should be stickied!!!)

i can't believe i've never heard of that before... is the increased vis time dramatically horrible? how bout on a horribly optimized map, will you still see noticeable improovement?

Probably. Vis time will get a boost, this is a final compile thing anyway. Even on a optimized map, it might drop the count in some areas but not others. It's always variable anyway.

Try it, and POAST SCREENSHITS!

EDIT: also, lose the hint brushes if you do the above method. they do nothing.

You learn something new every day.

How do you even find out about these things?

Read the HL source code every night before going to sleep.

What would happen if it was set to one?

The compile process would run for 6.66 years and then your computer would melt.

But your map would be well optimised.

But is it worth selling your map to Satan?

... Yes.

The minimum is 64. It takes a while to compile but works well.

heres my map:at worst cases it goes all the way up to 3000 wpolys.
i'll try rimrooks method now.

edit: er, i just set max node size to 128, put it on full vis and compiled using compilator. my map now has 200 more wpolys >.>
i can see the nois changes in gl_wireframe, but for some reason the wpolys just went up.

Rimrook, i tried this method a few times. it doesnt reduce my pollys it just increases them. on 128 max node, i had 3100 wpolys in 1 place, on 64 i had 3200 in the same place.

You should def. try experimenting with HINT brushes, the layout in the area you showed us should make them more-or-less effective.