From: <ant...@wm...> - 2000-08-14 09:41:51
|
While I am trying to figure out why 3.3 does not work with Q3demo (but works w/ Q3test or SOF, but for some reason the top 40-80 scan lines are cut off.. that's another weird thing.. maybe because I have X4.0.1 ?) I stumbled accross this weirdness: with all the Mesa's that come w/ Q3test and Q3Demo and Q3A they will default at 640x480x16bit colordepth and 16bit Zbuffer on my Voodoo2. For some reason when I use 3.3 with Q3test and Q3demo (before it crashes) they report that they have a 24bit Zbuffer!? Now maybe i am confused, but doesn't the Voodoo2 have a maximum of 16bit zbuffer (either integer and floating point? I think that's what Gary Tarolli told me) Another problem I noticed is that the FXMesa module is version 0.30 but it does not detect (or at least report) the right settings for my Voodoo2: One of the old ones: GL_VENDOR: Brian Paul Mesa CVA Extension (C) 1999 Keith Whitwell GL_RENDERER: Mesa Glide v0.30 Voodoo_Graphics 0 CARD/4 FB/4 TM/2 TMU/NOSLI GL_VERSION: 1.2 Mesa 3.1 beta as opposed to the new one: GL_VENDOR: Brian Paul GL_RENDERER: Mesa Glide v0.30 Voodoo_Graphics 0 CARD/0 FB/0 TM/2 TMU/NOSLI GL_VERSION: 1.2 Mesa 3.3 0mb of Framebuffer? 2Mb of texture memory? At least it got my 2TMU's right. It obviously works ok, but I am wondering why it does this? |