Re: [info-performer] pfUpdatable question

New Message Reply Date view Thread view Subject view Author view

From: Yair Kurzion (yair++at++polygon.engr.sgi.com)
Date: 08/08/2002 15:35:02


Hello Matt !

What methods does your pfDCS subclass define ?
Have you re-defined pf_applyUpdate ?

A little background:

o Performer creates multiple copies of each node - one for each CULL process
  and one for ISECT.

o All Performer nodes are subclasses of pfUpdatable. A pfUpdatable contains a
  mechanism to propagate node changes from the APP process to its downstream
  processes (CULL, ISECT).

o If you subclass a node, the subclass node is only available in the APP
  process. Performer creates a copy of the parent class for use by downstream
  processes. This means that you can not change the CULL behavior of a
  subclassed node. This is documented in the Performer programmers guide (in
  chapter: `Programming with C++', last page).

o When you change something on a node, Performer creates an `update' request
  for that node. Performer propagates these requests by calling pf_applyUpdate
  on a destination node. The error message you received says that your node did
  not process update code 70 (UPDCS_MATRIX). UPDCS_MATRIX is a normal DCS
  update and should be processed by pfDCS::pf_applyUpdate.

If you have a simple (small) sample code demonstrating your problem, please
send it my way and I'll try to debug it.

-yair

> In our application we get the following warning.
> PF Warning: 14976 (Performer) Internal : Attempt to apply unknown
> pfUpdatable update 70 to object of type ccDCS whose id is 16617.
>
> ccDCS is derived from pfDCS.
>
> This warning usually occurs after we move models loaded in our database
> process over to the app process. This sort of warning is usually followed
> by a segmentation violation in our cull process.
>
> I had a bit of a search in the archives, and questions on this warning has
> been posted several times before, but with no response. If anybody could
> tell me what this warning means, and perhaps a way to stop it. That would
> be great.
>
> Thanks in advance for any help,
> Matt.
>
> -----------------------------------------------------------------------
> List Archives, Info, FAQ: http://www.sgi.com/software/performer/
> Open Development Project: http://oss.sgi.com/projects/performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com
> -----------------------------------------------------------------------
>

-- 
\_________  \_____  \__    \__  \_____        
\_________  \_____   \__   \__  \_____         Yair Kurzion
       \__     \__   \____\__      \__         yair++at++sgi.com
       \__          \__  \__                  (650) 933-6502
       \__          \__   \__          
       \__          \__    \__             


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Thu Aug 08 2002 - 15:35:17 PDT

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