On Fri, Dec 17, 1999 at 11:28:02PM +0200, Eero Pajarre wrote:
> I have not so far have met any texture problems
> (I would change performance for correctness,
> if it would happen in my program...)

You likely wouldn't unless you are using multitexturing and have more
textures than available memory.

> I will try tomorrow if I can use Mesa with Q3
> 
> (I am using Win95, and I use Mesa for my own work
> because of my problems with 3dfx drivers,
> but Q3 uses the 3dfx stuff)

You can easily turn it back on if you want. Look at fxsetup.c. The
correct code is just #if 0'd out with a comment explaining why.

In fact, I think I found a way to allow both TMUs to be used, but only
incur the performance penalty in the multitexturing case, so that will
be a little better, but I still want to figure out why the functions
don't work in the first place.

> So you said that the problems were with the jump pads,
> and with the current Mesa? (3.3 or 3.2 ?)

No, the the jump pad was the repeating textures. That's fixed.

The easiest way to reproduce it is to take the existing code, but change
fxsetup, to always store the textures in TMU1. (Reverse the case of my
current work around) Now, you'll see corrupted textures
everywhere. Obviously forcing them to TMU1 shouldn't make any
difference, but it does. It looks like a problem in setting up the
multitexture, because texture0 is in TMU1, and texture1 is in
TMU0. That's supposed to work, but doesn't.

The better workaround I found was to notice when the textures are
reversed when setting up multitexturing and force them out of memory at
that point. That seems to allow me to place textures in either TMU
without problems. It only textures the performance hit (of swapping the
textures) when you are multitexturing the textures are reversed. So,
it's less of an impact, but it is still broken.

The other bug, is that the fog in the q3tourney2 level near the
lightning gun and teleporter flashes black sometimes. I suspect this is
related to the previous bug, but the previous workaround doesn't
alleviate this problem, so maybe not.

                                                        - |Daryll



_______________________________________________
Mesa-dev maillist  -  [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev

Reply via email to