From: Stuart Ballard <sballard@ne...> - 2001-07-23 17:54:53
[adding dri-devel to the recipients - I suggest responding to only one
list or the other as appropriate, but please keep me cc'd as I'm not
subscribed to either list]
I sent the following message to dri-users yesterday morning:
Stuart Ballard wrote:
> I'm using the version of DRI that came with XFree86 188.8.131.52 (yes, I
> know, unreleased snapshot, unsupported...) on a Matrox G450 card with
> kernel 2.4.2.
> When playing Descent 3 from Loki, I have to specify the
> "--nomultitexture" option or I get what is described in the D3
> documentation as a "hall of mirrors" effect. What actually seems to
> happen is that a large proportion of surfaces (wild guess: any surface
> with multitexturing specified?) are neither drawn nor erased: whatever
> was there in the previous frame stays there.
> My questions are, basically:
> - What am I missing by not getting support for "multitextures"? What are
> - Is it a known bug that multitexturing isn't supported on Matrox cards?
> - If I upgrade to the latest XFree, DRI and kernel, is this fixed? If
> not, is it on the cards to be fixed in the future?
I've received a couple of responses, and they boil down to confirmation
that the problem still exists with the latest XFree and DRI CVS. I've
also received a response from a Radeon user indicating the same problem.
But nobody seems to know exactly what multitexture actually is, or
whether this is a known problem and being looked at.
I found a reference in November 2000 by searching for multitexture in
the archives (I think the archive search is broken, because a search for
"Torvalds" also showed only mails from 2000, not any recent posts) which
indicated that a multitexture bug had been solved, but I've had
confirmation that this particular bug still exists.
So I'm forwarding my question here - is the requirement to specify
--nomultitexture on Descent3 (and the free demo available from
lokigames.com if you're looking for a test case) a known bug; what am I
missing by specifying it; and is there any prospect of it being fixed?
Thanks in advance,
Get latest updates about Open Source Projects, Conferences and News.