From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 93144] [radeonsi] Alien: Isolation feature request
Date: Sun, 03 Apr 2016 00:39:35 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1122162472=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[IPv6:2610:10:20:722:a800:ff:fe98:4b55])
by gabe.freedesktop.org (Postfix) with ESMTP id DA02A6E360
for ; Sun, 3 Apr 2016 00:39:35 +0000 (UTC)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============1122162472==
Content-Type: multipart/alternative; boundary="14596439751.8a9bD3De.25909";
charset="UTF-8"
--14596439751.8a9bD3De.25909
Date: Sun, 3 Apr 2016 00:39:35 +0000
MIME-Version: 1.0
Content-Type: text/plain
https://bugs.freedesktop.org/show_bug.cgi?id=93144
--- Comment #26 from Christoph Haag ---
(In reply to Alexandre Demers from comment #24)
> Ok, I saw the comment in Phoronix' forum. I suspect the extension to still
> be disabled in his case.
glxinfo says opengl 4.2 and that the compute shader extension is there.
I tried making an apitrace, but it turned out to be 6.1 gigabyte, so I'm not
uploading that if there's no real need.
I don't know terribly much about shaders, but if I see
68300 @1 glCreateShader(type = GL_COMPUTE_SHADER) = 3085
68301 @1 glShaderSource(shader = 3085, count = 1, string = ["#version 420 core
etc...
68302 @1 glCompileShader(shader = 3085)
in apitrace, doesn't that mean it successfully uses compute shaders?
Mesa: User error: GL_INVALID_OPERATION in unsupported function called
(unsupported extension or deprecated function?)
But the skeptical approach might be the right one, that my first test didn't
actually test it with compute shaders.
I tried it with MESA_GL_VERSION_OVERRIDE=4.3fc MESA_GLSL_VERSION_OVERRIDE=430fc
to see whether the game would do something different - and if I'm not
completely blind it does look a lot better beyond the colorful flickering,
doesn't it?
New Video: https://www.youtube.com/watch?v=ueoELXXduvk
It did say once on startup:
Mesa: User error: GL_INVALID_OPERATION in unsupported function called
(unsupported extension or deprecated function?)
so there's possibly still something missing. (would be nice for mesa to
actually print what the "unsupported function" is)
Anyway, not investigating further right now because I want to go to sleep
before 3 AM.
--
You are receiving this mail because:
You are the assignee for the bug.
--14596439751.8a9bD3De.25909
Date: Sun, 3 Apr 2016 00:39:35 +0000
MIME-Version: 1.0
Content-Type: text/html
Comment # 26
on bug 93144
from Christoph Haag
(In reply to Alexandre Demers from comment #24)
> Ok, I saw the comment in Phoronix' forum. I suspect the extension to still
> be disabled in his case.
glxinfo says opengl 4.2 and that the compute shader extension is there.
I tried making an apitrace, but it turned out to be 6.1 gigabyte, so I'm not
uploading that if there's no real need.
I don't know terribly much about shaders, but if I see
68300 @1 glCreateShader(type = GL_COMPUTE_SHADER) = 3085
68301 @1 glShaderSource(shader = 3085, count = 1, string = ["#version 420 core
etc...
68302 @1 glCompileShader(shader = 3085)
in apitrace, doesn't that mean it successfully uses compute shaders?
Mesa: User error: GL_INVALID_OPERATION in unsupported function called
(unsupported extension or deprecated function?)
But the skeptical approach might be the right one, that my first test didn't
actually test it with compute shaders.
I tried it with MESA_GL_VERSION_OVERRIDE=4.3fc MESA_GLSL_VERSION_OVERRIDE=430fc
to see whether the game would do something different - and if I'm not
completely blind it does look a lot better beyond the colorful flickering,
doesn't it?
New Video: https://www.youtube.com/watch?v=ueoELXXduvk
It did say once on startup:
Mesa: User error: GL_INVALID_OPERATION in unsupported function called
(unsupported extension or deprecated function?)
so there's possibly still something missing. (would be nice for mesa to
actually print what the "unsupported function" is)
Anyway, not investigating further right now because I want to go to sleep
before 3 AM.
You are receiving this mail because:
- You are the assignee for the bug.
--14596439751.8a9bD3De.25909--
--===============1122162472==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============1122162472==--