Page 1 of 1

Occluding materials

Posted: Sat Jan 14, 2006 3:17 pm
by ClayOgre
I was looking at the 2.0.4 bzw man page and noticed the "occluder" function in the materials statement. If I make use of this, does it mean that things get speeded up, since anything that is blocked (i.e. behind an object using an occluding material) by this material doesn't get rendered? I was under the impression that originally everything got rendered in the game, whether you were actually looking at it or not.

Posted: Sun Jan 15, 2006 9:18 am
by optic delusion
Of course I have no actual knowledge but...
The way I have it figured is, it only draws the back-sides of objects if you apply transparency in the map file. But it does draw objects hidden by the object in front.

here is a related link. I think the lack of response proves my theory.

I'm still on a slow computer, and start losing FPS instantly when something isnt right..
so the way I tested was I created a worst case scenario map, where I looked thru twenty semi-transparent objects simultaneously.
If I used transparency in the matrix, FPS immediately went waaay down.
If I used a transparent texture, FPS was the same as a regular texture.

The only explanation I could come up with was that the client draws back-sides of an object only when transparency is applied mathematicly. It doesn't know the difference between a transparent texture and a regular one.
So this means it draws the sides of objects towards the player, whether another object is in front of it or not.

I'm pretty sure you will see vast improvements in occluder operation in version 2.1.