Re: pfCycleBuffer's causing SEGV's

New Message Reply Date view Thread view Subject view Author view

Jenny Zhao (zhz++at++dandan.asd.sgi.com)
Mon, 9 Sep 1996 12:40:45 -0700


unfortunately pfCycleBuffer doesn't handle indexed geosets.

On Sep 9, 3:31pm, Brian Furtaw wrote:
> Subject: pfCycleBuffer's causing SEGV's
> Question:
>
> Do pfCycleBuffers work with indexed pfGeoSets?
>
> The reason I ask is this, the man page says this,
> While pfCycleBuffers can be used for generic dynamic data, a
> prominent use is as attribute arrays for pfGeoSets. The function
> pfGeoSet::setAttr accepts pfCycleBuffer memory for attribute
> arrays and the pfGeoSet will index the appropriate pfCycleMemory
> when rendering and intersection testing.
>
> Currently, pfGeoSets do not support pfCycleBuffer index lists.
>
> Does this mean the index list or the whole pfGeoSet containing the
> index list. I am trying to use a CycleBuffer in an indexed GeoSet as
> the list of vertices and I am getting coredumps (SEGVs). So the
> CycleBuffer's are causing memory to be accessed illegally somewhere,
> without CycleBuffers the code runs fine.
>
> Brian
>
>
> --
> o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o
>
> Brian Furtaw (brian++at++sgi.com)
> RSE Graphics/Communications Office: (301) 572-3293
> Silver Spring, MD Fax: (301) 572-3280
> =======================================================================
> List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com
>-- End of excerpt from Brian Furtaw

-- 

Jenny Zhao zhz++at++asd.sgi.com 415 933-5091 (Voice) 415 965-2658 (Fax) Silicon Graphics - IRIS Performer ======================================================================= 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:53:31 PDT

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