From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94835] Increase fragment shader sample limits from 16 to 32 (AMD Linux - Mesa/RadeonSi)
Date: Wed, 06 Apr 2016 07:10:38 +0000 [thread overview]
Message-ID: <bug-94835-502-7NKYliLrbu@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94835-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 556 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=94835
--- Comment #1 from Edwin Smith <esmith@feralinteractive.com> ---
Added links to:
94705 - CoH2 specific bug logged by an end user showing the side effect if the
sampler limit is reached on AMD.
91951 - Unsure if exactly the same issue but potentially a similar root cause.
This was logged agains ARMA 3 developer by another developer so I have no
insight other than finding the bug when looking for duplicates before logging.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1390 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-04-06 7:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 7:05 [Bug 94835] Increase fragment shader sample limits from 16 to 32 (AMD Linux - Mesa/RadeonSi) bugzilla-daemon
2016-04-06 7:06 ` bugzilla-daemon
2016-04-06 7:10 ` bugzilla-daemon [this message]
2016-04-06 13:47 ` bugzilla-daemon
2016-04-06 17:03 ` bugzilla-daemon
2016-04-07 12:46 ` bugzilla-daemon
2016-04-07 18:18 ` 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-94835-502-7NKYliLrbu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox