Hi all,
Again, Michel D\"anzer suggested to mail this problem to this list. This
is what I wrote him:
I'm a beta tester of the upcoming MSX emulator openMSX (see
openmsx.sf.net). This emulator also has a renderer based on the SDL GL
library. However, it seems that some things go wrong with this renderer
in its current implementation on my Ati Radeon 32MB SDR (and you know
I'm using the drivers from your site).
The author of this GL renderer, Maarten ter Huurne, suggested that the
problem was in my drivers. This is an original e-mail (partly snipped):
-------- Original Message --------
Subject: Re: [openMSX-devel] Web site
Date: Sun, 1 Dec 2002 20:05:01 +0100
From: Maarten ter Huurne <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
> It's not that broken if it works on everybody's computer except
> yours...
The code assumes textures of width 1024 are available, which is true for
some
GFX cards and not for others. However, it seems this problem also stops all
other texture mapping on Manuel's PC, I don't know whether that is correct
behaviour by the OpenGL spec or whether that is a driver bug (I guess the
latter).
----------------------------------------------------------------------------
The problem is that Maarten uses textures of 1024 pixels wide, which has
the effect that on my system the whole window stops being rendered. I
just get to see some old VRAM data of the GFX card (like parts of
previously run GL programs or so).
This is how I described it in another mail:
> Well, only in the openMSX window, not on the whole PC... ;-)
>
> > behaviour by the OpenGL spec or whether that is a driver bug (I guess
> > the latter).
>
> It is strange then that practically all other openGL apps work fine!
> (OK, there are some glitches here and there, but nothing as serious
> as this...)
>
> Before my SDLGL went completely dead, I was also still having the
> problem that any Console background is completely white in the GL
> renderer...
>
> I'm sure that I'm not the only one who has this problem. But most
> people here have NVidia cards, I guess.
Can you enlighten us about this problem? Is it indeed a driver bug or
problem?
-------------
Michel suggested it was a problem due to low texture memory:
> Yes, it's probably the bug discussed on dri-devel, triggered by low
> texture memory.
However, this is his reply on my reply to that:
> I configured X to run in 1024x768, which gives me 17MB for textures
> (instead of the 2752kB at 1600x1200), according to the X log. The
> problem is still there. (As opposed to the Tux Racer problem, which is
> gone then, as previously reported...)
>
> ...?
Hmm, no idea then, seems to be a different problem after all. Please
post to dri-devel again.
Anyone else who knows what might be the problem?
Best regards,
Manuel Bilderbeek
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
