From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98724] garbled output using glDrawElementsIndirect
Date: Mon, 14 Nov 2016 17:47:43 +0000 [thread overview]
Message-ID: <bug-98724-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1102 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98724
Bug ID: 98724
Summary: garbled output using glDrawElementsIndirect
Product: Mesa
Version: git
Hardware: Other
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: logan@bacoosta.com
QA Contact: dri-devel@lists.freedesktop.org
I work on an N64 emulator (GLupeN64). I received a report from a user that they
had garbled output from the application. They tried it with llvmpipe and it
worked.
The issue report is here:
https://github.com/loganmc10/GLupeN64/issues/102
It includes and apitrace and a screenshot.
I had him disable indirect drawing, and in that mode the application will use
glDrawElementsBaseVertex instead of glDrawElementsIndirect. He said that that
fixed the issue, but it was very slow.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2533 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-11-14 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 17:47 bugzilla-daemon [this message]
2016-11-15 1:57 ` [Bug 98724] garbled output using glDrawElementsIndirect bugzilla-daemon
2016-11-16 11:40 ` bugzilla-daemon
2016-11-17 1:14 ` bugzilla-daemon
2018-03-31 23:43 ` bugzilla-daemon
2019-09-25 17:55 ` 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-98724-502@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).