From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36762] New: broken minimap on 0ad alpha5
Date: Mon, 2 May 2011 01:15:30 -0700 (PDT) [thread overview]
Message-ID: <bug-36762-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=36762
Summary: broken minimap on 0ad alpha5
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: fabio.ped@libero.it
After this recent commit of the 0ad game (which will be available in the
upcoming alpha5 release):
http://trac.wildfiregames.com/changeset/9139
the game minimap on r300g is broken and it looks like this:
http://img194.imageshack.us/img194/3881/0adbrokenminimap.png
This is especially noticeable with circular minimaps, e.g. on Death Canyon map:
0ad -quickstart -autostart='Death Canyon'
The developer thinks that the 0ad commit is fine, and indeed with other drivers
(I tested r300c, llvmpipe and swrast) the minimap is OK.
I reproduced this bug with current master, 7.10 and 7.9 mesa branches.
The 0ad report is here: http://trac.wildfiregames.com/ticket/803
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-05-02 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 8:15 bugzilla-daemon [this message]
2011-07-19 12:24 ` [Bug 36762] broken minimap on 0ad alpha5 bugzilla-daemon
2011-07-22 8:09 ` [Bug 36762] broken minimap on 0ad >= alpha5 bugzilla-daemon
2012-03-03 21:39 ` [Bug 36762] broken minimap on 0ad >= alpha5 and <= alpha8 bugzilla-daemon
2012-03-16 22:00 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-36762-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.