Felix Kühling wrote:
Hi,
even with LIBGL_SYNC_REFRESH I get bad tearing with quake2. I looked
into the source a bit and now I'm scratching my head about this
question: Does waiting for a vblank do anything useful if you havn't
flushed the 3D hardware graphics pipeline before? I believe the driver
On Thu, 2003-06-05 at 23:29, Felix Kühling wrote:
>
> even with LIBGL_SYNC_REFRESH I get bad tearing with quake2. I looked
> into the source a bit and now I'm scratching my head about this
> question: Does waiting for a vblank do anything useful if you havn't
> flushed the 3D hardware graphics pip
Hi,
even with LIBGL_SYNC_REFRESH I get bad tearing with quake2. I looked
into the source a bit and now I'm scratching my head about this
question: Does waiting for a vblank do anything useful if you havn't
flushed the 3D hardware graphics pipeline before? I believe the driver
should call something
Felix Kühling wrote:
On Thu, 05 Jun 2003 16:51:27 -0600
Brian Paul <[EMAIL PROTECTED]> wrote:
Felix Kühling wrote:
Hi,
even with LIBGL_SYNC_REFRESH I get bad tearing with quake2. I looked
into the source a bit and now I'm scratching my head about this
question: Does waiting for a vblank do anyth
On Thu, 05 Jun 2003 16:51:27 -0600
Brian Paul <[EMAIL PROTECTED]> wrote:
> Felix Kühling wrote:
> > Hi,
> >
> > even with LIBGL_SYNC_REFRESH I get bad tearing with quake2. I looked
> > into the source a bit and now I'm scratching my head about this
> > question: Does waiting for a vblank do anyth
