From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100200] Default Unreal Engine 4 frag shader fails to compile
Date: Tue, 14 Mar 2017 16:07:48 +0000 [thread overview]
Message-ID: <bug-100200-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 914 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100200
Bug ID: 100200
Summary: Default Unreal Engine 4 frag shader fails to compile
Product: Mesa
Version: 13.0
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: felix@bellaby.plus.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 130218
--> https://bugs.freedesktop.org/attachment.cgi?id=130218&action=edit
default UE4 fragment shader
UE4Editor (with -opengl3) seems to run reasonably well on r600/ARUBA using Mesa
version 13.0, apart from the failure to compile the attached default fragment
shader.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2437 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:[~2017-03-14 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 16:07 bugzilla-daemon [this message]
2017-12-06 11:53 ` [Bug 100200] Default Unreal Engine 4 frag shader fails to compile bugzilla-daemon
2018-08-11 11:37 ` bugzilla-daemon
2018-12-07 16:05 ` 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-100200-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.