From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 59899] Diagonal rendering artifacts on xbmc
Date: Mon, 04 Feb 2013 09:57:20 +0000 [thread overview]
Message-ID: <bug-59899-502-V63nvVpOuj@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-59899-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1786 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=59899
--- Comment #6 from aeriksson@fastmail.fm ---
Tried mesa git as of yesterday. No improvement.
I've also tried to flip all USE flags on/off for mesa 9.0.1 with no
improvement.
Doing some surfing, I noticed the z buffer issues being a common problem, so I
decided to try the car racing game "trigger". It does show the same effect as
I've seen in screenshots on youtube (flickering triangular misrenderings on
objects). The dynamic behavior seems to be the same. However, I see the same
effect on the fist screen in Trigger, where the three helmets are shown. I'm
not sure if they are supposed to be animated or static. The zbuffer issues I
saw in other reports were all related to movements (Stuff move back/front, when
I move a little). I also have zbuffer issues on the terrain once the game
starts.
If xbmc makes use of depth to paint its screen with a bunch of objects, I can
see how this might be z related. However, xbmc should show a static screen (I
think), whereas common z reports are all related to movement of the observer (I
think).
Any ideas how one could test this theory?
Another crazy thing is that every once in a while it renders perfectly ok.
While "bisecting" through the USEflags, I had a run of "good, good, good,..."
and each test was a restart of Xserver, starting xbmc. After going back to the
known bad set of USE flags (which now rendered good!!), I did some cursing and
warm rebooted the box, and it suddenly rendered bad again :-(. This kind of
suggests an uninitialized HW register to me...
Any ideas how one can make xbmc not exercise the (gl?) related areas of the HW?
I'm lacking a solid known-good state at the moment.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2547 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-02-04 9:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 12:21 [Bug 59899] New: Diagonal rendering artifacts on xbmc bugzilla-daemon
2013-01-29 12:09 ` [Bug 59899] " bugzilla-daemon
2013-01-29 21:32 ` bugzilla-daemon
2013-01-29 21:33 ` bugzilla-daemon
2013-01-29 21:33 ` bugzilla-daemon
2013-01-31 8:56 ` bugzilla-daemon
2013-02-04 9:57 ` bugzilla-daemon [this message]
2019-09-18 18:51 ` 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-59899-502-V63nvVpOuj@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