Re: problem with V1.1

New Message Reply Date view Thread view Subject view Author view

Fred Dech (fred@cerulean.bvis.uic.edu)
Tue, 11 May 1999 11:46:45 -0500 (CDT)

Onyx2 V6.4. i managed to get around the problem
for now by padding to powers of 2 and using TRUNCATE.

the problem i've been having isn't noticable with *small* data-sets, unless
you look close. the voBrickSetIterator loop for stuffing the image data
into the bricks iterates over the same data-space multiple times (~4) when
using AUGMENT. that is, at least in my applications. i've got the same
behavior in Performer and OGL Volumizer apps.

--fred

Ballard Andrews; wrote:
>
> Fred,
>
> What platform are you running on?
> AUGMENT seems to work fine on an Octane
> in demos which use voglInitAppearance
> (which is most of them).
>
> -ba
>
> Fred Dech wrote:
> >
> > hi.
> >
> > we upgraded to Volumizer 1.1 late last week. some applications that use
> > voPartialBrickTypeScope::AUGMENT in the voBrickSetCollection constructor
> > now either exhibit some unpredictable behavior, or simply don't work.
> > if voPartialBrickTypeScope::TRUNCATE is used, they work fine, but, of
course,
> > don't process partial bricks.
> >
> > is this something that others have experienced? if so, is there a
workaround?
> >
> > thanks.
> >
> > --fred
> > --
> > Fred Dech fdech@uic.edu
> > VRMedLab
> > (312) 413-3092: fax (312) 996-8342
>
> --
> Dr. Ballard Andrews
> Schlumberger Doll Research
> Old Quarry Road
> Ridgefield, CT 06877
> tel: 203-431-5522 fax: 5521
>

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Nov 01 1999 - 13:42:01 PST