From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70650] New: Blackscreen on Unity3D Games
Date: Sat, 19 Oct 2013 16:10:50 +0000 [thread overview]
Message-ID: <bug-70650-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1185 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=70650
Priority: medium
Bug ID: 70650
Assignee: dri-devel@lists.freedesktop.org
Summary: Blackscreen on Unity3D Games
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: openproggerfreak@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/radeonsi
Product: Mesa
Created attachment 87855
--> https://bugs.freedesktop.org/attachment.cgi?id=87855&action=edit
RADEON_DUMP_SHADERS(Guns of Icarus)
Its not possible to start any Game which is using the Unity3D-Engine (like Guns
of Icarus,Splice,Spectraball etc.)
When you start the Game a Blackscreen Window appears and nothing more is
happening(the Process have no CPU % or changing RAM-Usage).
It works with LLVMpipe(LIBGL_ALWAYS_SOFTWARE=1) so its definitly a
radeonsi-problem
Kernel 3.12rc3 (drm-next git branch)
Mesa 10.0.0-devel
libdrm git
glamor git
Xorg 1.14.3
AMD Radeon HD 7970
PS:Sorry for my bad English -.-
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2630 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:[~2013-10-19 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-19 16:10 bugzilla-daemon [this message]
2013-10-19 16:50 ` [Bug 70650] Blackscreen on Unity3D Games 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-70650-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.