From: R. A. K. <rak...@gm...> - 2008-01-09 04:49:05
|
On Jan 8, 2008 7:48 AM, R. Aditya Kadambi <rak...@gm...> wrote: > > > On Jan 8, 2008 7:44 AM, Brian Paul <bri...@tu...> > wrote: > > > Brian Paul wrote: > > > On 1/5/08, Wes Bethel <ewb...@r3...> wrote: > > > > > >> - Using h/w accelerated rendering (I have a laptop with a ATI R200 > > card, > > >> it uses Mesa 6.4.2 (IIRC) in conjunction with DRI to do h/w > > >> acceleration), and also skipping the size check, it looks visually > > like > > >> data from only one of the texture slices is accessed regardless of > > the > > >> texture coordinates I specify. In other words, while the (u,v) > > >> coordinates appear to produce the correct value, the w coordinate > > >> (texture depth) appears to be hard-wired regardless of what I > > specify. I > > >> actually believe the problem is a bit worse than this -- I don't > > think > > >> the (u,v) coordinates are being correctly mapped to a 3D texel > > location > > >> either. However, it is difficult to explain clearly exactly what the > > >> problem is. Suffice it to say there is a problem mapping a (u,v,w) > > >> texture coordinate to a 3D texel. > > > > > > I can't test R200, unfortunately. Maybe someone else can look into it. > > > > To prevent this issue from getting lost, please file a Mesa bug report. > > > > -Brian > > > Hi Brian; > > I am still working on this. I got a patch on the dri-users list that I > need to try. I will file a report as soon as I finish my investigation. > > -Aditya > > This was fixed today with a patch from Roland Scheidegger I have filed a bug report and included the patch in the comments. It is Bug #13980 https://bugs.freedesktop.org/show_bug.cgi?id=13980 Thanks, Aditya |