dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100695] Texture artifacts in Deus Ex: Mankind Divided
Date: Sat, 22 Apr 2017 21:53:53 +0000	[thread overview]
Message-ID: <bug-100695-502-wook7f415c@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100695-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 669 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=100695

--- Comment #8 from Hadrien <freedesktop@psydk.org> ---
Some in-game bad textures disappeared. The Talos Principle is fixed too. I
think those glitches were actually related to bug 100681. The textures looked
dirty, but they were not complete garbage as seen in the screenshots attached
to this bug. So now I think it is a different problem.

So far I have only seen the glitch on user interface textures.

I am still learning to build my own version of Mesa with a specific version of
LLVM in order to find the bad revision.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1607 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

  parent reply	other threads:[~2017-04-22 21:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-16 17:37 [Bug 100695] Texture artifacts in Deus Ex: Mankind Divided bugzilla-daemon
2017-04-17  7:39 ` bugzilla-daemon
2017-04-18 19:48 ` bugzilla-daemon
2017-04-19  3:52 ` bugzilla-daemon
2017-04-21  0:45 ` bugzilla-daemon
2017-04-22 13:41 ` bugzilla-daemon
2017-04-22 19:53 ` bugzilla-daemon
2017-04-22 21:44 ` bugzilla-daemon
2017-04-22 21:53 ` bugzilla-daemon [this message]
2017-04-25 20:33 ` 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-100695-502-wook7f415c@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