From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 26092] shader problems with Flightgear
Date: Fri, 24 Feb 2012 12:59:12 +0000 [thread overview]
Message-ID: <bug-26092-502-PaOX7XHu5B@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-26092-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=26092
--- Comment #1 from popolon@popolon.org 2012-02-24 04:59:12 PST ---
I also have a problems with cloud with Sandy Bridge (i965 driver), using linux
kernel 3.0 or 3.2, Mesa 8.0.1., see [1] in attached picture.
I tried with software renderer, still a little line under the clouds sometimes,
but far less. Some transparant textures like chimnees on roof ([2] on attached
picture) have the transparent part fully black.
Only With kernel 3.2 (not with 3.0), that is far faster than 3.0, 2d windows
text rendering displays bugs during windowed flightgear ([3] on screenshot),
some times texte looks like barcode (vertical Black and white line along the
text), some time there is horizontal lines. hiding and redisplaying the window
resolve the artifact, but artifact appear again when the view is scrolled.
Still during windowed flightgear with Linux-3.2, jpeg display strangly in
firefox (4 ?, I can't manage to catch it in screenshot, when I click on gim
screenshot window, the problem disappear), pictures looks like randam shift
problems on some lines, like on old TV with bad signal reception.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-02-24 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 14:15 [Bug 26092] New: shader problems with Flightgear bugzilla-daemon
2012-02-24 12:59 ` bugzilla-daemon [this message]
2012-02-24 13:00 ` [Bug 26092] " bugzilla-daemon
2012-02-24 13:06 ` bugzilla-daemon
2012-02-24 21:09 ` bugzilla-daemon
2012-07-03 7:19 ` 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-26092-502-PaOX7XHu5B@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