From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99923] HITMAN (2016) having lighting and artefacting, and overly light room.
Date: Fri, 10 Mar 2017 05:59:08 +0000 [thread overview]
Message-ID: <bug-99923-502-Uy0llESEu1@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99923-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 805 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99923
--- Comment #10 from sephiroth99@gmail.com ---
I have the same issue. My GPU is a 7950. I am using Debian packages. I see the
issue with Mesa 17.0.1/LLVM 4. With Mesa 13.0.5/LLVM 3.9 the issue is not
present. This is also at the lowest settings possible, but it happens at
"medium" settings too.
One thing that changed between Mesa 13 and 17 for radeonsi is the OpenGL
version, it was 4.3 now at 4.5. I used the GLSL override to put version 430
with Mesa 17 but the issue still persists.
Unrelated last point: while searching on Bugzilla for this issue, there was
another one (100061), I think the Hitman issue it refers to in the description
is this issue?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1621 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:[~2017-03-10 5:59 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 15:09 [Bug 99923] HITMAN (2016) having lighting and artefacting, and overly light room bugzilla-daemon
2017-02-23 15:10 ` bugzilla-daemon
2017-02-23 15:32 ` bugzilla-daemon
2017-02-23 16:01 ` bugzilla-daemon
2017-02-23 16:47 ` bugzilla-daemon
2017-02-23 16:58 ` bugzilla-daemon
2017-02-23 17:23 ` bugzilla-daemon
2017-02-24 7:48 ` bugzilla-daemon
2017-02-24 8:53 ` bugzilla-daemon
2017-02-24 9:23 ` bugzilla-daemon
2017-02-24 9:33 ` bugzilla-daemon
2017-03-10 5:59 ` bugzilla-daemon [this message]
2017-03-10 6:22 ` bugzilla-daemon
2017-03-20 4:47 ` bugzilla-daemon
2017-03-22 16:54 ` bugzilla-daemon
2017-03-25 11:47 ` bugzilla-daemon
2017-04-05 4:37 ` bugzilla-daemon
2017-05-12 16:50 ` bugzilla-daemon
2017-06-21 22:27 ` bugzilla-daemon
2017-08-09 18:13 ` bugzilla-daemon
2017-11-07 20:26 ` bugzilla-daemon
2017-12-05 18:21 ` bugzilla-daemon
2017-12-05 19:09 ` bugzilla-daemon
2018-02-04 16:12 ` bugzilla-daemon
2018-03-22 13:52 ` bugzilla-daemon
2018-03-24 8:02 ` bugzilla-daemon
2018-04-03 9:04 ` bugzilla-daemon
2018-04-03 9:05 ` bugzilla-daemon
2018-04-03 15:28 ` bugzilla-daemon
2018-04-04 17:12 ` bugzilla-daemon
2018-05-22 6:21 ` bugzilla-daemon
2018-05-22 6:22 ` bugzilla-daemon
2018-05-22 6:25 ` bugzilla-daemon
2018-05-24 6:25 ` bugzilla-daemon
2018-07-11 13:25 ` bugzilla-daemon
2018-07-24 13:01 ` bugzilla-daemon
2018-08-04 17:41 ` bugzilla-daemon
2018-09-28 2:20 ` bugzilla-daemon
2018-10-04 2:27 ` bugzilla-daemon
2018-10-07 22:37 ` bugzilla-daemon
2018-10-08 22:21 ` bugzilla-daemon
2018-10-10 18:31 ` bugzilla-daemon
2018-10-11 19:41 ` bugzilla-daemon
2018-10-11 21:26 ` bugzilla-daemon
2018-10-31 15:33 ` bugzilla-daemon
2018-11-11 19:11 ` bugzilla-daemon
2018-11-12 14:49 ` bugzilla-daemon
2018-11-12 19:15 ` bugzilla-daemon
2019-01-27 13:54 ` 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-99923-502-Uy0llESEu1@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