From: jan p. springer (jsd++at++igroup.org)
Date: 02/11/2006 05:17:41
Bram Stolk said the following on 02/11/06 09:45:
> Hi,
>
> I had a crashing perfly once that could be remmedied by specifying the visual with -t
>
> First you select your Id with glxinfo -t
>
> Then you run perfly as perfly -t 0x??
>
> Maybe this will let you run the latest nvidia driver.
>
> Bram
too true. starting w/ 81.87 drivers perfly/pfCity need -t0x... (actually i
use 0x21 as a default). i've submitted a bugreport to nvidia but got no
answers back. i'm wondering if the performer team already realized this.
if you're (or anybody else is) interested i've build a visual selector for
our vr framework that doesn't have that problem at all. you can find it here:
[http://cvs.sourceforge.net/viewcvs.py/avango/avango/src/modules/interface/fpFrameBufferConfig.c%2B%2B?view=markup]
(the interesting bits are in 'fpFrameBufferConfig::configureFrameBuffer')
to the original problem i could imagine that somehow __GL_SYNC_TO_VBLANK
might still be set (to anything != 0), so although the draw is around
1ms you would still be bound to vertical retrace which depends on the
refresh rate of your display (as specified by the xorg modeline used). if
you know the limits of your hmd (xres, yres, refresh) then buidling a custom
modeline with gtf should be the way to go.
cheers,
j.
-- +------------------------------------+--------------------------------------+ | jan p. springer | jsd++at++igroup.org | | computer science, buw.media.vrsys | jan.springer++at++medien.uni-weimar.de | +------------------------------------+--------------------------------------+
This archive was generated by hypermail 2b29 : Sat Feb 11 2006 - 05:18:04 PST