Re: [Dri-devel] Incomplete scene with OpenGL + direct rendering + mga

[<sy...@sc...>]

On Wed, Nov 26, 2003 at 09:30:57AM +0100, Jan Gukelberger wrote:
> > You should try the daily snapshots available from the DRI website...=20
> =20
> I did so yesterday.=20
> I also had to install the XFree86 binary from the 'extra' section and l=
n -s
> libexpat.so.0=20
> libexpat.so.1=20
>=20
> However, it didn't solve any problem. The examples of my first message =
still
> produce the=20
> same results as before. :-(=20

Ok I tried this myself in XFree86 and you're absolutely correct. Only the
first triangle is visible.

It looked like a clipping problem. So I added some debug printks into the
drm module but the clipping coordinates are in fact correct.

Then I tried drawing another triangle in the middle and behold the right
hand triangle became visible.

Doing a glFlush() before glutSwapBuffers() makes the last triangle
visible.

This also explains why I didn't see it with DirectFB since it always does
a glFlush() when the context is unlocked.

I think there's something wrong with tracking DMA buffer ages...

> Moreover, bzflag does now often freeze. This happens reproducably when
> enabling the=20
> option "Smoothing".

Indeed it does. Also many of the mesa demos now segfault in the spanline
functions. I think this might be what happens to bzflag too since
smoothing uses a software fallback. Although bzflag doesn't leave a
coredump for some reason...

> Any further advice?=20

I'll see if I can solve these issues and get back to you...

--=20
Ville Syrj=E4l=E4
sy...@sc...
http://www.sci.fi/~syrjala/