When starting a game (e.g. out-of-order) with antialias set to 1,
nothing is displayed (i.e. just a black screen / window).
There is also a message about an unknown opcode 'DDY' while
compiling.

With antialias=0 or antialias=-1, the two  games I tried seemed OK
(i.e. the intro / initial screen displays fine).

I'm attaching a debug log of out-of-order.

Regards,

Rogier.

Am 31.05.2011 11:49, schrieb Rogier:
Looks like this one:
http://lists.freedesktop.org/archives/dri-devel/2010-August/002805.html
There the answer is that the hardware doesn't support something. What
graphics card do you have? Is everything displayed correctly when
disabling antialiasing? The log you posted was with antialiasing
disabled, would you send one with enabled antialiasing?

Best regards,
Tobias Hansen

Hi Tobias,

Thanks for your reply.
It seems like it.
Wouldn't that be 'mesa doesn't support something' ? (something that would be
in hardware, if only I had a better graphics card ?)

In that case, I would expect either mesa to return a failure somewhere, and
then sludge to fail or maybe even to take corrective action (if possible at
all), or mesa (knowing it can't support DDY) to do something that at least
preserves the output.
ATI Technologies Inc RS690M [Radeon X1200 Series]
Yes.
And it is also when using linear interpolation (-a-1).
Just using antialiasing (-a1) it doesn't work.
Hmmm...
The command-line has a '-a 0' indeed, but the log _does_ include the 'DDY'
message, as well as 'Built shader program: 3 (smartScaler)', which puzzles me,
as they are unique to antialiasing...
I suspect, I made a typo while sanitizing the /usr/bin/script log file.

I created a new log with antialiasing, and except for the first line, it is
identical to the one I included in the report. It seems redundant to include
it here ...

Regards,

Rogier.

Am 01.06.2011 10:00, schrieb Rogier:
I asked the other developer (the one who wrote the OpenGL code) and he
says the driver reports success wrongly so we can't do anything about it:

http://www.adventuredevelopers.com/forum/index.php?topic=3507.0
Aren't there multiple drivers for ATI cards? Could you try another one?

Regards, Tobias

Hi Tobias,
OK.
Personally, I'll do without AA, and assume it will get fixed in Mesa, somwehere
in the future.
However, if it is useful to you in any way, I'll gladly try another driver and
report the results.

Rogier.

Am 03.06.2011 09:22, schrieb Rogier:

Would be interesting, but it's not important.

Seems like you just have to install the package libgl1-mesa-dri when
using the mesa driver.

See http://bugs.debian.org/628808

Hi Tobias,

I have been away, and I still need to check bug 628808, but liblg1-mesa-dri
was/is already installed on my system.

Rogier.

I'm attaching another mail from Rogier. (Please keep attaching to the
bug report.):

Am 30.07.2011 17:52, schrieb Rogier:

thanks for having another look at this. I have searched the web a bit on
how well the RS690 is supported by the drivers and found out that it
seems to belong to the latest graphics cards without support for vertex
shaders that were sold. sludge-engine uses shaders, so any way you can
make it work involves shader code being processed on the cpu and thus
slowness.

Here is the table stating that the ship doesn't support shaders:
http://xorg.freedesktop.org/wiki/RadeonFeature

Best regards,
Tobias

This bug should be reassigned to the libgl1-mesa-dri package. The
underlying problem is that there's currently no mechanism for a Gallium
driver shader compiler error to be propagated to the application.

reassign 628680 libgl1-mesa-dri
thanks

I see you are part of the Debian X Strike Force. It's yours. :)

Am 03.11.2011 11:42, schrieb Michel Dänzer: