oct vs. quad

New Message Reply Date view Thread view Subject view Author view

Joe Castillo (rltyme++at++banet.net)
Mon, 23 Mar 1998 06:32:06 -0500


Hello

In this paragraph,

"Culling: The hierarchy that you make should be spatially
     organized in a way that the culling process can quickly and
     efficiently decide what to draw. The culling test in Performer
     takes place at the geoset level and thus your MultiGen
     database should use groups as your culling nodes. I have
     found that an oct-tree is better than a quad tree since it will
<---------------?
     make a shallower hierarchy. If you make too deep of a
     hierarchy you will be spending all of your time culling and little
     time drawing. This is a balance act between culling and
     drawing.

Can anyone describe the terms "oct-tree,quad-tree?"
How can or does it effect my hierarchy when I'm using externally
referenced models? instanced? LODs?

thank you all......

Joe :-0

Hello

In this paragraph,

"Culling: The hierarchy that you make should be spatially
     organized in a way that the culling process can quickly and
     efficiently decide what to draw. The culling test in Performer
     takes place at the geoset level and thus your MultiGen
     database should use groups as your culling nodes. I have
     found that an oct-tree is better than a quad tree since it will     <---------------?
     make a shallower hierarchy. If you make too deep of a
     hierarchy you will be spending all of your time culling and little
     time drawing. This is a balance act between culling and
     drawing.

Can anyone describe the terms "oct-tree,quad-tree?"
How can or does it effect my hierarchy when I'm using externally referenced models? instanced? LODs?

thank you all......
 

Joe   :-0 ======================================================================= List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/ Submissions: info-performer++at++sgi.com Admin. requests: info-performer-request++at++sgi.com


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:57:04 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.