On 2/16/13 1:28 AM, Francois Gouget wrote:
However I think the test should still not fail. So I'm looking for a
volunteer to either get the test to succeed with urlmon 6.0, or find a
way to detect it and skip these three tests.
I believe it's time to skip those tests on IE6 then. I will send a
Ben allowed me to forward this email.
Kudos to him for all the knowledge his brainbox contains!
Original Message
Subject: Re: Fix catalyst brain damage to speed up Falcon BMS 2x
Date: Sat, 16 Feb 2013 11:20:35 -0500
From: Ben Supnik
To: Stanislaw Halik
Hi Guys,
I'm afraid I
On 2013-02-16 15:27, Henri Verbeet wrote:
The driver essentially runs out of GPRs to run the shader. It's
probably a combination of lack of optimization and a shader that isn't
so great to begin with. Though if this is with the LLVM shader backend
for r600g you'll probably just want to disable th
On 16 February 2013 14:52, Stefan Dösinger wrote:
> I'm not sure what you mean by this. The mesa bug is incomprehensible as well,
> it isn't clear what exactly fails. I guess some shader doesn't compile, it
> might be helpful to attach the failing shader from Wine's debug output.
>
The driver es
On 2013-02-16 14:52, Stefan Dösinger wrote:
Lack of GLSL disables HDR apparently. But enabling it changes FPS from 70 to 90.
You want GLSL on AMD GPUs because the ARB shader extensions support only Shader
Model 2.0. I don't see the problem with changing the fps from 70 to 90 either
:-) . Did y
Hi,
The patch is conceptually wrong, tweaking how you disable ARB_map_buffer_range
won't improve the odds of it getting in. As I said, you want to make sure that
the problem is indeed fglrx(i.e., test on other cards and see if
map_buffer_range has a negative impact there), and if it is, we have
Interesting, Google for:
x-plane ARB_map_buffer_range "Ben Supnik"
Sorry for double post. Also BCC'ing Ben. If Ben wishes to make himself
seen, he will :)
Resubmitting. Spam filter ate my message. Really sorry if you receive
this twice!
On 2013-02-16 09:04, Stefan Dösinger wrote:
What you really want to do is figure out why GL_ARB_map_buffer_range
is slow on fglrx, and make sure that the problem is really fglrx
specific. I fixed a number of dynam
Am 16.02.2013 um 08:39 schrieb Stanisław Halik :
> +dynamic_buffer_ok = gl_info->supported[APPLE_FLUSH_BUFFER_RANGE] ||
> + (!gl_info->[GL_AMDX_debug_output] &&
> gl_info->supported[ARB_MAP_BUFFER_RANGE]);
What you really want to do is figure out why GL_ARB_map_buffer_range is slow on
fg
