Andy Ross wrote:
Keith Whitwell wrote:Andy Ross wrote:Is it possible [...] to get the client-side libGL to look somethere *other* that /usr/X11R6/lib/modules/dri for drivers?It's LIBGL_DRIVERS_PATHPerfect. Thanks.You also don't exhibit a texture border bug that the ATI drivers haveWe fallback on some texture border cases.Not this one, I suspect. The runway markings are built up of tiled quads, drawing the whole texture into each quad. This makes up probably 20-30% of the screen pixels at startup; if you were rendering them in software I'm sure it would be noticeable. Actually, I'm fuzzy on the spec here. The DRI (and NVidia) drivers appear to *not* sample the texture border color by default when drawing quads with texture coordinates of exactly 1 and 0. The ATI ones seem to do so, which results in a dark stripe between tiles (FlightGear doesn't bother to set the border color and leaves it as black). Problem is, my cursory reading of the spec says that ATI is right and the rest of the world (!) is wrong, even though that would make life hell for people who simply want to build up tiled images and don't care (much) about border artifacts. What's the truth?
Texture borders are kinda complicated. You can either define an explicit image border (glTexImage2D's border=1) or use the default texture border color. Whether or not the texture border is sampled is determined by the texture filter and wrap mode. There are lots of mode combinations, some of which sometimes sample the border, and others which never do. Texture borders are an area that's still kind of flakey in today's drivers. They've always been trouble. I've been pretty careful to get this right in Mesa's software rasterizer. The Mesa/test/texwrap.c demo shows a bunch of different modes.
There are sporadic rendering bugs in FlightGear, however. Every ~40 frames or so, I'll see a large triangle or two flash on the screen.How recent is this driver? I fixed some problems like that a week or two ago.It's CVS from the trunk as of yestserday afternoon. Should I be using a different branch?I'm also seeing some stability trouble in FlightGear.These sorts of bugs are basically impossible to debug remotely. Unless you're willing to dig into the driver yourself, or at least figure out a way to easily reproduce the problem in a (much) less complicated program than flightgear, or convince someone to spend *a lot* of time working through it with you, it won't get fixed. Try and narrow the behaviour down.Yeah, this was mostly a shot in the dark. I was hoping someone could chime in with a note like "you need to enable the whizgig when running on your hardware version" or "check the foozle to see what lock the server is waiting on", etc... I'll take a closer look. Andy
-Brian
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
