Hi,
The Makefile in directory 'Mesa-3.0/widgets-mesa/src' does not build
the 'libMesaGLwM.a' library. Issuing the 'make libMesaGLwM.a' command
does not work either.
This has not changed in 3.1 beta 3. I see that all RPM packages also
lack this library.
Shouldn't this be corrected? Am I missing
Hi,
for some time i thought this was a bug in the glx-mga driver, but its the
same with X11-sw and 3dfx:
http://www.tu-bs.de/~y980/q2water.jpg
(taken from "quake2 +map q2dm1")
The water is supposed to be blue like the small triangle i have marked.
For some silly reason it is mostly blue
I've been wanting to finish Mesa 3.1 for some time now but
there's still outstanding bugs to be fixed. Keith's been
working on those and in the mean time I've been working on
newer development. We believe it's time to make a branch so
we can do both.
Here's the plan:
We're adopting an
SiO2 Software wrote:
1. The sample texgen.c is busted - the teapot is drawn smooth-shaded
wireframe.
2. Texturing is broke in some instances - texture coordinates are zero
(hence texel [0,0] is always used).
Anyone else seen these problems?
I just did a cvs update and clean build and
Brian Paul [EMAIL PROTECTED] wrote:
I've rewritten the texture download paths. The code is much
cleaner now, less memory is used, and it's faster. Yeah!
Cool!
This was long-overdue work. I was hesitant to make these big
changes for Mesa 3.1 but John C. pushed a bit. I've done
enough
Hi Guys,
Well, we went back and re-visited the Assyntax.h stuff again, and
worked through the problems we were having. The problems we had were
as follows:
1. No 'good' cpp is available on Win32 with most compilers. To solve
this we now have a copy of the Cygwin cpp.exe in our build path
Kendall Bennett wrote:
Brian wrote:
This was long-overdue work. I was hesitant to make these big
changes for Mesa 3.1 but John C. pushed a bit. I've done
enough testing that I feel good about putting this code in 3.1.
Of course, let me know asap if you find a new texture download
I've checked in some rather significant changes to the tessellation code.
The winding rule code has evolved a lot, and all three tessellation demos
should work correctly - except the self-intersecting parts of book/tesswind.
The first half is okay, but I'm tracking down problems in the segment
I've found that your new tessdemo stops working if the lines self
intersect. Is this a requested behavior?
The self-intersecting code is still under development at the moment. It
works in some instances (ie. the star in book/tess), but I'm still ironing
out the implementation of contour
And finally Ted, I just built Mesa on Win32 and got several thousand
warnings. This does seems a little high... Are we still trying to fix
this?
Yeah, that's about right. ;^(
I'll be working on it, but it's a slow/mechanical process ...
I wasn't able to get the warning logs up on the www
10 matches
Mail list logo
