Ryan C Stallings wrote: > > Hello, > I am new to DRI hacking, and I am looking for some guidance. I am trying to >get the Neverwinter Nights Toolset to work under wine (http://nwwine.beergeek.net). >I have hacked wine a bit to get it working for most people, but I am having problems >with the r128 drivers that other people using different cards are not seeing. I am >using a Rage Mobility 128 with the latest CVS DRI and X 4.2. I have two problems. > > 1) Some textures don't appear (or may not repeat) when in 1600x1200 mode (they work >fine when X is in 1280x1024 or 1024x768) > > Wine makes the following series of calls > # Set GL_TEXTURE_WRAP_S to GL_REPEAT > trace:opengl:wine_glTexParameteri (3553, 10242, 10497) > # Set GL_TEXTURE_WRAP_T to GL_REPEAT > trace:opengl:wine_glTexParameteri (3553, 10243, 10497) > > When in 1600x1200 the 1st call produces a GLError of GL_INVALID_VALUE (no error in >other resolutions) the second call seems to succeed. So I think that call failing is >the problem. However I looked at the mesa source in CVS and this doesn't make sense; >these parameter seem valid. Is the GL_INVALID_VALUE being produced at a higher level >than _mesa_TexParameterfv? How could this be a product of the resolution?
Are you absolutely certain that the error is being generated by glTexParameteri()? My hunch is that it's being generated by glTexImage when too large of texture is specified. As you increase the screen size, the space left for textures is reduced. In extreme cases, the maximum texture size may be reduced as well. Have you set the MESA_DEBUG env var? > The above problem occurs in both XFree 4.1 version and in CVS. > > 2) Assert fails in r128_texstate.c > The texture that r128UpdateTextureUnit has been passed is null. I think what happens >is that the texture is deleted and set to null. Then a new texture is bound to the >old spot with glBindTexture, but no new texture is created. > r128_texstate.c:494: r128UpdateTextureUnit: Assertion `t' failed. > > This happens when a window is created on top of another window and they both have >renderings in them. The new window works fine (I believe rendering to the window >below it is stopped while the new window is pen), but when the new window is closed >(and the old window becomes the focus), this assertion fails. Someone else will have to look into the assertion. I don't have time. > This seems to be a regression. The XFree 4.1 version does not have this problem. > > I would greatly appreciate it if one of you could point me in the right direction so >I can fix the bug in the driver. -Brian _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
