From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70569] New: DOTA2 background and other missing elements on HD4850 GPU
Date: Thu, 17 Oct 2013 09:49:03 +0000 [thread overview]
Message-ID: <bug-70569-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1280 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=70569
Priority: medium
Bug ID: 70569
Assignee: dri-devel@lists.freedesktop.org
Summary: DOTA2 background and other missing elements on HD4850
GPU
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: vallesroc@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 87786
--> https://bugs.freedesktop.org/attachment.cgi?id=87786&action=edit
Screenshot of the fountain on a newly started game
On a HD4850, DOTA2 in-game background and some other objects aren't being
rendered. Attached screenshot shows the problem well.
DOTA2 graphics settings are at the lowest (didn't help). This is using git
mesa3d on a current (~amd64) Gentoo, built both with and without LLVM shader
compiler backend. Kernel is 3.12-rc5.
It has, to my knowledge, never worked... I kept trying it once in a while for
half a year.
Since nobody else has complained yet, I suspect it's a problem that affects
only the HD4xxx line of cards.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2764 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-10-17 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 9:49 bugzilla-daemon [this message]
2013-10-17 9:51 ` [Bug 70569] DOTA2 background and other missing elements on HD4850 GPU bugzilla-daemon
2014-05-12 5:12 ` 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-70569-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.