From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91780] Rendering issues with geometry shader
Date: Thu, 27 Aug 2015 21:04:49 +0000 [thread overview]
Message-ID: <bug-91780-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2402 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91780
Bug ID: 91780
Summary: Rendering issues with geometry shader
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: jonas@wielicki.name
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 117951
--> https://bugs.freedesktop.org/attachment.cgi?id=117951&action=edit
apitrace which shows the problem
In the attached apitrace, *sometimes* (about 50% of the runs) rendering issues
can be observed. They manifest in appearantly missing geometry (compare
attached screenshot; the UI has been disabled for taking the apitrace).
Steps to reproduce:
1. DRI_PRIME=1 apitrace replay r600-renderbug-noui.trace
2. If step 1 did not show the behaviour, retry a few times.
Expected results:
Rendering should work and show a terrain without holes
Actual results:
Holes in the terrain
The results have been observed on mesa-11.0.0-rc1 with and without
http://lists.freedesktop.org/archives/mesa-dev/2015-August/092766.html applied.
The same code has never (in 50+ tests) shown the issue on the Intel integrated
GPU.
The application which produces the given behaviour can be found at
https://github.com/horazont/scc/tree/f31d90e1579ebda14ce7a0417339b2cd448efde8
The geometry shader is in:
https://github.com/horazont/scc/blob/f31d90e1579ebda14ce7a0417339b2cd448efde8/game/resources/shaders/terrain/main.geom
The usage is in:
https://github.com/horazont/scc/blob/f31d90e1579ebda14ce7a0417339b2cd448efde8/libffengine-render/src/render/fancyterrain.cpp
(search for draw_elements, GL_GEOMETRY_SHADER, GL_LINES_ADJACENCY)
In another commit, the geometry shader has been disabled
(<https://github.com/horazont/scc/commit/4e1e298b02723efcf6555c1c4a7efa31682cf79b>),
which appears to fix the problem or make it very hard to reproduce.
radeon GPU:
Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD
6630M/6650M/6750M/7670M/7690M] (rev ff) {6630M according to notebook specs}
intel GPU:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller (rev 09)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4397 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 reply other threads:[~2015-08-27 21:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 21:04 bugzilla-daemon [this message]
2015-08-27 21:06 ` [Bug 91780] Rendering issues with geometry shader bugzilla-daemon
2015-08-27 21:20 ` bugzilla-daemon
2015-08-27 21:29 ` bugzilla-daemon
2015-08-27 21:29 ` bugzilla-daemon
2015-08-28 7:39 ` bugzilla-daemon
2015-09-03 9:59 ` bugzilla-daemon
2015-09-03 10:00 ` bugzilla-daemon
2015-09-04 13:05 ` bugzilla-daemon
2015-11-11 23:07 ` 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-91780-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