From: MLM Veraart (veraart++at++fel.tno.nl)
Date: 04/27/2001 01:14:35
Boris Mansencal wrote:
>
> Mario Veraart wrote:
>
> > Boris Mansencal wrote:
> > > When default sorting is enabled during cull traversal,
> > > are pre- and post- draw callbacks also sorted ? How ?
> >
> > The use of draw callbacks disables the sorting for all geometry below the callback.
> > Performer doesn't know the state change that you perform in the callback.
> > I think that all the geometry is just rendered in tree traversal order.
> > If your top scene node has a draw callback it results that is no sorting.
> >
> >
>
> Thank you.
> Where can I find this in the doc ?
Some piece from the pfChannel man page:
Sorting by state is limited to the scope of a transformation (pfDCS or
pfSCS) or a node with draw callbacks, i.e. - pfGeoSets affected by
different transformations or draw callbacks are not sorted together.
However, range sorting spans both transformation and draw callback
boundaries. Thus a range-sorted scene graph with many transformations
and expensive draw callbacks may suffer reduced performance due to an
increased number of transformation and draw callback changes.
> If the draw callback is not on the root node, but on a pfGeode of the scene graph,
> in which display list are put the pfGeoSets of this pfGeode (the opaque or transparent
> one) ?
>
You can find out in which bin it is in by calling pfDrawBin(binnr) instead of pfDraw().
For binnr you can use the following names
PFSORT_OPAQUE_BIN draw opaque bin
PFSORT_TRANSP_BIN draw transparent bin
Mario
This archive was generated by hypermail 2b29 : Fri Apr 27 2001 - 01:15:42 PDT