From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 100177] New: [GM206] Misrendering in XCOM Ennemy Within
Date: Sun, 12 Mar 2017 22:37:23 +0000 [thread overview]
Message-ID: <bug-100177-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1227 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100177
Bug ID: 100177
Summary: [GM206] Misrendering in XCOM Ennemy Within
Product: Mesa
Version: 17.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: pierre.morrow-GANU6spQydw@public.gmane.org
QA Contact: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Created attachment 130180
--> https://bugs.freedesktop.org/attachment.cgi?id=130180&action=edit
IG Menu Screen in working state
On the menu screen of XCOM Ennemy Within, most of the background is not
visible, and some orther parts are flickering (some z-fighting?).
I tested with the same software stack on a Fermi card, and it worked there.
Card: GeForce GTX 960 (GM206)
Mesa: 17.0.1
Linux: 4.10
An apitrace of the bug is available here:
https://phabricator.pmoreau.org/F111738
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2744 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2017-03-12 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 22:37 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-100177-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-03-13 2:27 ` [Bug 100177] [GM206] Misrendering in XCOM Ennemy Within bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-13 4:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-13 4:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-13 9:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-29 14:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-30 16:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-100177-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.