dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28359] Regression running Second Life viewer on r600 (mipmap generation issue?)
Date: Sun, 20 Jun 2010 04:50:20 -0700 (PDT)	[thread overview]
Message-ID: <20100620115020.A89D11300E2@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-28359-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=28359

--- Comment #3 from Aidan Thornton <makosoft@googlemail.com> 2010-06-20 04:50:20 PDT ---
Small additional detail: the mipmaps themselves appear to be generated fine as
far as I can tell, and everything works so long as no mipmap generation is
happening. However, when a mipmap is generated the next frame rendered by the
viewer reliably fails to render a lot of the in-world objects. In fact, whilst
textures are being loaded rapidly enough that at least one mipmap is generated
per frame, the same affected objects are consistently not rendered on every
frame. 

It appears that hardware mipmap generation and rendering are interacting badly
somehow. Given that Second Life relies heavily on streaming textures, this is
enough to make it unusable.

(Oh, and the patch pointed to by git bisect does indeed force hardware mipmap
generation rather than software as it claims).

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2010-06-20 11:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-02 18:29 [Bug 28359] New: Regression running Second Life viewer on r600 (mipmap generation issue?) bugzilla-daemon
2010-06-02 19:21 ` [Bug 28359] " bugzilla-daemon
2010-06-03 10:39 ` bugzilla-daemon
2010-06-20 11:50 ` bugzilla-daemon [this message]
2012-11-02 16:28 ` bugzilla-daemon
2012-11-02 17:17 ` bugzilla-daemon
2012-11-02 17:42 ` 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=20100620115020.A89D11300E2@annarchy.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).