All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99444] [radeonsi] The Witcher 3 (GOG/1.31) [Wine] starting menu is distorted
Date: Mon, 23 Jan 2017 20:42:19 +0000	[thread overview]
Message-ID: <bug-99444-502-RuGJAgkLVx@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99444-502@http.bugs.freedesktop.org/>


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

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

--- Comment #9 from Shmerl <shtetldik@gmail.com> ---
(In reply to Samuel Pitoiset from comment #8)
> Well, the trace is broken somehow, and it has been recorded using NVIDIA
> blob because it relies on NV_register_combiners. That explains the
> GL_COMBINER0_NV errors while replaying it.
> 
> Could you try that game directly using RadeonSI? Presumably, it should work
> fine except if it still relies on NV_register_combiners. And that would be a
> game bug.

The second trace I linked: https://uploadfiles.io/caf8c is recorded on AMD
hardware (RX 480) with radeonsi. And the screenshot of the initial report shows
how it looks on actual RX 480 as well. That's exactly how I run it (it's from
the actual game run in Wine, not from trace).

I'm not sure how the other trace ( https://ufile.io/ed6ac ) was recorded - the
author never replied.

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

[-- Attachment #1.2: Type: text/html, Size: 1994 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-01-23 20:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18  3:03 [Bug 99444] [radeonsi] The Witcher 3 [Wine] starting menu is distorted bugzilla-daemon
2017-01-18  3:04 ` [Bug 99444] [radeonsi] The Witcher 3 (GOG/1.31) " bugzilla-daemon
2017-01-18  3:09 ` bugzilla-daemon
2017-01-18  8:18 ` bugzilla-daemon
2017-01-19  3:54 ` bugzilla-daemon
2017-01-20 20:24 ` bugzilla-daemon
2017-01-21  0:05 ` bugzilla-daemon
2017-01-22  3:52 ` bugzilla-daemon
2017-01-23 10:54 ` bugzilla-daemon
2017-01-23 20:30 ` bugzilla-daemon
2017-01-23 20:42 ` bugzilla-daemon [this message]
2017-01-23 20:44 ` bugzilla-daemon
2017-01-31  1:38 ` bugzilla-daemon
2017-01-31  9:18 ` bugzilla-daemon
2017-01-31  9:41 ` bugzilla-daemon
2017-01-31 16:58 ` bugzilla-daemon
2017-02-02  9:42 ` bugzilla-daemon
2017-02-03  9:57 ` bugzilla-daemon
2017-02-03 10:05 ` bugzilla-daemon
2017-02-03 10:45 ` bugzilla-daemon
2017-02-08  2:21 ` bugzilla-daemon
2017-02-10  3:55 ` 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-99444-502-RuGJAgkLVx@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.