Real-time Database Manipulations

New Message Reply Date view Thread view Subject view Author view

Dave Russell (drussell++at++vsl.ist.ucf.edu)
Tue, 11 Jul 1995 14:17:45 -0400


All right, so I've spent several months working on code which I knew broke a
basic rule of Performer. On the Indigo2 that I've been developing on,
everything seemed fine, so I assumed that I had gotten away with something
despite the protests of my resident Performer notable ( Mr. Marrou :) ).

I am working on producing free play destructable buildings. On the Indigo2,
(or an Onyx 4 CPU in APPCULLDRAW), I modify the Performer tree from a sproc'ed
and haven't had any problems. As someone obviuosly knew, my cute little trick
doesn't woek well at all on the Onyx in multiprocess mode. The problem that I
have now is how to correct my obviuos mistake without destroying the neat class
structure that I developed in the process. (I'd also like to keep from
hampering the overall applications speed anymore than I have to.)

>From what I understand, in Performer 1.2, I will have to move all of my
Performer Tree manipulation into the APP process if I want the system to work
properly. In Performer 2.0, it looks like I could use the pfBuffers in order
to do almost exactly what I'm doing now.

I guess my question boils down to this: is there any way that I can generate
ANY perform tree infromation in a process sproc'ed off the APP and get the
system to work?

(And maybe someone could give a brief reason for why heirarchy construction is
limited to the APP process. Preferrably something more than the "just because"
that I'm getting from the guys here.)

Thanks for your help. I'd be glad to go into a little more detail of the
system if it would helpl someone give me a solution to the problem. I just
figured since I knew I was doing something that I shouldn't do, I'd start from
there.

-- 
David Russell				|    	
Visual Systems Lab			|	Static worlds breed	
Institute for Simulation and Training	|	   static minds.
					|	     
drussell++at++vsl.ist.ucf.edu		|   CHANGE YOUR (virtual) WORLD!

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:51:40 PDT

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