From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 91247] Tomb Raider: Underworld renders lots of artefacts on models and objects
Date: Wed, 15 Jul 2015 03:30:25 +0000 [thread overview]
Message-ID: <bug-91247-8800-BMcSPmcCj6@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91247-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1169 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91247
--- Comment #2 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
Created attachment 117125
--> https://bugs.freedesktop.org/attachment.cgi?id=117125&action=edit
vert shader at failing call
OK, so in my trimmed trace,
http://people.freedesktop.org/~imirkin/traces/tru-trim.trace.xz
it seems like things start going wrong on API call 424136 (I ran apitrace
dump-images with '*/draw' and then did the diff-images thing).
Coincidentally, right before this happens, it does glDepthFunc(GL_EQUAL) [which
is *nuts*] and glDepthRange(0, 0.98).
I need to see if nuking that glDepthRange call causes llvmpipe to generate the
same image for that draw call. Also see if there are any funny depth-related
bits we know about... ugh.
Still bothering me is that apitrace is returning broken-looking depth surfaces.
The previous draws all had glDepthRange(0.98, 1)... coincidence? And the shader
will end up generating very negative z values, which will map to a depth range
of 0.98 I guess?
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2015-07-15 3:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 17:01 [Bug 91247] New: Tomb Raider: Underworld renders lots of artefacts on models and objects bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-91247-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-07-06 17:22 ` [Bug 91247] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-15 3:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2015-07-15 3:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-17 18:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-18 16:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-21 4:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-15 21:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-15 22:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-17 6:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-17 8:57 ` 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-91247-8800-BMcSPmcCj6@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.