Too many faces


Too many faces

One of the tings that can slow down renduring time is the amount of faces, edges, and points that a card has to render. A point is where the lines meet up. An edge is the line between each point. A face is the triangle that appears when you have three edges connect three points. A square at minimum will have four points, and five edges, and two faces. A cube would end up having eight points, 18 edges, and 12 faces. Turning on Occlusion in my Rendering Info Displays revealed that this is not the case. Cubes appear to be split in a 3×3 grid on each side resulting in 56 points, 162 edges, and 108 faces.

The interesting part is when I turned the mesh detail down to the bare minimum, the cube I was looking at went down to the basic 8 points, 18 edges, and 12 faces. This is great except any round prims, flexi’s or sculpties looked horrible. Turning the mesh detail up to the max resulted in the 3×3 subdivision of the side mesh.

Cylindars are the same way. I can understand the need to have the edge of the circle to be subdivided for a smoother surface. What I can not understand is the subdivision along the height of the cylindar.

I believe that the mesh for our prims can be further optimized. I had always assumed that they were in their most simplest forms. I wonder what the benefit is for subdividing the side up like this is.

Woodbridge (81, 75) - Jan 13, 2008 (323 days ago) by Dedric Mauriac

Tags for this Snapshot

108 12 162 18 3x3 56 8 amount appears assumed bare basic benefit card case circle connect cube cubes cylindar cylindars detail displays edge edges end face faces flexis forms great grid height horrible info interesting line lines looked max meet mesh minimum occlusion optimized part point points prims render rendering renduring resulted resulting revealed round sculpties side simplest slow smoother split square subdivided subdividing subdivision surface time tings triangle turned turning understand woodbridge

Leave a Comment

You're not logged in. If you want to post a comment, please log in.