Re: pfMemory problem of Hunter database

New Message Reply Date view Thread view Subject view Author view

Marcus Barnes (marcus++at++multigen.com)
Mon, 7 Jul 1997 10:46:43 -0700


On Jul 4, 6:32pm, Jim wrote:
> I use vega3.0 and performer 2.02 on Max Impact.
> I load the Hunter database and loader prompt free() and decompConcave()
> warnning.
>
> ========================================================================
> MultiGen Inc. OpenFlight (r) loader R15.2d
> for IRIS Performer 2.x $Date: 1996/12/13 23:03:24 $
> ========================================================================
>
> => warn decompConcave() Could not decompose concave polygon!

This is a warning from pfdGeoBuilder utility. It means that the database
contains a concave polygon that it cannot tessalate. You will have to find this
polygon in the database and triangulate it by hand.

> => warn pfMemory::free() can't free() non-pfMemory data ( Error 0 )

This means that some part of your application is trying to free a piece of
memory that is not derived from pfMemory. I can offer one guess: If you've
assigned a callback function using pfdConverterAttr( "flt", PFFLT_REGISTER_NODE
) then you may be attempting to free CB_CLEAN data erroneously. See the
loader's readme file for an complete explanation.

Regards.

--
+ Marcus Barnes, Technical Staff        mailto:marcus++at++multigen.com +
+ Multigen Inc.                         http://www.multigen.com    +
+ 550 S. Winchester Blvd.               phoneto:1-408-556-2654     +
+ Suite 500 San Jose CA 95128           faxto:1-408-261-4102       +
=======================================================================
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:55:35 PDT

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