Paul Sherman (psherman++at++bvr.co.il)
Mon, 22 Nov 1999 16:31:50 +0200
I am running into a little problem with shared channels and automatic
DVR. When I run a two channel application with two different channels
(not in
the same channel group), I get a dvr output that is about 1150x920 on
the
first channel and slightly larger (1160x928) on the second
channel. Statistics report draw times of 16.5 msec and 15.9 msec
respectively. Those values are for my "opening scene". Moving around in
the
database gives similar and expected values.
However, when I run the same application (except that the second channel
is
shared with the first in the same channel group), in the same database
and at
the same "opening scene" location, I get viewport sizes of 780x624 (17.1
msec) and 790x632 (15.9 msec) respectively.
My channel share mask is 0x1e05f5 which is:
PFCHAN_FOV
PFCHAN_NEARFAR
PFCHAN_SCENE
PFCHAN_STRESS
PFCHAN_LOD
PFCHAN_EARTHSKY
PFCHAN_SWAPBUFFERS
PFCHAN_STATS_DRAWMODE
PFCHAN_CULL_VOLUME
PFCHAN_GSTATE
PFCHAN_PRICLASS_LIST
PFCHAN_LPOINTFUNC
I am not sharing:
PFCHAN_VIEW
PFCHAN_VIEW_OFFSETS
PFCHAN_APPFUNC
PFCHAN_CULLFUNC
PFCHAN_DRAWFUNC
PFCHAN_VIEWPORT
PFCHAN_SWAPBUFFERS_HW
I thought that changing stress might make a difference, but sharing it
or not
sharing it seems to have no effect. I also get no change when I add or
remove
sharing on the last four attributes (PFCHAN_CULL_VOLUME, PFCHAN_GSTATE,
PFCHAN_PRICLASS_LIST, PFCHAN_LPOINTFUNC). I cannot share view, app, cull
and
draw because of the nature of my application. I also need to have the
second
channel in the same channel group as the first. I do not have a
lightpoint
function so sharing it or not makes little difference to me.
Running as root makes no real difference other than a slight improvement
in
frame rates (although not dvr output sizes). I am running with a forked
draw,
cull and compute. I lock app on cpu1, cull0 on cpu2, draw0 on cpu3,
cull1 on
cpu4, draw1 on cpu5 and compute on cpu4 (with cull1). draw0 runs with
priority 38 and draw1 with priority 39. Nothing is put on cpu0. The
machine is
an OnyxII with IR graphics.
So, does anybody have any suggestions as to what could be causing this
and
how to fix it? I am at a loss.
Thank you,
Paul Sherman
psherman++at++pobox.alaska.net
P.S. Please note that I will be on the road from the 24th of November
until the 26th
of November and will not be able to answer or respond to email queries.
Also note
that any personally responses should go to psherman++at++pobox.alaska.net and
not to
psherman++at++bvr.co.il. As you might guess, I am going home for the
holidays...
This archive was generated by hypermail 2.0b2 on Mon Nov 22 1999 - 06:32:21 PST