[info-performer] Effects of PFDRAW_OFF?

New Message Reply Date view Thread view Subject view Author view

From: R Krijnen (krijnen++at++fel.tno.nl)
Date: 10/10/2002 09:05:13

Hi pfExperts,

Question:
What still happens internally in performer when I call PFDRAW_OFF
(pfChannel::setTravMode)?

I know the cull and draw callbacks for that channel will not be called
anymore!
But what is the performer still doing (in software/hardware)?
is the draw process still actively trying to sync with pfFrame?
How do I minimize this effect?
Are there any other activities that have to do with cull and draw?
Or ...
Is there a better/other way to disable the cull+draw process of a performer
application?

I have two application running on the same pipe. But I disable the channel so
one application won't bother the other. At least that's what I want. I still
have a slight performance hit on the active application (won't run a steady
60Hz anymore) compared to running them separately!
I'm using a 3Pipe 6CPU Onyx2 Ir2 with Irix 6.5.5 and Performer 2.2.6
First app running APPCULL_DRAW (pipewindow from 0,0 - 1280,1024)
Second app APP_CULL_DRAW (pipewindow from 1280,0 - 2560,1024)

Thanks,
Robbert Krijnen 

--
Senior Scientific Researcher  --  Command & Control and Simulation
TNO Physics and Electronics Laboratory
Oude waaldorperweg 63  --  PO Box 96864, 2509 JG the Hague
The Netherlands  --  http://www.tno.nl/instit/fel/ebf
T +31 (0)70 374 02 78  --  F +31 (0)70 374 06 52

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Thu Oct 10 2002 - 09:05:47 PDT

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