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 89069] Lack of grass in The Talos Principle on radeonsi (native\wine\nine)
Date: Thu, 12 Feb 2015 09:00:21 +0000	[thread overview]
Message-ID: <bug-89069-502-tlsc1IJts1@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89069-502@http.bugs.freedesktop.org/>


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

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

--- Comment #10 from Daniel Scharrer <daniel@constexpr.org> ---
(In reply to smoki from comment #9)
>  As you say that you can't reproduce it with some traces, you may try to
> research which exact option in game

The reason the first trace doesn't show the same GPU faults is because it's
only up to the main menu. That used to be enough for the GPU faults, but some
recent change in mesa seems to have 'fixed' those. The new trace is longer and
all GPU faults happen while loading an actual game or walking around.

Anyway, I don't want to derail this bug too much with the GPU faults - just
though it was an interesting detail. If 0e9cded is reverted or another fix
lands in mesa master that happens to reintroduce the GPU faults I'll be sure to
reopen #87278.

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

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

  parent reply	other threads:[~2015-02-12  9:00 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10 20:01 [Bug 89069] Lack of grass in The Talos Principle on radeonsi (native\wine\nine) bugzilla-daemon
2015-02-11  0:29 ` bugzilla-daemon
2015-02-11  3:39 ` bugzilla-daemon
2015-02-11  3:51 ` bugzilla-daemon
2015-02-11 10:57 ` bugzilla-daemon
2015-02-11 14:56 ` bugzilla-daemon
2015-02-12  4:42 ` bugzilla-daemon
2015-02-12  7:16 ` bugzilla-daemon
2015-02-12  7:35 ` bugzilla-daemon
2015-02-12  8:43 ` bugzilla-daemon
2015-02-12  9:00 ` bugzilla-daemon [this message]
2015-02-12  9:09 ` bugzilla-daemon
2015-02-12 10:53 ` bugzilla-daemon
2015-02-12 14:18 ` bugzilla-daemon
2015-02-12 14:23 ` bugzilla-daemon
2015-02-12 14:26 ` bugzilla-daemon
2015-02-12 14:39 ` bugzilla-daemon
2015-02-13  2:48 ` bugzilla-daemon
2015-02-14  8:12 ` bugzilla-daemon
2015-02-17  3:17 ` bugzilla-daemon
2015-02-17  3:23 ` bugzilla-daemon
2015-02-17  4:34 ` bugzilla-daemon
2015-02-18 16:21 ` bugzilla-daemon
2015-02-18 18:31 ` bugzilla-daemon
2015-02-21 10:07 ` bugzilla-daemon
2015-02-21 13:36 ` bugzilla-daemon
2015-02-21 13:54 ` bugzilla-daemon
2015-02-21 14:19 ` bugzilla-daemon
2015-05-02  0:33 ` bugzilla-daemon
2015-05-02  0:38 ` bugzilla-daemon
2015-05-02  0:43 ` bugzilla-daemon
2015-05-02  0:44 ` bugzilla-daemon
2015-05-02  0:53 ` bugzilla-daemon
2015-05-03 11:30 ` bugzilla-daemon
2015-05-04 22:47 ` bugzilla-daemon
2015-05-08 23:09 ` 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-89069-502-tlsc1IJts1@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