All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103297] Rendering issue in cemu BOTW game for pre gcn hardware
Date: Mon, 16 Oct 2017 16:03:23 +0000	[thread overview]
Message-ID: <bug-103297-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 103297
           Summary: Rendering issue in cemu BOTW game for pre gcn hardware
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: johann.maxime@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 134866
  --> https://bugs.freedesktop.org/attachment.cgi?id=134866&action=edit
screenshot of botw

Using cemu emulator on Ubuntu 17.04 with wine lastest mesa git build give
graphical glitch on pre gcn hardware.
In my case I use AMD TURKS (HD 7670M).
The Legend Of Zelda Breath Of The Wild has heavy graphical issues.
Some other games works perfectly (Mario Kart 8 for example).

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

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

             reply	other threads:[~2017-10-16 16:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 16:03 bugzilla-daemon [this message]
2019-09-18 19:24 ` [Bug 103297] Rendering issue in cemu BOTW game for pre gcn hardware 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-103297-502@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.