From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90404] Shaders are choppy
Date: Mon, 11 May 2015 18:24:35 +0000 [thread overview]
Message-ID: <bug-90404-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1030 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=90404
Bug ID: 90404
Summary: Shaders are choppy
Product: Mesa
Version: 10.5
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: charlespoetwolf@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 115700
--> https://bugs.freedesktop.org/attachment.cgi?id=115700&action=edit
Link to the apitrace (Couldn't figure out how to trim it small enough)
I'm pretty sure these are the shaders that are broken. They have an arboreal
effect on my screen. Attached is an apitrace and screenshot of what it looks
like. The video card specifically is AMD Radeon HD 3650 Mobility
The item used for the report is Assault Android Cactus demo.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2533 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:[~2015-05-11 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 18:24 bugzilla-daemon [this message]
2015-11-18 19:55 ` [Bug 90404] Shaders are choppy bugzilla-daemon
2015-11-18 19:59 ` [Bug 90404] [Steam] Assault Android Cactus demo: " bugzilla-daemon
2015-11-19 4:36 ` bugzilla-daemon
2015-11-19 4:38 ` [Bug 90404] [Steam] Unity3D Games: " bugzilla-daemon
2019-09-18 19:19 ` 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-90404-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.