From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71239] Metro Last Light quits(?) on r600g
Date: Mon, 18 Nov 2013 06:52:16 +0000 [thread overview]
Message-ID: <bug-71239-502-NFdciUfXDE@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-71239-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 942 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71239
--- Comment #14 from Tapani Pälli <lemody@gmail.com> ---
I've been testing this with Mesa master (2cfbf84) on IVB ultrabook. There's
quite a lot of rendering artifacts here and there, my findings so far:
1. all lighting and shadows are missing making the game look terrible
2. a flash of 'outside world' visible in the metro tunnel when game menu comes
up
3. text/graphics missing from game menus
4. sudden graphics glitches, looks like parts of low resolution fbo rendered on
top of scene now and then when moving the camera
5. flashes of objects rendered with solid red color (just when they become
visible for the first time?)
Following errors seen on console:
Mesa: User error: GL_INVALID_ENUM in glTexParameter(pname=GL_TEXTURE_LOD_BIAS)
will continue investigation on what's wrong
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1704 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
next prev parent reply other threads:[~2013-11-18 6:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 2:00 [Bug 71239] New: Metro Last Light quits(?) on r600g bugzilla-daemon
2013-11-05 2:16 ` [Bug 71239] " bugzilla-daemon
2013-11-05 2:17 ` bugzilla-daemon
2013-11-05 2:20 ` bugzilla-daemon
2013-11-05 2:33 ` bugzilla-daemon
2013-11-05 7:47 ` bugzilla-daemon
2013-11-05 9:27 ` bugzilla-daemon
2013-11-05 9:48 ` bugzilla-daemon
2013-11-05 10:24 ` bugzilla-daemon
2013-11-05 16:27 ` bugzilla-daemon
2013-11-06 11:41 ` bugzilla-daemon
2013-11-06 12:26 ` bugzilla-daemon
2013-11-06 13:19 ` bugzilla-daemon
2013-11-06 17:06 ` bugzilla-daemon
2013-11-18 6:52 ` bugzilla-daemon [this message]
2013-11-21 11:07 ` bugzilla-daemon
2013-11-21 15:54 ` bugzilla-daemon
2013-12-25 9:39 ` bugzilla-daemon
2014-01-09 9:32 ` bugzilla-daemon
2014-02-09 13:38 ` bugzilla-daemon
2014-02-10 7:19 ` bugzilla-daemon
2014-02-15 21:25 ` bugzilla-daemon
2014-02-16 4:30 ` bugzilla-daemon
2014-02-16 11:35 ` bugzilla-daemon
2014-02-16 12:23 ` bugzilla-daemon
2014-02-16 13:03 ` bugzilla-daemon
2014-02-16 13:32 ` bugzilla-daemon
2014-02-17 17:21 ` 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-71239-502-NFdciUfXDE@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;
as well as URLs for NNTP newsgroup(s).