Re: [Mesa3d-dev] sources.lst files

[<de...@ko...>]

>> 
>> I've reported every bug in the past that I've been able to isolate to a simple
>> test case (and they've all been fixed quickly).  Unfortunately, this one isn't so simple,
>> we use a large number of features, and the application itself is a very large, complex
>> application that takes several hours to compile and just getting the compile to work is
>> a bit hard (it's C++, needs a very recent version of gcc, STLport, etc etc), and we're
>> not yet distributing the source in a general manner.
>
>Would sending me a binary be practical?

Sure, in fact, with the next release or so, any user will be able to download the binary
from the website without a password (right now it's password protected and you
have to make a formal request).

Right now I'm struggling with getting the Linux port to work again now that the main
programmer changed some source and it's causing g++ to report an internal compiler error
(urk).

>
>Could you send me a screenshot of the problem?  That might give me a hint.

Sure: see page http://www.cgl.ucsf.edu/home/dek/mesa_bug

>> Here's some of the features we're enabling : lighting, fog, arbitrary clip planes, stippled lines,
>> alpha blend modes, material properties, depth test, line width, point size, scissor, color logic op, vertex
>> arrays, polygon offset, stencil, along with tons of texture options including 3D textures
>> when available.
>
>Can you enable/disable these different OpenGL features in order to narrow
>down or characterize the circumstances under which the problem appears?

We'll see.  It's tricky because those modes are activated and deactivated numerous
times during a frame render, and not all of them are applied when the bonds are drawn.
Certainly,lighting, fog, clip planes, alpha blending, material properties, depth testing, scissor, and color logic
op are applied during bond rendering.