From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 44701] Regnum online textures flickering
Date: Thu, 12 Jan 2012 09:58:13 +0000 [thread overview]
Message-ID: <bug-44701-502-34loMvwovh@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-44701-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=44701
Michel Dänzer <michel@daenzer.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
|.org |org
Component|Drivers/Gallium/r600 |Mesa core
--- Comment #1 from Michel Dänzer <michel@daenzer.net> 2012-01-12 01:58:13 PST ---
(In reply to comment #1)
> Mesa warning: glDraw[Range]Elements(start 5358, end 5754, count 396, type
> 0x1403, indices=0x29dc)
> end is out of bounds (max=2943) Element Buffer 384 (size 11508)
> This should probably be fixed in the application.
> Mesa warning: glDraw[Range]Elements(start 3558, end 5358, count 1800, type
> 0x1403, indices=0x1bcc)
> end is out of bounds (max=2943) Element Buffer 384 (size 11508)
> This should probably be fixed in the application.
AFAICT these rendering calls are ignored, as start > max. That could explain
the missing parts on the screenshots.
This looks like either a bug in the app or in the Mesa core code printing these
messages. Either way, the driver probably can't do anything about it,
reassigning to Mesa core for now.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2012-01-12 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 23:02 [Bug 44701] New: Regnum online textures flickering bugzilla-daemon
2012-01-12 9:58 ` bugzilla-daemon [this message]
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-44701-502-34loMvwovh@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